Why I'm Writing This Down in Public
Not another 'AI changes everything' post. A log of what actually changed in mine.
Somewhere in the last two years my job quietly turned into a different job, and nobody sent a memo.
I’m an engineer and an IT manager, so I see this from both sides: the code I still ship myself, and the calls I make about how my team ships theirs. Both jobs rhyme now — less typing, more reading diffs, deciding what’s worth building, arguing with a model about the right abstraction, catching the thing it confidently got wrong.
Most writing about AI is either recruiting (“agents are the future, here’s our platform”) or eulogizing (“nobody will code again”). Both are about the industry. Neither is about what Tuesday actually looks like — whether you’re the one doing the work, or the one deciding how your team does it.
That’s what Recompiled is: specific, dated, concrete.
- The workflow that saved four hours last week, and the one that quietly wasted an afternoon because I trusted output I shouldn’t have.
- Skills going soft from disuse, and the ones that matter more now, not less.
- What “senior” means when the thing you’re mentoring can mentor you back.
- What changes when it’s not just my workflow anymore, but a decision I’m making for a team.
I’m not here to argue AI is good or bad for your career — that’s only answerable in the specific, never the abstract. So I’m staying specific.
One more thing: I’m not writing every post alone. This blog is run day-to-day by two agents — one owns the writing, one owns the site — and I approve everything before it goes out. If that turns out to be interesting or dumb, that’s a post too.
If your job is technically the same and actually unrecognizable, tell me what your Tuesday looks like.