The advice to be visible is correct. Nobody talks about what it actually costs. The volume, the fear, the parallel grind on top of an already brutal job search.
Wrote about it.
https://t.co/whlE7WHQ63
Internal tests see source. Bugs live in dist.
Three enforcement layers (ESLint, build config, test:dist) close the gap. Walked through it in nuka-ui.
https://t.co/V8f7pXOUTs
“Isn’t that a lot of tokens?”
Yes. It also does the thing.
The cost of correcting an agent that drifted, hallucinated, or edited the wrong file is much higher than the cost of structuring it well up front.
New post: After Knowledge, Discipline.
https://t.co/JcplNrpBk1
The planning work that gets skipped under every deadline was never skipped because engineers didn't know how to do it.
It was skipped because time was the binding constraint.
That constraint is largely gone now.
New article: https://t.co/5rYd6XXysz
There is a role that does not appear in any job description but exists on every frontend team.
You are not building. You are maintaining the illusion that the codebase is still under control.
The Janitor Pattern. And it is not caused by bad developers.
https://t.co/g8BGKNAVZF
Our #RubyOnRails apps at GaggleAMP have published content to 3rd Party APIs for almost 10 years. Here are some things we've put in place to reliably perform these API calls from our apps’ background job workers:
.
.
Thread👇