AI didn't eliminate the hard work. It just revealed where it actually lives.
The easy stuff was never the real work - we were just busy doing it. Now AI compresses it, and we hit the hard parts faster.
jkudish.com/newsletter?u...
i think it makes the gap between senior and junior wider than it's ever been.
seniors know what to ask for, what to reject, and when the AI is confidently wrong. that's not a skill you can shortcut.
i think it makes the gap between senior and junior wider than it's ever been.
seniors know what to ask for, what to reject, and when the AI is confidently wrong. that's not a skill you can shortcut.
those who built systems around it. and those who just used it as a faster keyboard.
the gap will be enormous.
those who built systems around it. and those who just used it as a faster keyboard.
the gap will be enormous.
CLAUDE.md, specs, commit history, architecture docs. that's not documentation overhead. that's your compound interest.
CLAUDE.md, specs, commit history, architecture docs. that's not documentation overhead. that's your compound interest.
the anxiety about the future dropped and got replaced by genuine excitement for what's possible.
the anxiety about the future dropped and got replaced by genuine excitement for what's possible.
which means the gap between you and your competition has never been smaller either.
taste, positioning, and who you build for matter more than ever. the code is the easy part now.
which means the gap between you and your competition has never been smaller either.
taste, positioning, and who you build for matter more than ever. the code is the easy part now.
most people start every session from scratch. same mistakes, same corrections, same context loading.
build the memory layer. that's where the leverage is.
most people start every session from scratch. same mistakes, same corrections, same context loading.
build the memory layer. that's where the leverage is.
spec conversations, architecture reviews, decision journals. each one feeds the next session. the AI gets sharper because my inputs get sharper.
shipping fast, at this point, is table stakes. compounding context is what I focus on now.
spec conversations, architecture reviews, decision journals. each one feeds the next session. the AI gets sharper because my inputs get sharper.
shipping fast, at this point, is table stakes. compounding context is what I focus on now.
the developers actually shipping are using all of them. different models, different tasks, swap as needed.
the answer was never "pick one." it's orchestrate many.
the developers actually shipping are using all of them. different models, different tasks, swap as needed.
the answer was never "pick one." it's orchestrate many.
feature bloat is easier than ever.
decision paralysis is worse.
scope creep happens in minutes instead of weeks.
speed without direction is just expensive chaos.
feature bloat is easier than ever.
decision paralysis is worse.
scope creep happens in minutes instead of weeks.
speed without direction is just expensive chaos.
Too sloppy. Too many assumptions. Not enough awareness of what makes code maintainable.
The path forward isn't "turn it loose and hope." It's building up the system with guardrails first.
Too sloppy. Too many assumptions. Not enough awareness of what makes code maintainable.
The path forward isn't "turn it loose and hope." It's building up the system with guardrails first.
What actually works in my AI setup. What doesn't yet. Two new Claude Code features that push things forward. And why I think the direction matters more than the destination.
jkudish.com/newsletter
What actually works in my AI setup. What doesn't yet. Two new Claude Code features that push things forward. And why I think the direction matters more than the destination.
jkudish.com/newsletter
Each one focused. Each one disposable. The human stays in the loop at every decision point.
Writing about this tonight in my newsletter
jkudish.com/newsletter
Each one focused. Each one disposable. The human stays in the loop at every decision point.
Writing about this tonight in my newsletter
jkudish.com/newsletter
If your AI forgets what it learned yesterday, you're not engineering. You're just prompting.
If your AI forgets what it learned yesterday, you're not engineering. You're just prompting.
Export it. Parse into markdown. Organize by project.
Decision log, prompt library, thinking evolution — all sitting in your export.
Export it. Parse into markdown. Organize by project.
Decision log, prompt library, thinking evolution — all sitting in your export.
AX design assumes agents take actions. Human states intent, agent executes, human reviews.
The whole field is about to flip.
AX design assumes agents take actions. Human states intent, agent executes, human reviews.
The whole field is about to flip.
Don't build ON one model. Orchestrate many.
Be the conductor, not an instrument.
Don't build ON one model. Orchestrate many.
Be the conductor, not an instrument.
Compound engineering: intentional loop where each session teaches the next.
Same tools. Completely different outcomes.
Compound engineering: intentional loop where each session teaches the next.
Same tools. Completely different outcomes.
record it, transcribe it, process it. decisions get captured with their reasoning. action items route to the right project. status updates sync automatically.
talking is faster than typing. let AI handle the rest.
record it, transcribe it, process it. decisions get captured with their reasoning. action items route to the right project. status updates sync automatically.
talking is faster than typing. let AI handle the rest.
Tip #4: "If you do something more than once a day, turn it into a skill or command."
Sitting at 46 commands, 44 skills, 38 sub-agents now. But the number isn't the point.
Tip #4: "If you do something more than once a day, turn it into a skill or command."
Sitting at 46 commands, 44 skills, 38 sub-agents now. But the number isn't the point.
It forced you to be deliberate. You couldn't start 5 features at once because you physically couldn't build them fast enough.
Now that friction is gone. And if we're not intentional about replacing it, we're in trouble.
It forced you to be deliberate. You couldn't start 5 features at once because you physically couldn't build them fast enough.
Now that friction is gone. And if we're not intentional about replacing it, we're in trouble.
You can add .md files to .claude/rules/ and scope them to specific file paths with glob patterns. They load automatically when Claude touches matching files.
You can add .md files to .claude/rules/ and scope them to specific file paths with glob patterns. They load automatically when Claude touches matching files.
I set up PHPStan on every Laravel project now. Static analysis, type checks, test suites.
Let the machines check the machines.
I set up PHPStan on every Laravel project now. Static analysis, type checks, test suites.
Let the machines check the machines.
Laravel having a first-party AI story is a big deal. The ecosystem needed this.
Laravel having a first-party AI story is a big deal. The ecosystem needed this.
It wrote 30k lines of code for a personal software system. Got sloppy quick. The kind of sloppy where you open a file and go "what is this doing."
But I learned more from those 30k lines than I expected.
It wrote 30k lines of code for a personal software system. Got sloppy quick. The kind of sloppy where you open a file and go "what is this doing."
But I learned more from those 30k lines than I expected.