Programming insights to Storytelling, it's all here.
I've tried vibe coding. It did not work for me. I think the problem is that I'm an actual developer, and I feel dread running code I don't understand. As Andrej Karpathy, who coined the term, described it, vibe coding is about fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists. He talks about asking LLMs for "the dumbest things" because he's "too lazy to find it," accepting all changes without reading diffs, and simply copying error messages in until they're fixed.
I was trying to experiment making an animation using the HTML Canvas and JavaScript. After drawing a small image and creating a game loop, I noticed my laptop fans whirring to life. The more I worked on my little animation, the louder my fans became. In fact, I didn't even finish my experiment, and I got a notification for low battery. What was it about my tiny 512x342 animation that made my powerful modern computer choke?
The 2010s was the Wild West of the mobile world. "Mobile-first" was the buzzword, much like "AI-first" is today. Every company, from the biggest social media giants to your local pizza parlor, seemed to be pestering you to download their app. There was a genuine hype train, and everyone was on board. The apps, frankly, were always mediocre, and a far cry from the full functionality of their website counterparts. But the message was clear. If you weren't on mobile, you were falling behind.
When companies publicly announce on LinkedIn that they're embracing AI, what are they actually doing internally? Are they replacing developers with agentic AI that swarms through code, debugging errors and deploying fixes? Are they parsing business requirements, accessing repos, building features, and deploying them before the 9am standup? For outside observers, it's hard to tell. But as a developer, I can assure you there's often a disconnect between what a CTO says and how the day-to-day workflow is actually affected.
Every time I join a new company, I wonder how their code ends up becoming so complex. You’ll see an application that is supposed to do a simple task turn into a monstrosity that everyone is afraid to update. Writing simple software is often the goal, but somehow we go astray. Tl;dr: Dedicate significant time to refinement *without* adding new features.
So, I call myself an AI skeptic. But honestly? It's more accurate to say I’m a technology skeptic in general. Before you picture me churning butter by candlelight, boycotting smartphones, or mailing handwritten letters, let me clarify: skepticism isn’t rejection. It’s a pause, a thoughtful question: Does this actually solve a real problem, or is it just the latest shiny new hype cycle?
How many terms and conditions did you agree to today? If you're like most people, you probably signed up for a website and clicked "I agree" without reading a single word. We all do it. Yet, what if these documents we collectively ignore are actually legally binding and could be used against you in court?
In The Expanse, humanity’s sprawling interplanetary empire rests on a single, elegant piece of fiction: the Epstein Drive. This miracle engine effortlessly defies physics, allowing ships to accelerate continuously, cross the solar system in mere days, and make far-flung Ceres as accessible as a commuter suburb. The show’s true genius lies in its grounded illusion: it layers the Drive with convincing jargon, detailed specs, and plausible limitations ("the Tori models can’t sustain 5G burns for more than 12 hours"). You’re genuinely tempted to believe it because the entire world feels engineered, not simply dreamed up.
Remember Bryant Gumbel? Back in the mid-90s, as the digital world began its explosive growth, the then-Today Show co-host famously dismissed the internet as a passing fad. "I'm online, and I think it's a fad," he declared, suggesting we'd all soon forget about it. History, of course, seems to have mocked him. The internet is now the bedrock of modern life.
At some point, in any company, there is always a new process introduced. This process promises to make things better, safer, and more efficient. In theory, it's brilliant. On paper, it addresses all the potential pitfalls. But then, it hits the real world, and what sounded like a stroke of genius becomes a bureaucratic nightmare, often leading to the exact opposite of its intended outcome.
