Rust is a lot of fun.
Adopting it for the Fitness Tracker project was definitely the right call - it has dramatically sped up the whole project and build sizes are incredibly small.
When I first got into Rust, the compiler felt slow. Installing rust-analyzer in VS Code felt muddy. With experience (and a lot of documentation), I have sped things up. But most importantly, I realize that the compiler is kind of slow and rust-analyzer is muddy. But I make that time back by avoiding difficult bugs in production so that’s more of a feature.
But getting deeper into Rust has meant that I have had to up my acronym game. I worked with a dude one time who took pronunciations really seriously and, I was less mature then, so I used to pronounce things in ways I knew would piss him off. But I have turned over a new leaf and so now I’m trying.
SQLX though….SEQUEL-EX? Or Es-Eue-El-Ex?
SEQUEL-EX sounds too much like one of the X-Men so I kind of prefer es-cue-el-ex. But that introduces my SQLite problem. SEQUEL-ite feels more comfortable whereas es-cue-el-ite reminds me of the time my roommate was working on his PhD in Geology.
So do I build a Windows app with es-cue-el-ex and sequel-ite? Do I go es-cue-el-ite and start making great geology jokes like ‘I would have used an arc to reference volcanic but implementing subduction with Rust made me blow my top’.
This is why software projects go over time and over budget.