Knowledge Base
Deep dives, tutorials, and research notes on the things I build with — AI, the web platform, accessibility, and system design.
For decades, an idea and a shipped product were separated by a painful canyon of skill, capital, time, and permission. AI is quietly collapsing that gap — and the new bottleneck is no longer technical capability. It's decisiveness.
Engineers who once celebrated automation are suddenly suspicious of AI coding — “did you really build it?” We asked the same about Python, about C, about compilers. What we call craftsmanship is often just familiarity wrapped in nostalgia.
Three years ago engineers asked which JavaScript framework to bet on. Today it's which AI stack will still matter in six months. Different nouns, same anxiety — and the exhaustion is no longer technical. It's existential.
AI mutates in public — a tool you mastered in three weeks gets replaced over a weekend. But the real problem isn't intelligence, it's cognitive bandwidth. You don't need to know everything about AI to benefit enormously from it. Trying to is the fastest way to learn nothing deeply.
Smart people are starting to confuse speed with wisdom. You can generate a strategy deck in twenty minutes and ship code before lunch — but synthesis is not understanding. You can outsource thinking; you cannot outsource the part where meaning gets made.
The most valuable person in your life is rarely the smartest one in the room — it's the one who gets you before you finish the sentence. Intelligence has become abundant. Understanding has not. So the better question isn't “How do I compete with machines?” but “Am I becoming someone who truly understands people?”
Showing 6 of 6 entries.
