You’ve felt it. That quiet, unsettling shift when you open your code editor or boot up a game engine, and the urge to build something from scratch is suddenly gone. Instead of writing the logic, you tab over to an AI chat. You type a prompt. The machine spits out the code. You copy. You paste. It works.
It should feel like a victory. Instead, it feels like you’re losing your mind.
We didn’t lose a skill; we lost the friction that made the skill worth having.
Recently, a thread on Hacker News asked if anyone else was losing their motivation to nerd out and tinker because of AI. The responses were a perfect split of cognitive dissonance. One camp complained that getting deep into technical problems is now ‘solved by a prompt.’ The other camp cheered: ‘The opposite is true for me! I always wanted to try Godot, and AI is helping me make that happen!’
But let’s look closer at that second camp. When you prompt an AI to write a Godot script, or set up your Home Assistant, or configure your LibreElec media server, you aren’t tinkering. You are supervising. You have become a middle manager for a very fast, very eager intern.
The people who say ‘AI helps me tinker more’ are lying to themselves. They aren’t process-driven tinkerers; they are outcome-driven builders. They just wanted to ship. And there is nothing wrong with wanting to ship—until you realize that the open-ended exploration, the late-night debugging, and the soul of the hobby are being quietly optimized out of existence.
The danger isn’t that the machine can build what you want, it’s that you no longer have to bleed for it.
Tinkering is inherently process-oriented. It’s about the struggle. It’s about spending four hours figuring out why a pointer is segfaulting, not because you need the program to run, but because the mystery is a puzzle you *have* to solve. AI is strictly outcome-oriented. It obliterates the struggle. It hands you the finished puzzle and asks, ‘Want another?’
When the friction is removed, the identity of the tinkerer evaporates. You are no longer a creator. You are a manager of AI outputs. And the worst part? Most people won’t notice the shift until the hobby they loved feels like a chore they are just overseeing.
AI is forcing you to answer a very personal question: Do you tinker to learn, or do you tinker to ship?
If you tinker to ship, congratulations. You now have a factory. But if you tinker to learn, to explore, to get lost in the machine—then you are watching your sanctuary get paved over by an autocomplete engine.
You can’t automate the struggle without automating the joy.
The real scarcity isn’t the ability to build anymore. The real scarcity is the desire to engage deeply when a prompt can produce the exact same artifact. If you let the AI do the bleeding, you don’t get to call yourself the craftsman. You’re just the guy holding the clipboard.
FAQ
Q: But if AI helps me finish projects faster, isn't that a good thing?
A: Only if your goal was the finished project. If your goal was the joy of figuring it out, you've traded a hobby for a delivery pipeline.
Q: How do I keep the tinkering spirit alive when AI is everywhere?
A: Intentionally pick problems AI can't solve. Work on hardware, physical builds, or obscure legacy systems where the friction is still real and the struggle is unavoidable.
Q: Isn't this just nostalgia for inefficient workflows?
A: No, this is about identity. Efficiency is for factories. Hobbies are for humans. If you apply factory metrics to a hobby, you kill the hobby.