@allenholub "Just talk about the issues as they come up" has never worked well in any context I've seen it used, and was mostly used as a blame game later, like "why didn't you bring it up before"...
@allenholub In my experience, most problems are so small that they seem like not something you really should put the effort in bringing up, until they are so big that they are difficult to solve. Regular retros lower the threshold for problems to be brought up.
studying conversation the way you study chess openings
"if they go 'how are you', you play 'good, how are you'. now in this position the opponent has a few possible moves. for example after 'so how do you know [party organizer]', you can…"
- Do you use Windows or Unix?
- Unix
- Me too! MacOS or free software?
- Free software
- Same! BSD or GNU/Linux?
- GNU/Linux
- Yay! RPM or deb?
- RPM
- DIE UNWASHED HEATHEN SCUM
… and I’ve never talked to them again.
Ruby-on-Rails advices we can read everywhere :
- don't put logic in the View
- don't put logic in the Controller
- don't put logic in the Model
Don't put any logic. Period. 😁😁😁
Now that Covid is over (🤦♂️) let's look at how the High Income Countries have performed.
▪️Covid deaths
▪️Excess deaths
▪️Mortality rates
▪️Vaccination Rates
▪️Loss of freedoms
▪️Economy.
How did your country do?
🧵
I'm not sure who needs to hear this, but if you're holding in-person conferences during a pandemic, you might want to avoid the use of the term "breakout sessions."
Some of the most effective senior engineers are the ones who help others by teaching how they think about problems. At some point, your biggest contribution becomes explaining your mental model.
@b0rk "Why is this process not doing what it's supposed to be doing" - hanging on i/o, deadlock, whatever... strace is my go-to debugging tool, if I don't know what to do, I strace everything.