@OrionSeven Our participation in the syntax generation of software engineering is gone -- and good riddance. However, the rest, and most important part, of software engineering is still in full force.
@ThePrimeagen When the dust finally settles, and we all realize the discipline required to properly use agents, I think we will be looking at a productivity increase on the order of a factor of 2 to 5.
I spent the weekend actually reading the Claude Code docs.
It's a rabbit hole.
CLAUDE.md files. MCP configs. Skills. Subagents. Hooks. Plugins. Agent Teams.
You could spend more time configuring Claude Code than building software.
All of it is productivity theatre.
The only thing that actually matters: think first, then give it focused, relevant context.
I just nearly fell into a 50-year-old trap: waterfall.
"I'll plan everything upfront, feed the spec to the LLM, ship it all."
But specs→code isn't like a compiler. Some questions only get answered in code.
Note to self: Validate the risky parts first.
The best DevOps tool is a calm, experienced senior engineer who's seen this problem before.
All the automation in the world can't replace someone who knows when NOT to automate something.
Hear me out:
We should standardize rules files as...
https://t.co/QOOsDi51uC
Not https://t.co/aB8qN0Dkjb, .cursorrules, https://t.co/Zbk0dmnB8R and all that BS
Many of the most important “prompt engineering” skills are management skills: clearly understanding the task to be done & what information is needed to do it; explaining the task to the AI; giving useful feedback to improve outputs; & generalizing lessons learned into a process.
It bothers me a lot that I feel less able to create a full working web app in an hour today than I could 11 years ago. It feels like it should be *much* easier now!