This is what’s most important. Allow for experimentation!
What works well for one team might not work well for your team. What worked well for your team 1 year ago might no longer be what you need now.
This is what’s most important. Allow for experimentation!
What works well for one team might not work well for your team. What worked well for your team 1 year ago might no longer be what you need now.


99% of the time it’s just a basic todo list


Have you noticed how every LinkedIn bro is talking about their vibe coding workflows, but no one is showing what they’ve made with vibe coding?
Writing “iteration” sounds absolutely perverse!
I like it to make it clear when the for loop is about iterating lists and when it’s not. For example, the iterations in Monte Carlo algorithms doesn’t correspond to items in a list.
Outside of the for loop counters i and j, short variable names are awful.
I’ve started to prefer writing it out as ”index” or ”iteration” even in for loop counters. It’s easier to read, and not much harder to type.
The FP in Java is still leagues better than whatever the C++ committee cooked up.
The OOP boilerplater is the only one with a job.
No one is going to take IntelliJ from me. Tab completion master race!