AI Development

1. Because I Can Is Only Half the Answer

   Gen AI expands what I can contribute at 630 Volleyball. Choosing that work still means deciding where desire and ability meet.

   Oct 27, 20264 min read

2. The Hire Who Never Remembers

   People keep asking what kind of person is good at AI. My bet is a skill instead: the written half of management, the only half that reaches an agent's next session.

   Oct 19, 20268 min read

3. There's No Replicator Yet

   An AI agent did nearly all of a family member's data entry, missed one or two items, and almost got written off. All-or-nothing is a replicator's bar, and nothing I use with AI clears it yet.

   Oct 14, 20266 min read

4. A product prototype that carries its decisions

   A wedding product proposal became a public walkthrough, an interactive fictional prototype, and a planning handoff that carries the product decisions without exposing the original conversation.

   Oct 10, 20266 min read

5. Photography reports that help me choose

   A photography report becomes useful when it helps choose what to share or revisit, without mistaking browser activity for people, quality, or proof of growth.

   Oct 10, 20266 min read

6. Trying to teach an AI how I edit photos

   We built a Lightroom editing experiment and ran blind comparisons against a fixed recipe. The results led me to ask what the work had cost and why we kept going.

   Sep 29, 20266 min read

7. The Connector You Can't OAuth

   I asked the new Siri what it could infer from a week of texts. The answer was not a better chatbot. It was inference over a graph no OAuth connector gets.

   Sep 15, 20267 min read

8. Give Your AI a Reason for Every Design Reference

   A useful design reference may come from a completely different product. The work is identifying the decision it helps with, then telling the agent which part should transfer.

   Sep 9, 20265 min read

9. Who Is Still Driving?

   Using AI takes practice, but a product that needs an expert to catch its mistakes should say so before someone relies on it.

   Sep 6, 20264 min read

10. Rigorous About the Wrong Question

    I asked an AI agent to audit my app for the person it was built for. It sent five sub-agents to check documents and none of them looked at the screen.

    Sep 3, 20267 min read

11. The Audit Reproduced the Failure

    A small inspection of one runaway session became repeated parallel work before it had earned that expansion. The 119-of-118 report was the alarm.

    Aug 23, 20267 min read

12. Nobody Owns What the Agent Leaves Running

    My machine ran out of resources, so I handed an agent four screenshots and typed one word: fix. It did a good job. A day later, twenty-two connector processes were still running, every one of them marked disabled in config. Nothing had failed — and that turns out to be the interesting part.

    Aug 23, 20267 min read

13. Everything I Was Afraid of Worked

    Last October I published a post arguing that agent safety is an architecture problem: the model proposes, hard-coded code disposes, a human approves. Then I built exactly that for a youth sports club's website and used it for an hour. I found seven things wrong with it. None of them were in the part I had been afraid of.

    Aug 17, 202611 min read

14. There Was Never a Person in That Seat

    Fixed-task studies measure whether AI helps with familiar work. My repository history raises a different question: does AI change the range of work one person attempts?

    Aug 8, 20266 min read

15. The Loudest Voice in My Voice Corpus Isn't Mine

    A pipeline mines my agent sessions into a character sheet that gets loaded as context. The top-ranked correction in it is a deny message from a hook I installed, quoted back at me across 117 sessions.

    Aug 7, 20267 min read

16. The Cut You'll Make Twice

    A written rule is not a control until the system has a place to enforce it and a failure record that proves what happened.

    Aug 6, 20266 min read

17. The Style Guide Was Teaching the Tells

    I asked an AI to audit the style guides that teach AI to write like me. The tone card was describing machine messages, the guide's examples had become tells, and a checker was grading drafts for phrases the corpus abandoned months ago.

    Aug 3, 20266 min read

18. One Component I Didn't Already Have

    A coding-agent plugin with 66,000 stars keeps landing in my inbox. The version that could actually run on my machine ships eight components. Seven of them my setup already does, can't use, or would pay for twice.

    Jul 31, 20266 min read

19. Every Link Resolves. Nothing Checks the Number.

    A strategy document I ship can carry an invented figure through every automated check I built, as long as the sentences around it are well-formed and the links resolve. I went looking for that hole on purpose. Then I decided not to close it.

    Jul 30, 202613 min read

20. Nothing Broke. It Just Wasn't There.

    I went looking for a tool I'd built four days earlier and it was gone. It hadn't failed — it had run, found two real problems, and fixed both. Working correctly and existing durably turn out to be different properties, and running the thing only tests one of them.

    Jul 30, 20268 min read

21. I Configured My Agent to Agree With Me

    A rival model's review of my agent's work looked sharper — it pushed back, it demanded alternatives. So I ran a controlled experiment on my own harness: same model, same prompt, config on and off. The vanilla arm argued with me. Mine never did.

    Jul 20, 20267 min read

22. The Migration That Ate Two Columns

    I rebuilt a database table and it silently deleted two columns I needed. No error. Every test for the thing I was changing passed. Here's what actually caught it.

    Jun 16, 20264 min read

23. Red Is the Good News

    Three bugs that would have shipped clean. None of them threw an error. The only thing that caught them was a test written to fail first, against the real thing.

    Jun 16, 20265 min read

24. I Wrote the Rule Down. I Broke It Anyway.

    There's a file in my project whose only job is to stop me from making one mistake. I made it three times in a row. The difference between a rule and a wall.

    Jun 16, 20264 min read

25. The Gate Verifies the Work. It Never Looks at the Plan.

    Thirteen features shipped green. The designs were all wrong. The system made being wrong cheap—but only on one side of the work.

    Jun 16, 20265 min read

26. The Only Thing in My Codebase That Can't Lie

    I asked an agent a simple product question and watched it spend three thousand words rediscovering things it had no way to trust. The fix wasn't a better map. It was noticing which artifacts in a codebase can lie to you — and which one can't.

    May 30, 202610 min read

27. When Your Lawyer Tells You to Use ChatGPT

    My lawyer told me to use ChatGPT instead of paying him. A colleague said the same about his accountant. The cleanest signal for which professions get compressed isn't the headcount data — it's when the practitioner himself tells you he's optional.

    May 26, 20266 min read

28. The A/B Test That Built the Lathe

    I pasted a two-paragraph plan into a terminal and walked away for two days. The strategy package that came back was good. Then I asked Claude to do it again from a template, without me in the feedback loop. The template version landed at 70-80% of the quality in 10-15x less time. The gap — and the loop that closed it — has a name from another century.

    May 24, 20269 min read

29. The Scaffolding the Agent Doesn't Build

    I sent Adam Bender's Google I/O talk to Claude with a note calling it the most insightful take I'd heard on AI and our industry, and asked for a LinkedIn caption. The draft came back confessing things about my work that weren't true. The story of why is the same story Bender is telling on a Google I/O stage.

    May 24, 20266 min read

30. The Side Project Is Pottery

    I keep a drawer full of side projects I'll never ship. I used to tell myself they were portfolio, optionality, businesses in waiting. I don't believe that story anymore — and I don't think most of the people telling it believe it either.

    Apr 20, 202613 min read

31. Curation Is Not Composition

    Every creative medium that got cheap hit this moment. Art, music, publishing — all flooded, all eventually rescued by a curation layer that scaled up to match the garbage. Software is in the flood now. Curation isn't going to save it, and I don't think we've noticed the reason yet.

    Apr 17, 202612 min read

32. The Walk-In Is Full

    I ship an end-to-end project most Saturdays and put it in a drawer I never reopen. So does everyone I know. The walk-in is full — not with abundance, but with relocated scarcity. What looked like software culture was partly muscle memory, an involuntary reflex held up by cost, and it's atrophying now that nothing fires it.

    Apr 13, 202612 min read

33. When the Grid Goes Dark

    AI stopped being a tool the moment I couldn't work without it. That's not adoption — that's dependency. And dependency without understanding is just a blackout waiting to happen.

    Apr 6, 20268 min read

34. The MasterChef Problem

    AI gave everyone a professional kitchen. But MasterChef didn't make chefs by handing out equipment — it made them by designing challenges that exposed who could actually cook. Digital product development is missing the challenges.

    Mar 27, 20269 min read

35. Skip the Steps

    Supabase added a 'Copy prompt' button that bypasses their entire setup guide. It's a small UI change that reveals a big design shift — and it pushed me from 'context engineering' to 'probability engineering' as the real frame for agent-native tooling.

    Mar 25, 202610 min read

36. Setting Up an AI-Native Dev Environment

    The practical companion to 'What 223 Sessions Taught Me.' How to set up CLAUDE.md files, the memory system, custom skills, project-scoped conversations, and the infrastructure that makes AI-assisted development actually sustainable.

    Mar 20, 20269 min read

37. What 223 Sessions Taught Me About Working with AI

    I pulled 30 days of Claude Code session data — 223 sessions, 38,000+ prompts, 32 projects, 1.2 GB of conversation. The numbers tell a story about what AI-native development actually looks like when nobody's watching.

    Mar 20, 202610 min read

38. The 48-Hour Artifact

    I pointed an AI agent at a product initiative and didn't write a single line of code or a single word of copy. Two days later: 11 prototype pages, 4 strategic documents, cross-industry research with 30+ citations. And a trust problem I still can't solve.

    Mar 16, 202611 min read

39. The Jevons Trap

    Every productivity wave in software history expanded demand for developers instead of shrinking it. AI should follow the same pattern. Unless the thing it produces is just good enough to ship and just bad enough to compound.

    Mar 9, 20268 min read

40. The Source of Their Intelligence

    Someone made the argument that most developers were never really engineering — they were sourcing solutions from Stack Overflow and Reddit, and AI just swaps the supplier. It's an uncomfortable take. It's also not entirely wrong.

    Mar 9, 20267 min read

41. The Sommelier Argument

    Maybe the highest-value skill in the AI era isn't making or judging. It's matching — knowing what's right for this moment, this audience, this context.

    Mar 5, 20268 min read

42. The Taste Gap

    AI can produce endlessly. But it can't tell you what's good. That gap — between generation and judgment — might be the only thing that matters now.

    Mar 5, 20266 min read

43. The Identity Crisis of the Prompter

    We keep reaching for craft metaphors — chef, artisan, architect — because 'person who types instructions' doesn't feel like enough. Why?

    Mar 5, 20265 min read

44. Six Months After the Horizon

    I published a prediction deck about the agentic web last September. Six months later, some of it looks prescient, some of it looks naive, and the most important developments weren't in the deck at all.

    Mar 3, 20267 min read

45. What the Grind Was For

    One morning, three AI agents, and a year's worth of thinking compressed into a few hours. The result was exhilarating — and it surfaced a question I can't answer.

    Feb 22, 20268 min read

46. Show Your Work

    If you take away the LLM, could I still do this? The answer is complicated — and the complication is the point.

    Feb 22, 20267 min read

47. Red-Teaming the Metering Phase

    I asked Gemini to tear apart my own thesis. Some of the hits landed. Here's what I'm keeping, what I'm revising, and what I hadn't considered.

    Feb 20, 20269 min read

48. The Metering Phase

    Every major infrastructure technology goes through a phase where we carefully ration usage. AI is there now. The question is which of today's anxieties are transitional—and which become permanent disciplines.

    Feb 20, 20268 min read

49. The Seven Stages of AI Adoption

    From wide-eyed optimism to 'the AI is gaslighting me with kindness.' A field guide to the emotional journey every AI adopter takes—and the sycophancy trap waiting at every stage.

    Jan 29, 20267 min read

50. When the Voice Guide Becomes the Problem

    I wrote a voice guide to help AI match my writing style. It worked too well—the AI learned the example phrases, not the principles behind them. Here's how I fixed it, and what it taught me about the difference between describing a voice and understanding one.

    Jan 21, 20265 min read

51. Personal Trainer Energy

    Building with AI in public looks a lot like fitness content. I'm not sure how I feel about that.

    Jan 21, 20267 min read

52. The Graveyard

    How many ideas die in the space between waking and coffee? Vercel's Agent Skills announcement made me think about what changes when engineering judgment becomes installable—and who gets to build things when the execution gap narrows.

    Jan 21, 20264 min read

53. The Next Chapter: What Happens When You Try to Scale Intent-Driven Engineering

    I've spent six months proving that one person with AI agents can build what used to require a team. Now I'm joining Commerce.com to find out if that methodology survives contact with an organization.

    Jan 17, 202610 min read

54. The Cognitive Foundry, Part 2: What the Simulation Can't Teach

    I wrote about simulation replacing apprenticeship. Then I stress-tested the idea. The technical case still holds—but I was wrong about what matters most.

    Jan 16, 202610 min read

55. The Cognitive Foundry

    The consulting industry's apprenticeship model was never really about the work—it was about proximity to mastery. When AI handles the grind, how does anyone learn to become a partner? The answer is reshaping the entire profession.

    Jan 16, 20269 min read

56. The AI Analyst

    We're not short on people who can chat with a bot. We're starved for people who can deconstruct a business process into atomic units an AI can actually execute. That gap has a name now.

    Jan 12, 20269 min read

57. The Agentic Student

    College students aren't just using AI chatbots anymore. They're building automation systems, running local LLMs, and treating software engineering as a just-in-time capability. The 'Chat Terminal' era is over.

    Jan 10, 20266 min read

58. The Neuro-Symbolic Convergence

    When will I be able to type natural language in my terminal and have the OS just understand? The answer is 2026—but not in the way you might expect.

    Jan 10, 202612 min read

59. The Third Race to the Bottom

    Consulting has played this game twice before—with body shops, then offshore. Now AI is the new lever. But what if the pattern itself is the problem?

    Jan 7, 20268 min read

60. No Room for Tourists

    Wade Foster doesn't send memos about AI. He runs hackathons and show-and-tells. That distinction matters more than most CEOs realize—and it's the same thing I've been telling my own teams.

    Jan 5, 20269 min read

61. Is Python the New Assembly?

    In the 1950s, engineers resisted compilers because they feared losing control. Now we're hitting that same phase transition—except the 'assembly' we're abstracting away is Python itself.

    Dec 31, 20254 min read

62. The Kitchen I'm Looking For

    I don't need more Salesmen. I need a Sushi Master, a Pitmaster, and a Molecular Gastronomist. AI lets us return to the Guild—craftspeople in their own lanes, augmenting their own mastery.

    Dec 21, 20258 min read

63. Describe the Pear

    An LLM is the ultimate observer. Like the angels in City of Angels, it watches everything. But it cannot taste. That's both a gap and an opportunity.

    Dec 17, 20254 min read

64. The Tragedy of the Timesheet

    What if the billable hour isn't a business model—it's a coping mechanism? A way to avoid confronting that the thing we're selling might not be scarce anymore.

    Dec 16, 20259 min read

65. I Don't Want to Be a 10-Person Team of One

    I've been the bridge. Between strategy and code, between design and delivery. It's exhausting. And lately I've been wondering if exhausting is the same thing as valuable.

    Dec 14, 20254 min read

66. Q1 2026: The Integration Quarter

    Everyone spent 2024-2025 experimenting with AI features. Q1 2026 is when the survivors figure out what actually works—and kill what doesn't.

    Dec 3, 20256 min read

67. The Storefront That Builds Itself

    Every e-commerce platform is racing to add AI features. But what if the real opportunity isn't AI features—it's AI architecture? What if the store itself could generate in real-time?

    Dec 3, 20256 min read

68. The Side of Agentic Commerce We're Not Talking About

    I just finished writing a whitepaper on agentic commerce. It's solid work. But something started bothering me. There's a version of this future that looks less like 'shopping gets easier' and more like 'retail becomes a trading floor.'

    Nov 27, 202512 min read

69. The Netflix Paradox: Why Shopping Isn't "Streaming" Yet

    Spotify knows what song you want to hear next. Netflix queues up your next binge. But your favorite retailer? Still making you filter by Men > Shirts > Size L. After 15 years of personalization promises, why doesn't shopping work like streaming?

    Nov 25, 20255 min read

70. Toolmaker or Tool User: Finding Your True Nature in the AI Age

    Ive been wrestling with a question that won't let go: who's more valuable, me using the LLM or the people building it? After days of thinking, I realized I've been asking the wrong question entirely.

    Nov 24, 20257 min read

71. The Infinite Concierge: Why Agentic Shopping Is Just Old School Merchandising on New School Rails

    Agentic shopping doesn't change why we buy. It radically changes the cost of discovery and the precision of the pitch. The game is the same. The speed of the players has changed everything.

    Nov 22, 20257 min read

72. Field Notes: Real Patterns and Next Moves

    I'm not observing from the sidelines. I'm running these experiments in real time. Here's what's actually happening—and what I'm doing about it.

    Nov 12, 20259 min read

73. The Playbook: Tactical Moves for the AI Era

    If both bubble and build-out are real, what do you actually do? Here's what I'm seeing work—and what's failing—across different roles.

    Nov 11, 20259 min read

74. Bubble vs. Build-Out: Understanding the AI Moment

    I've spent months arguing AI isn't a bubble—it's infrastructure. Then smart money started betting against it. Both can be true. Here's what I'm figuring out.

    Nov 10, 20258 min read

75. AI Isn't a Bubble. It's Infrastructure.

    Hank Green says the AI industry is a bubble. I think we're looking at it wrong—what if AI isn't a product at all, but a foundational technology like electricity?

    Nov 9, 20257 min read

76. Intent-Driven Engineering: By The Numbers

    I built a $2.5M platform in 80 hours using GenAI tools. Heres what the numbers actually say about productivity, cost, and what happens when you stop pretending software takes as long as it used to.

    Nov 5, 202514 min read

77. The 'Do More With Less' Paradox

    If AI does all the junior work, where do the senior engineers come from? I used to see this as a pipeline problem. Now I'm wondering if we're not even using a ladder anymore.

    Oct 30, 20254 min read

78. My AI Agents Have Rules. They Break Them. So I Built a Cop.

    Instructions arent enough. To make agentic workflows reliable, I had to build a meta-agent to police my coding agents. Welcome to the unglamorous world of AI Ops.

    Oct 28, 20254 min read

79. Debunking the 'Svelte + AI' Myth: 69 Production Components Don't Lie

    Blog posts claim LLMs struggle with Svelte 5.' Our evidence? Two production apps, 69 components, and Agent-OS v3.0.0 optimized for Svelte. The data doesn't match the narrative.

    Oct 23, 20258 min read

80. "Agentic Software" Isn't Magic. It's a New Interface for an Old Problem.

    My feed is saturated with agentic software.' The promise is magic: autonomous agents executing complex, multi-step plans. But let's cut the hype. This isn't magic.

    Oct 21, 20253 min read

81. From Wearing Many Hats to Orchestrating AI Specialists

    The constant role-switching isnt a strength—it's a source of profound inefficiency. AI changes the model.

    Oct 2, 20253 min read

82. Four Questions That Expose Fake GenAI Expertise

    The gap between slick slide decks and the messy reality of building something that actually works is wider than most people realize.

    Oct 1, 20253 min read

83. From Asking AI Questions to Giving It Directives

    The shift from prompting to architecting—and why more powerful models demand a different kind of input.

    Sep 30, 20252 min read

84. Building for AI Agents Changes Everything About Your Technical Skills

    The shift isnt about learning to use AI—it's about learning to build for AI. That distinction changes everything.

    Sep 21, 20253 min read

85. What Actually Worked When I Let Multiple AI Agents Rebuild My App

    Clean specs, small tasks, a unified preamble, and ruthless guardrails. The model mattered less than the system.

    Sep 17, 20253 min read

86. What Shipping with AI Actually Looks Like

    Shipping means a real object changed in a real system. There is a link, an owner, a date, and a small metric that moved.

    Sep 4, 20253 min read

87. Measuring the Unowned Storefront: Observability for Agent Commerce

    Everyone is busy selling shovels. But the mine moved. Agents now sell on surfaces brands do not own. The win is not a better shovel. It is eyes and throttle on those agents: traces, attribution, consent, limits.

    Aug 27, 20259 min read

88. Why I Burned My AI-Generated App to the Ground (Again)

    You can rush with straw or sticks, but the only way to survive the wolf of drift and fragility is to build with bricks.

    Aug 17, 20252 min read

89. Why AI-Native Development Needs Building Codes

    Were in an AI development gold rush. The same historical pattern applies: unregulated innovation, followed by standards that make outputs safe and repeatable.

    Aug 12, 20253 min read

90. When I Asked the AI to Critique Its Own Framework

    Something broke, and instead of debugging the code, I asked the system why it hadnt caught the problem itself.

    Aug 8, 20253 min read

91. I’m Not Using GenAI. I’m Building a System Around It.

    Aug 7, 20253 min read

92. Who Checks the Foundation?

    Aug 5, 20252 min read

93. Designing What You Don't Build — And Building What You Can't Read

    The absentee software engineer.

    Aug 5, 20254 min read

94. The Work Before the Words

    Meta-Companion to "Living The Gap"

    Aug 4, 20252 min read

95. Behind the Scenes: Why We Had to Slow Down to Speed Up

    A simple bulk upload broke — 22 teams skipped, 0 created. The fix seemed easy. AI suggested patching the frontend. But that would’ve locked in a broken contract. Here's how we slowed down, re-architected the system, and avoided weeks of silent tech debt and wasted tokens.

    Aug 3, 20255 min read

96. What $800 in AI Credits Taught Me About Building

    I burned through $400 of Lovable credits and $400 of Kilo tokens. Then I burned the app to the ground.

    Aug 3, 20252 min read

97. 🌀 The Paradox of Velocity in AI Coding

    After sprinting through two weeks of AI-coded progress—and crashing into drift, chaos, and broken trust—I reset everything. This is the story of slowing down, building real structure, and defining a repeatable AI‑Ops workflow. From vibe coding to teardown, here’s what I learned.

    Aug 3, 20258 min read

98. When Intent Becomes the Source Code

    The past two weeks of AI engineering forced a shift I didnt expect—away from writing code and toward describing systems semantically.

    Aug 2, 20252 min read

99. What My JSX-Free React App Taught Me About AI-Assisted Engineering

    I still dont really know what JSX is. But if I'm asking AI the right questions, does it matter? Is this really different from architecting systems based on principles and relying on an engineering staff to understand the nuances?

    Aug 2, 20253 min read

100. Why My React App Doesn't Use JSX

     Most React apps are JSX-first. Mine isnt. That wasn't a bold opinion—it's just where I ended up after building a real system using AI as my primary coding partner.

     Aug 2, 20254 min read

101. I Still Don’t Really Know JSX. And I Don't Think It Matters.

     I built a production-grade React app—and still don’t fully understand JSX. In the AI-assisted era, syntax mastery matters less than system design. You’re not the coder anymore. You’re the architect. The real skill? Knowing what to ask, how to judge, and when the output doesn’t fit.

     Aug 2, 20253 min read

102. Why I'm Skeptical of Agentic AI (Despite Using AI Every Day)

     I use AI to code, test, document, and enforce rules. But I dont trust autonomous agents to plan and execute on their own.

     Aug 2, 20253 min read

103. Even the AI Is Confused

     What My Stack Audit Revealed About Modern Dev

     Aug 1, 20253 min read

104. Treating AI Prompts Like Jira Stories Changed My Workflow

     The realization: AI needs the same structured context that humans need to start work safely.

     Aug 1, 20252 min read

105. The Drift Beneath the Velocity

     Week 2 of AI-assisted coding brought velocity — but also drift. This post explores the moment I realized I was managing AI agents like a team, and what that means for the future of software consulting.

     Aug 1, 20254 min read

106. When Documentation Becomes a Contract Your AI Must Follow

     A styling bug taught me the difference between docs-as-code and docs-as-contracts—and why AI development demands the latter.

     Jul 31, 20252 min read

107. Skip the API: Building a Local ChatGPT Bridge for VS Code

     Can you skip the API and wire ChatGPT directly into VS Code? Turns out, yes — with a little browser magic. This post breaks down how I thought about building a local-first bridge that replaces Kilo and avoids token costs, all powered by curiosity and a builder’s mindset.

     Jul 31, 20254 min read

108. Building an AI-Driven E2E Testing Framework from Scratch

     Testing was my bottleneck. So I built a framework where AI writes, runs, and validates the tests.

     Jul 30, 20252 min read

109. From Copilot to Enforcer: The AI Maturity Spectrum for Developers

     Or: What happens when AI stops just helping you code — and starts holding your system accountable

     Jul 30, 20254 min read

110. Tool-and-Die Thinking for the AI Age

     How AI coding tools helped me beat the overhead wall — and build faster than I think.

     Jul 30, 20253 min read

111. Just-in-Time Software

     Just like cloud killed the server rack, AI is killing fixed tools. I built a full E2E test system from scratch—faster, cheaper, tailored—using nothing but schema, rules, and AI prompts. Why buy tools when you can generate them just-in-time?

     Jul 30, 20254 min read

112. Why Demo Mode Should Be a First-Class Feature

     Building a sandboxed demo environment taught me that onboarding isnt just UX—it's architecture.

     Jul 30, 20253 min read

113. Why I Built Feature Toggles Into the Bracket App

     Sometimes the feature isnt for the user. It's for the system operators—the ones who have to keep the app online when the fire starts.

     Jul 30, 20252 min read

114. When Fast Isn't Fast Enough: From AI Coding to AI Concurrency

     Theres a strange kind of bottleneck that only shows up after you've gotten fast. The only real blocker left is waiting for a model to finish one thing before starting the next.

     Jul 30, 20254 min read

115. Designing AI-Enforced Safeguards for Development

     After a few bugs slipped past my AI assistant, I redesigned the system to make safeguards automatic.

     Jul 29, 20252 min read

116. How I Made a Cache Bug Impossible to Reintroduce

     A dropdown bug became a lesson in building automated guardrails that prevent architectural drift—especially when AI is generating your components.

     Jul 29, 20253 min read

117. Who Reviewed the Reviewer?

     This post is about that realization. About what happens when AI becomes the default reviewer, and starts learning from its own reflections. We’re not just debugging code anymore. We’re debugging the system that teaches itself how to review.

     Jul 29, 20256 min read

118. Building a Production App Solo in Seven Days with AI

     The key wasnt using AI to write code—it was creating a system to govern AI's behavior, output, and role in the development process.

     Jul 28, 20253 min read

119. Tokens Are Dev Hours. Waste Is a Feature, Not a Bug.

     With AI development, waste isn’t hidden in team velocity or burndown charts — it’s itemized on your invoice. That’s not a flaw. It’s a feature.

     Jul 28, 20254 min read

120. The AI Engineer Has Joined the Team. Now What?

     AI isn’t just accelerating software development — it’s reorganizing it. This post unpacks what changes when you start designing teams, tools, and processes around a human–AI hybrid model. Planning shifts. Costs shift. Roles shift. The real question is: are we ready to shift with it?

     Jul 27, 20254 min read

121. How Structured Documentation Turned My AI Into an Engineering Team

     Documentation can be more than a reference—it can be a knowledge layer that both humans and AI agents use to build.

     Jul 26, 20253 min read

122. How Fear of AI Turned Into an AI Development System

     I started building with AI out of fear of being left behind. What I ended up with was a repeatable system for AI-driven development.

     Jul 25, 20253 min read

123. From Fear to Flow: How Building a Tournament Manager App Taught Me to Scale with AI

     I didn’t start with a strategy. I started with fear. Here’s how a grassroots volleyball app turned into my personal AI bootcamp—and the repeatable framework I built along the way.

     Jul 25, 20255 min read

124. My AI Engineering Team

     I didn’t set out to build an AI team. I just started with ChatGPT prompts for Lovable AI. Over time, it evolved into managing a layered squad of AI tools—architects, coders, and reviewers—working together like a real dev team. This changed how I work and lead AI-assisted projects.

     Jul 23, 20253 min read

125. When You Start to Hear the Music

     What happens when AI sharpens your mind, but drifts you further from those who don’t think that way? This post explores the private cost of clarity — and the quiet grief that comes from outgrowing the resolution your old relationships were built on.

     Jul 10, 20253 min read

126. From Pattern to People

     The hidden cost of clarity in an AI-shaped mind

     Jul 8, 20254 min read

127. Still Your Car. Still Your Wrench.

     What AI Coding Tools Don’t Tell You About Building Real Software

     Jul 6, 20254 min read

128. From Prompt to Pattern

     This post wraps my “Help Me Help You” arc and opens a new question: If precision makes AI more effective, does it also increase human disconnection? I’ve felt the drift. The next thread I’m pulling on is: how to stay human inside all this structure.

     Jul 2, 20253 min read

129. How I Work With AIs (And Why)

     A behind-the-scenes look at how I use GPT and Lovable together. One rewrites the prompt. One generates the code. I just define the intent — and stay out of the way. This isn’t a tech stack. It’s a new mode of working.

     Jul 2, 20254 min read

130. Prompt Strategists, Agent Orchestras, and What Comes Next

     Prompting is evolving into orchestration. One AI clarifies, another executes, a third checks the result. We’re entering an era where modular intelligence matters — and prompts become the interface between thinking systems.

     Jul 2, 20254 min read

131. When One AI Rewrites for Another

     Prompt rewriting isn’t just a clever trick — it’s becoming core infrastructure. From cloud tools to agent chains, we’re seeing a shift: one AI clarifies the ask, another executes. The result? Fewer errors. Smarter systems.

     Jul 2, 20253 min read

132. Help Me Help You (Help Me)

     One AI helps another do its job better. I use GPT to rewrite prompts for Lovable — cutting errors, saving time, and revealing a deeper pattern: intent → refiner → executor. This isn’t just prompt cleanup. It’s the start of a new architecture.

     Jul 2, 20254 min read

133. How I Used One AI to Train Another: A Tactical Reset in Data Architecture and AI Tooling Strategy

     Like most devs experimenting with AI tools, I’ve found myself juggling multiple platforms, APIs, and half-understood schemas to build things faster. Sometimes it works. Other times, it works against you.

     Jun 30, 20254 min read

134. $50 of AI Later: Lessons from Burning Credits Fast

     AI credits vanished quickly, highlighting hidden costs and forcing clarity into my development process. Here's how a $50 investment turned into a practical blueprint for smarter AI‑assisted builds.

     Jun 29, 20256 min read

135. The Lost‑Phone Test for AI: Could Your Org Still Function Tomorrow?

     Dropped phone, lost life. Same test applies to corporate AI: if your copilots vanished tomorrow, would work even slow down? The “Lost-Phone Test” exposes integration gaps and makes the case for a Chief Intelligence Officer to weave tools into real workflows.

     Jun 28, 20253 min read

136. Overnight Dev: From Rage-Quit to Release in 72 Hours—With AI Riding Shotgun

     Burned-out coder to live app in one weekend: two failed scrapers, one hidden JSON API, and AI tools that scaffolded the rest. How DevTools + GPT turned AES volleyball data into an MVP—and why your next Jira ticket might build itself.

     Jun 27, 20253 min read

137. It’s Time for the CIO 2.0

     Most AI conversations start in the wrong place — with tools, not capabilities. What’s missing isn’t another pilot. It’s a new executive role: someone to steward how your organization thinks, learns, and evolves.

     Jun 27, 20253 min read

138. From Shutdown to Speedrun

     The Cost of Surviving the Age of Constant Upgrades

     Jun 25, 20255 min read

139. You’re Sending Self-Driving Cars Down Unmarked Roads

     AI doesn’t fail because it’s bad — it fails because your data lacks the infrastructure it needs to navigate. Language models don’t just search — they interpret. Most orgs haven’t built for that.

     Jun 23, 20254 min read

140. ChatGPT Doesn’t Eat—So Why Do I Keep Asking It to Cook?

     LLMs can draft the menu, but you still have to taste the sauce. Here’s my field-note recipe for closing the fidelity gap between what ChatGPT writes and what actually works.

     Jun 18, 20254 min read

141. The Cake Is a Lie: Why AI Isn’t Ready

     Everyone says AI can build for you — that you just describe the thing, and it ships itself. But I actually tried. I took it seriously. And what I found was brittle, inconsistent, and full of guesswork. If it took this much effort to build a landing page, what happens when the stakes are higher?

     Jun 17, 20254 min read

142. Signal Reflex → Signal Dispatch

     Signal Reflex is now Signal Dispatch — a shift from sensing to sending. Same voice, sharper intent. This is where ideas go out.

     Jun 16, 20251 min read

143. Driving While Not Driving

     (How to Keep Moving Without Losing Yourself)

     Jun 15, 20253 min read

144. The Machine Loom

     If humans are the loom, AI is the thread—fast, abundant, and increasingly tangled.

     Jun 14, 20253 min read

145. I Built a Site Just to See If I Still Could

     I didn’t need to build the site from scratch. That was the point.

     Jun 14, 20253 min read

146. How Content and Commerce Actually Connect Now

     Your content is the storefront. If it’s not reducing friction or moving someone closer to a decision, it’s not connected to commerce at all.

     Jun 13, 20252 min read

147. The Sky Is Not Falling

     I built the core Let’s Pepper site in under 2 hours—then spent over 8 trying to get one visual detail (the section dividers) to look right. AI can prototype, but it doesn’t ship. This post breaks down why the real work happens after the first draft, and why experience still matters more than ever.

     Jun 12, 20252 min read

148. Coaching Without Coddling: How I Support High-Potential People Without Micromanaging

     Once I know someone’s worth investing in, I shift gears. Here’s how I coach without taking the wheel—and why presence matters more than pressure.

     Jun 12, 20253 min read

149. How We Find the Ones Who Just Get It

     Hiring the right consultant isn’t about checking boxes. It’s about building the kind of process that makes the right people show up—and lets the wrong ones opt out early.

     Jun 12, 20253 min read

150. When the Tools Get in the Way

     We made websites easier to build by hiding the code. But now that AI can write that code for us, the abstraction layers are becoming the new friction.

     Jun 11, 20253 min read

151. The Role of Self-Awareness in Every Tool I Use

     I don’t chase tools anymore. If it fights my instincts or adds ceremony, I’m out. If it sharpens my clarity, it stays. That’s the filter.

     Jun 9, 20253 min read

152. How I Structure My AI Workflows to Support Real Thinking

     My AI workflow isn’t about speed—it’s about clarity. Here’s how I use LLMs to shape messy ideas and reduce drag when I need to think straight.

     Jun 5, 20253 min read

153. Why I Use AI Every Day (And Why I Started Writing About It)

     I didn’t use AI to go faster—I used it to catch up with myself. This blog is where that journey turned into something useful and real.

     Jun 4, 20252 min read

154. Grid-Level Thinking Wasn't the Plan

     This wasn’t meant to be a thought leadership series. It started as a phone call—and a question: Where does AI actually help, right now, for real? I’m Not Hyping AI. I’m Just Using It.

     Jun 4, 20252 min read

155. Power Without Purpose Is Just a Bill.

     Post 4 of 4 in the Grid-Level Thinking series—why using AI for real work has changed how I design systems, think about leverage, and clarify what actually matters.

     Jun 4, 20253 min read

156. Plug In. Then Rethink the System.

     Post 3 of 4 in the Grid-Level Thinking series—adopting AI isn’t the hard part. Redesigning your system around it is.

     Jun 4, 20252 min read

157. Wired for Power: Everyone Got the Current. Not Everyone Built the City.

     Post 2 of 4 in the Grid-Level Thinking series—access isn’t the differentiator anymore. Application is.

     Jun 4, 20251 min read

158. Wired for Power: AI Is the Grid. You’re the Architect.

     Post 1 of 4 in the Grid-Level Thinking series—what we miss when we treat AI like magic instead of infrastructure.

     Jun 4, 20252 min read

159. The Entry-Level Developer: Evolution, Not Extinction

     The junior dev role isn’t dying. It’s evolving. The job is no longer about churning out syntax—it’s about navigating ambiguity, thinking critically, and collaborating with AI. Here’s what still matters, and how to coach for it.

     Jun 4, 20252 min read

160. How I Built Signal Reflex in a Week

     This blog isn’t a new habit—it’s just a new slice of my output. Here’s how I launched Signal Reflex in a week by treating it like any other creative drop: strategy, tools, publishing cadence, and what I learned by shipping.

     Jun 4, 20253 min read

161. Start Smart, Not Perfect

     Jun 2, 20252 min read

162. How I Use AI in Consulting (For Real)

     Jun 2, 20252 min read

163. Why I Started Signal Reflex

     I didn’t start writing to build an audience. I started because AI helped me get past the blank page. This is where I work through what matters—before it fades.

     Jun 2, 20252 min read

Looking beyond essays? Search all writing