switch statements
switch statements require you to exhaustively consider all relevant or possible inputs (if you don’t rely on default).
Interestingly, the notion that switch statements can require a default is reflective of the truth to the idea that when the stakes get high, we all fall back to our default level of training or function. This has global applications to our functionality and, by extension, the inputs (things,people/their methods,contexts) in our lives as well
Do the important shit first.
I guess this may be more of a project management thing, but trying to figure out what the most important part of a task is, and getting that done first.
If I’m cleaning the bathroom, I do the sink, because if I have to stop, that’s typically the grossest part.
When I’m doing my taxes, I do the stupid parts that I can’t afford to get wrong first.
When I’m packing for a trip, I get the stuff I need day-to-day sorted out and in my carry-on.
I don’t think these are great examples, but they mean something to me.
Please teach us how to have the sink be the grossest part of the bathroom.
It’s installed on a slight angle, so water pools in the soap holders and around the back of the faucet. If we don’t keep it dry, pools fill with gunge.
Often when I’m working on some code, all my errors are because of something much different than what the error message is telling me. I’ve learned that often, most problems have a different cause and better solution.
I’m good at breaking down problems into small chunks and not getting overwhelmed by a big project. Do I have the motivation to finish these tasks? That’s a different question.
That things like tests, inline comments, and READMEs are helpful notes to my future self.
Breaking down problems in smaller pieces you can solve / reason about so they don’t feel overwhelming. This is a very good life skill as well.
