Joey Kudish 🇺🇦🏳️🌈
@jkudish.com
I Build Software That Works. Let’s Build Yours. TetherMobile.com founder. Laravel + AI. Newsletter: jkudish.com/newsletter
More tonight: 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 2:58 PM
More tonight: jkudish.com/newsletter
I have a /create-skill skill, very meta I know
February 3, 2026 at 3:43 PM
I have a /create-skill skill, very meta I know
Each one teaches the next one. The commit skill informed the PR skill. The meeting notes skill feeds the daily planner. The code review skill shaped the test runner.
You're not building tools. You're building an ecosystem that gets smarter every week.
You're not building tools. You're building an ecosystem that gets smarter every week.
February 2, 2026 at 7:20 PM
Each one teaches the next one. The commit skill informed the PR skill. The meeting notes skill feeds the daily planner. The code review skill shaped the test runner.
You're not building tools. You're building an ecosystem that gets smarter every week.
You're not building tools. You're building an ecosystem that gets smarter every week.
The 1000x developer isn't who prompts fastest.
It's who rebuilds the right friction, the kind that forces focus, teaches the system, and ensures you FINISH before starting the next thing.
Build the governor back in. Just make it yours.
It's who rebuilds the right friction, the kind that forces focus, teaches the system, and ensures you FINISH before starting the next thing.
Build the governor back in. Just make it yours.
February 1, 2026 at 6:01 PM
The 1000x developer isn't who prompts fastest.
It's who rebuilds the right friction, the kind that forces focus, teaches the system, and ensures you FINISH before starting the next thing.
Build the governor back in. Just make it yours.
It's who rebuilds the right friction, the kind that forces focus, teaches the system, and ensures you FINISH before starting the next thing.
Build the governor back in. Just make it yours.
The answer isn't "slow down." It's intentional friction.
Friction you choose, not friction imposed on you:
→ Spec-first workflows (plan before you prompt)
→ Review loops that teach the next session
→ Completion rituals (what did I FINISH today?)
Friction you choose, not friction imposed on you:
→ Spec-first workflows (plan before you prompt)
→ Review loops that teach the next session
→ Completion rituals (what did I FINISH today?)
February 1, 2026 at 6:01 PM
The answer isn't "slow down." It's intentional friction.
Friction you choose, not friction imposed on you:
→ Spec-first workflows (plan before you prompt)
→ Review loops that teach the next session
→ Completion rituals (what did I FINISH today?)
Friction you choose, not friction imposed on you:
→ Spec-first workflows (plan before you prompt)
→ Review loops that teach the next session
→ Completion rituals (what did I FINISH today?)
Here's what I'm seeing (in myself and every builder I talk to):
Code collapses days into minutes. But decisions, what to build, why, in what order, take the same time they always did.
We removed the production bottleneck and exposed the real one: judgment.
Code collapses days into minutes. But decisions, what to build, why, in what order, take the same time they always did.
We removed the production bottleneck and exposed the real one: judgment.
February 1, 2026 at 6:01 PM
Here's what I'm seeing (in myself and every builder I talk to):
Code collapses days into minutes. But decisions, what to build, why, in what order, take the same time they always did.
We removed the production bottleneck and exposed the real one: judgment.
Code collapses days into minutes. But decisions, what to build, why, in what order, take the same time they always did.
We removed the production bottleneck and exposed the real one: judgment.