I say the question isn't if you use AI to build you something, but if you nerd out and tinker yourself.
Same how you're not a musician just because you had Suno create something.
So, no, sticking to the actual meaning of a thing is not true scotsman fallacy.
In this analogy, the person calling themselves a musician would have to be falsely calling themselves a programmer after using AI to code something. The word used here was "tinker" which can be any number of things. One can "tinker" with business ideas, investment theses, hardware designs, economic models, gameplay concepts, baking recipes, brewing formulas, and more.
For other tinkerers, the tinkering is accomplishing an objective or building a thing. That's maybe Matthias Wandel.
I used to be like you (when I was a pro coder), and now I'm more like Matthias (I have a homestead and a small business). You're welcome to write the code and enjoy yourself that way. I want to enjoy the thing I've built, with the help of AI. You can say I didn't build it, I don't really care--my ego isn't wrapped up in it.
So if I outsource all the work to some guy on fiverr am I also a tinkerer?
(Depends what you're building, of course)
Those are not tinkerers then, as there's no tinkering involved. Or there might be in other parts (e.g. with electronics to hook up and house the code AI wrote for you, if it's something that will run on a Raspberry Pi), but not in the coding part.
The question implies: "do you still enjoy nerding out and tinkering by writing code yourself, now that AI can write it". Else asking if you're demotivated from doing it "because of AI" wouldn't make sense.
So I would say that "I like making stuff by having AI write the code" is still an admission of not nerding out and tinkering (regarding code) anymore.
This seems closed minded view of tinkering. There are plenty of ways to tinker aside from just writing code. It could be in driving traffic to a website, selling a product, combining datasets, automating a task, etc.
I personally love economics and have used AI to tinker with combing multiple datasets to create new ways of viewing economic growth at the metro level across variables.
Matthias is obviously a tinkerer.
The post didn't say anything about code, maybe you didn't notice that.
If the guy didn't write any code, don't you still think he's a tinkerer? I do. Don't you think he's nerding out? I do.
I'm using AI to mess with all kinds of things I didn't do before AI. Like working on 90s Ford trucks.
If you've narrowed the scope of the question, or narrowed the definition of "tinkering" to require writing code, I'm just left scratching my head.
If you're using AI (to wit: another tool) to nerd out and tinker, then you're obviously not losing that motivation.
So my genuine answer to the original question is: No, I nerd out and tinker more than ever.
Right now, I am using AI as a tool to do stuff I otherwise wouldn't do, like reverse engineer a Whoop band for use with Apple Health sans a Whoop subscription.
I have way more hard problems that engage me then ever.
I do both human and AI coding. The former more to learn and mold my mind around a problem. The latter when I feel I am ready to delegate to a junior dev.
I think of AI coding like how I’ve operated as a principal engineer at a company. It works well when you study the problem well enough to know precisely what you want. That often requires actual hands on technical work IMO. The coding isn’t for the machine, its not even to ship, it’s to help me think. Then I have a basis to really understand and care about the details. I can micromanage agents to do what’s expected at this point.
Part of the fun is solving puzzles where the coding agent gets stuck and me then giving it technical direction. Especially when an agent says that something cannot be done in software (I show them how it actually can be done).
I am in the more motivated than ever camp.
For me, I'm more interested in learning the internals of systems (How do locks work, and why do we need them? How does VFS work?) and making experimental implementations in learning OSes (for sure I don't have the technical skills to implement the ideas in production OSes). AI helps by being a very good search engine, but other than that it doesn't help much, as I completely block code generation from an AI agent. Everything is discussion only.
I now have Home Assistant established at home. LibreElec for a home media server. Time lapse camera for home mushroom growing. Wine steeping projects. And much more.
To really get motivation, u need to spend the correct amount of time of understand and make your hand dirty when it is necessary. I noticed that if I try before by myself, I understand what I am doing, and after I just optimize the code using an LMM, it is way more motivating
Some highlights:
* a proxy (and reverse proxy) is 3 words on a web server configuration object that supports many such proxies on many such web servers
* it can send 6,000,000 web socket messages per second per socket (or 5,000,000 per second roundtrip with responses)
* it can log everything
* none of it was written with AI. The one time I used AI to validate some absurd performance results the AI took a lot of education to follow the code only to reaffirm my incorrect conclusion
On the other hand there are new techniques like keeping the agents on track and imagining about which things now became possible.
But the real tinkering: In real life with real physical work.
With AI, if there's software I wish existed, I can make it happen without making it an unpaid second job.