Claude Code Skills vs Slash Commands: Which One to Use
Three differences that actually matter — and why I default to slash commands after weeks of trial and error.
I Spent Weeks Confused About Claude Code's 5 Concepts. Here's the Mental Model That Finally Clicked.
Slash commands, skills, agents, MCP servers, plugins — I kept building three things for the same task until this mental model clicked.
I spent years on Kubernetes. Now I'm betting against it.
Solo devs don’t need complexity. They need deploys that work.
Why Your AI Wakes Up Every Morning With No Memory (And how to fix it)
AI agents start every session blank. Here’s why context loss is the silent killer of productivity, and the patterns that fix it without rewriting your tooling.
I Watched AI Generate a Perfect Todo App in 3 Minutes. Then I Spent 3 Days Fixing It.
AI generated a working app in 3 minutes. I spent 3 days rebuilding it. Not because the AI failed—because I didn’t specify what I actually needed. Here are the 8 questions I should have asked first.
The Junior Dev Paradox: We’re Speed-Running Past the Tutorial
AI tools let juniors skip the tutorial and ship features on day one. The catch: they’re also skipping the part where they learn to debug.
When Claude Code Goes Down: A Meditation on Modern Dependency
Let me paint you a picture. It’s this evening. I’m in the zone. Fingers flying across the keyboard, that beautiful flow state where you and your AI coding assistant are one harmonious bug-squashing machine. And then, without warning, without so much as a courtesy error message, Claude Code just… dies. Not the graceful kind of death where systems send you helpful notifications. Well, okay, they had a status page. There was technically a “we’re experiencing technical difficulties” message somewhere on the internet if you went looking for it. But in the moment? When you’re mid-keystroke and suddenly your AI copilot just stops responding? It just felt gone. Vanished. Disappeared like my motivation to manually write boilerplate code.
How to Secure Your Vibe-Coded Project (Before It Secures You)
Most developers ship without security audits. Here’s how to catch vulnerabilities before they become breaches.
10 Ways to Waste Time and Money with AI Agents: A Field Guide to Self-Sabotage
Money spent is obvious—we burn through tokens like a hedge fund manager through investor capital, exhausting our weekly quotas by Tuesday. Time, however, is subtle and invisible. Something I call the Anti-AI Paradox: that creeping realization that you could have hand-coded the entire feature in half the time it took to “collaborate” with your AI assistant. Let me save you some grief. 1. Being Super Vague AI models are getting smarter by the day. But they can’t read tea leaves like some digital oracle you summoned from Silicon Valley. “My ‘Schedule’ button isn’t scheduling the post.” Sure, Einstein. I can see that. Revolutionary observation.
The Indie Dev Edge in the Age of AI
AI can write you a thousand lines in seconds. Too bad it can’t read them for you. That’s still your job—and probably your superpower.
You should probably ditch your IDE
What if the real productivity upgrade isn’t another plugin—but a paradigm shift?
Be prepared to throw away your code
Why the best architecture might be the one you’re willing to throw away
What every indie dev should master before asking AI to build for them
How to stay in control when your AI starts writing code faster than you can think.
Your SaaS Will Break — Here’s How to See It Coming
What many founders realize only after their first outage.
A Saner Way to Use AI for Coding
Turns out, TDD was built for the AI age.
You’re Making Your SaaS Harder Than It Needs to Be
A few weeks ago, I spent an entire evening chasing a bug in a React component that refused to re-render. I tried useEffect. Then useMemo. Then stared at the dependency array like it had personally wronged me. Eventually, I fixed it — by restarting the dev server. That’s when it hit me: React wasn’t made for people like me. React was built for teams — with dedicated frontend engineers, design systems, review processes, and time to care about component hierarchies. I’m just trying to build a SaaS. Alone.
If I Were Starting a New SaaS Today, I'd Do This
Most SaaS projects fail because founders spend weeks on foundations instead of features. Here’s how to skip the scaffolding and ship fast.
Don’t write a CD pipeline yet
If you’ve never deployed by hand, you don’t deserve automation.
The Hidden Tax Slowing Down Indie SaaS Builders
Ship faster by thinking smaller, not fancier.
How indie devs can vibe code fast without sinking their own ship
The quiet tension between vibe and discipline.