Post

This is so true it hurts, it truly adds an extra layer when writing/putting RFCs up for review. Also, there’s nothing like “who the hell thought this was a good ide-“ and then seeing your name embedded in a comment

Me 7 years ago writing clever code to optimize computer time or line count. Me today writing obvious code to optimize my time 3 months from now.

Pro tip: you can speed this up by making really bad decisions that bite you much faster. I'm only half-joking too; I've seen some teams where the culture pushed people to write such bad code that it started causing problems and wasting time within months or even weeks, not years.

true

This was one of my most formative experiences in my PhD! Some examples: * Polyrepo -> monorepo * Static typing for configuration -> Runtime with Confection Looking at some code, seeing it as a teachable moment for a junior, and seeing that _I_ wrote it, was very humbling.

This really resonates with me. I spent 6 years building the AI products at my previous company and felt first hand the consequences of decisions (both good and bad). I've much more opinions on how to do certain things because of it.

Agree! Currently paying off debt now and is part of the reason for me doing more data eng work (hired as a data scientist). Helped build pipelines from 0 data and seeing now that things work differently at different scales