Being able to take out the battery so that I can swap it with a pre-charged one. Those were great times. Then you can just throw the nearly-dead one on the charger.
This is identical to having the super power of being able to restart your phone to get a full battery charge.
I'm sure Chuck Schumer will get to the bottom of this after he finishes his book tour on antisemitism in America while being completely tone-deaf on the absolute disdain many of us have for our tax dollars supporting a genocide in the 21st century.
I had a similar experience with square roots, writing both the positive and negative answers. It's wild for a teacher to actively reject correct answers because "that's not what we learned today" (the negative answers, in my case).
This was a great blog post. I love Rust and Bevy, but I can definitely see why you made the switch.
The primary issue with your decision to use Rust/Bevy, for me, was that you were taking on the task of getting others to work in a difficult language for novice developers. I would never suggest Rust as someone's first language, coupling that with a regularly-changing library like Bevy.
I would love to know what the pros and cons were between Unity and Godot. If you were going to switch to C# anyway, Godot seems like the next logic choice to me, so I'm curious about what your team's evaluation was for that engine.
When I learned Python I thought that not having a statically typed language was the way to go, but then it just became an issue when I was trying to ensure that everything was at least something like what I was expecting. Going back to statically typed languages even harder with Rust has been a dream. I love it.
I've had mine on vibrate for years. Texting doesn't trigger it, only calls. It's been great. I look at my phone only when I'm ready to look at it.
This was a good blog post. I particularly appreciated the statement about the validate and parse function comparison: "Both of these functions check the same thing, but parseNonEmpty gives the caller access to the information it learned, while validateNonEmpty just throws it away."
You can just pinch the end of a banana to start peeling it. The effort required is far less than trying to overcome the ripping force of the stem.
I love how the solution didn't involve changing the prefix to "mcaffee_". Now users don't know who to blame. Great. That's so nice of them.
Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn't be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.
As someone who learned a lot from C++ and that now loves Rust, this annoys me.
Now I use lowercase and underscores everywhere.