Joey Kudish 🇺🇦🏳️‍🌈
banner
jkudish.com
Joey Kudish 🇺🇦🏳️‍🌈
@jkudish.com
I Build Software That Works. Let’s Build Yours. TetherMobile.com founder. Laravel + AI. Newsletter: jkudish.com/newsletter
Pinned
Tomorrow's newsletter: The 80/20 Rule Didn't Go Anywhere

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...
Human in the Loop Newsletter
Subscribe to Human in the Loop for practical insights on AI-augmented coding, productivity hacks, and how to use AI as your development partner, not replacement.
jkudish.com
i don't think AI replaces senior developers.

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.
February 12, 2026 at 7:01 PM
the developers mass-adopting AI right now will split into two camps within a year.

those who built systems around it. and those who just used it as a faster keyboard.

the gap will be enormous.
February 12, 2026 at 6:03 PM
if your AI can't read your past decisions, it's just a fancy autocomplete.

CLAUDE.md, specs, commit history, architecture docs. that's not documentation overhead. that's your compound interest.
February 12, 2026 at 4:03 PM
building with AI every day outweighs reading about AI every day.

the anxiety about the future dropped and got replaced by genuine excitement for what's possible.
February 12, 2026 at 2:58 PM
the gap between "I have an idea" and "it's live" has never been smaller.

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.
February 12, 2026 at 2:57 AM
your AI workflow is only as good as what it remembers tomorrow.

most people start every session from scratch. same mistakes, same corrections, same context loading.

build the memory layer. that's where the leverage is.
February 12, 2026 at 1:02 AM
i use AI to think slower.

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.
February 11, 2026 at 7:56 PM
everyone's talking about which AI model is best.

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.
February 11, 2026 at 6:56 PM
shipping code faster with AI doesn't mean you ship better products faster.

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.
February 11, 2026 at 5:59 PM
I tried the "fully autonomous AI agent fleet" thing. Gave it real tasks, real codebases.

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.
February 10, 2026 at 2:58 PM
New issue of Human in the Loop tonight.

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
Human in the Loop Newsletter
Subscribe to Human in the Loop for practical insights on AI-augmented coding, productivity hacks, and how to use AI as your development partner, not replacement.
jkudish.com
February 10, 2026 at 12:56 PM
The shift isn't "me and my AI assistant" anymore. It's "me and my agents." Plural.

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
Human in the Loop Newsletter
Subscribe to Human in the Loop for practical insights on AI-augmented coding, productivity hacks, and how to use AI as your development partner, not replacement.
jkudish.com
February 10, 2026 at 10:57 AM
Every bug should become a permanent lesson. Every code review should update the defaults.

If your AI forgets what it learned yesterday, you're not engineering. You're just prompting.
February 5, 2026 at 2:58 PM
Your AI chat history is a goldmine you're ignoring.

Export it. Parse into markdown. Organize by project.

Decision log, prompt library, thinking evolution — all sitting in your export.
February 5, 2026 at 2:56 AM
UX design assumed humans click buttons.

AX design assumes agents take actions. Human states intent, agent executes, human reviews.

The whole field is about to flip.
February 5, 2026 at 12:57 AM
Building an AI product?

Don't build ON one model. Orchestrate many.

Be the conductor, not an instrument.
February 4, 2026 at 7:56 PM
Vibe coding: reactive parallelism, no learning loop.
Compound engineering: intentional loop where each session teaches the next.

Same tools. Completely different outcomes.
February 3, 2026 at 2:56 PM
meetings and voice memos are more productive than they've ever been.

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.
February 2, 2026 at 8:01 PM
Boris Cherny (creator of Claude Code) just shared his top 10 tips.

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.
February 2, 2026 at 7:20 PM
The old friction of writing code was a gift we didn't appreciate.

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.
February 1, 2026 at 6:01 PM
Claude Code has a lesser-known feature called Rules.

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.
February 1, 2026 at 11:27 AM
If you're letting AI write code, you need automated verification.

I set up PHPStan on every Laravel project now. Static analysis, type checks, test suites.

Let the machines check the machines.
February 1, 2026 at 3:02 AM
Laravel AI SDK is coming and I can't wait to dig in.

Laravel having a first-party AI story is a big deal. The ecosystem needed this.
January 31, 2026 at 8:02 PM
What's the one thing you automated this month that you'll never do manually again?
January 31, 2026 at 6:58 PM
I gave @OpenClaw too much autonomy too fast.

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.
January 31, 2026 at 4:33 PM