Exactly. And I was never particularly good at coding, either. Pairings with Gemini to finally figure out how to decompile an old Java app so I can make little changes to my user profile and some action files? That was fun! And I was never going to be able to figure out how to do it on my own. I had tried!
Fair enough. But that particular could be anything that has been bothering you but you didn’t have the time or expertise to fix yourself. I wanted that fixed, and I had given up on ever seeing it fixed. Suddenly, in only two hours, I had it fixed. And I learned a lot in the process, too!
It's just fun in a different way now. I've long had dozens of ideas for things I wanted to build, and never enough time to really even build one of them. Over the last few months, I've been able to crank out several of these projects to satisfactory results. The code is not a beautiful work of art like I would prefer it to be, and the fun part is no longer the actual code and working in the code base like it used to be. The fun part now is being able to have an app or tool that gets the job I needed done. These are rarely important jobs, just things that I want as a personal user. Some of them have been good enough that I shipped them for other users, but the vast majority are just things I use personally. Just yesterday for example, I used AI to build a GTK app that has a bunch of sports team related sound effects built into them. I could have coded this by hand in 45 minutes, but it only took 10 minutes with AI. That's not the best part though. The best part is that I was able to use AI to get it building into an app image in a container so I can distribute it to myself as a single static file that I can execute on any system I want. Dicking with builds and distribution was always the painful part and something that I never enjoyed, but without it, usage is a pain. I've even gone back to projects I built a decade ago or more and got them building against modern libraries and distributed as RPMs or app images that I can trivially install on all of my systems. The joy is now in the results rather than the process, but it is joy nonetheless.
I have a 10-year-old side project that I've dumped tens of thousands of hours into. "Ship the game" was an explicit non -goal of the project for the vast majority of that time. Sometimes, the journey is the destination.
I yearn for the mindset where I actively choose to accomplish comparatively little in the brief spells I have to myself, and remain motivated. Part of what makes programming fun for me is actually achieving something. Which is not to say you have to use AI to be productive, or that you aren't achieving anything, but this is not the antithesis of what makes programming fun, only what makes it fun for you.
Ultimately it's up to the user to decide what to do with his time ; it's still a good bargain that leaves a lot of sovereignty to the user. I like to code a little too much ; got into deep tech to capacities I couldn't imagine before - but at some point you hit rock bottom and you gotta ship something that makes sense. I'm like a really technical "predator" - in a sense where to be honest with myself - it has almost become some way of consumption rather than pure problem solving. For very passionate people it can be difficult to be draw the line between pleasure and work - especially given that we just do what we like in the first place - so all that time feel robbed from us - and from the standpoint of "shipper" who didn't care about it in the first place it feels like freedom. But I'd argue that if anyone wants to jump into technical stuff ; it has never been so openly accessible - you could join some niche slack where some competent programmers were doing great stuff. Today a solo junior can ship you a key-val that is going to be fighting redis in benchmarks. It really is not a time to slack down in my opinion - everything feels already existing and mostly already dealt with. But again - for those who are frustrated with the status-quo ; they will always find something to do. I get you however that this has created a very different space where past acquired skill-sets don't necessarily translate as well today - maybe it's just going to be different to find it's space than it was 10 years ago. I like that the cards have be re-dealt though - it's arguably way more open than the stack-overflow era and pre-ai where knowledge was much more difficult to create.
I think it just depends on the person or the type of project. If I'm learning something or building a hobby project, I'll usually just use an autocomplete agent and leave Claude Code at work. On the other hand, if I want to build something that I actually need, I may lean on AI assistants more because I'm more interested in the end product. There are certain tasks as well that I just don't need to do by hand, like typing an existing SQL schema into an ORM's DSL.
I’ve got kids and so seldom find myself with the time or energy to work on something. Cursor has really helped in that regard. I have an extensive media collection of very large VR video files with very unhelpful names. I needed to figure out a good way to review which ones I wanted to keep and discard (over 30TB, almost 2000 files). It was fun sitting using Cursor with Claude to work on setting up a quick web UI, with calls out to ffmpeg to generate snapshots. It handled the “boring parts” with aplomb, getting me a html page with a little JavaScript to serve as my front end, and making a super simple API. All this was still like 1000 lines and would have taken me days, or I would have copied some boilerplate then modified it a little. The problems Claude couldn’t figure out were also similarly interesting, like its syntax to the ffmpeg calls were wrong and not skipping all the frames we didn’t want to generate, so it was taking 100x longer to generate than was necessary seeking through every file, then I made some optimizations in how I had it configured, then realizing I’d generated thumbnails for 3 hours only for them to not display well on the page as it was an 8x1 tile. At that point Claude wanted to regenerate all the thumbnails and I said “just display the image twice, with the first half displayed the first time and the second half displayed the second time, saving myself a few hours. Hacky, but for a personal project, the right solution. I still felt like I was tinkering in a way I haven’t in awhile, and a project that I’d never have gotten around to and instead have just probably bought another new hard drive, took me a couple hours, most of which was actually marking the files as keep or delete. I ended up deleting 12TB of stuff I didn’t want, which it felt cool to write myself a bespoke tool rather than search around on the off chance that such a thing already exists. It also gave me a mental framework of how to approach little products like this in the future, that often a web ui and a simple API backend like Node making external process calls is going to be easier than making a full fat windows UI. I have a similarly sized STL library from 3D printing and think I could apply mostly the same idea to that, in fact it’s 99% the same except for swapping out the ffmpeg call to something to generate a snapshot of the stl at a few different angles.
I enjoy noodling around with pointers and unsafe code in Rust. Claude wrote all the documentation, to Rust standards, with nice examples for every method. I decided to write an app in Rust with a React UI, and Claude wrote almost all the typescript for me. So I’ve used Claude at both ends of the spectrum. I had way more fun in every situation. AI is, fortunately, very bad at the things I find fun, at least for now, and very good at the things I find booooring (read in Scot Pilgrim voice).
I think there can be other equally valid perspectives than your own. Some people have goals of actually finishing a project instead of just "tinkering"... and that's ok. Some say it might even be necessary.
This matches my experience. A recent anecdote: I took time during a holiday to write an Obsidian plugin 4 years ago to scratch a personal itch as it were. I promptly forgot most of the detail, the Obsidian plugin API and ecosystem have naturally changed since then, and Typescript isn't in my day-to-day lingo. I've been collecting ideas for new plugins since then while dreading the investment needed to get back up to speed on how to implement them. I took a couple hours over a recent winter holiday with Claude and cranked out two new plugins plus improvements to the 4 year old bit-rotting original. Claude handled much of the accidental complexity of ramping up that would have bogged me down in the past--suggesting appropriate API methods to use, writing idiomatic TS, addressing linter findings, ...
I'm finding that too. I have old stale projects that I'm hesitant to try and fix because I know it will involve hours of frustrating work figuring out how to upgrade core dependencies. Now I can genuinely point Claude Code at them and say "upgrade this to the latest versions" and it will do most of that tedious work for me. I can even have it fill in some missing tests and gaps in the documentation at the same time.
You just described my experience exactly. Especially the personal side project time as a parent. Now after bed I can tinker and have fun again because I can move so much more quickly and see real progress even with only an hour or two to spend every few days.
Yes! I feel like so many people really fail to appreciate this side of things. Heck, Suno has gotten me to the point where I play so much more piano (the recording -> polished track loop is very rewarding) that not only did I publish an album to Spotify in my favorite genre, of music that I’m really happy with, I’ve also started to produce some polished acoustic recordings with NO AI involvement. That’s just because I’ve been spending so much more time at the piano, because of that reward loop.
Yep, have seen this myself as previously a manager and now with a young family. I can make incredible progress on side-projects that I never would have started with only 2-4 hours carved out over the course of a week. There is a hopefully a Jevon's paradox here that we will have a bloom of side-projects, "what-if" / "if only I had the time" type projects come to fruition.
I was very anti AI (mainly because I am scared that I'll take my job). I did a side project that would have took me weeks in just two days. I deployed it. It's there, waiting for customers now. I felt in love with the process to be honest. I complained my wife yesterday: "my only problem now is that I don't have enough time and money to pay all the servers", because it opened to me the opportunities to develop and deploy a lot of new ideas.
I experienced the exact same thing: I needed a web tool, and as far as I could tell from recent reviews, the offerings in the chrome extension store seemed either a little suspicious or broken, so I made my own extension in a little under an hour. It used recent APIs and patterns that I didn't have to go read extensive docs for or do deep learning on. It has an acceptable test suite. The code was easy to read, and reasonable, and I know no one will ever flip it into ad-serving malware by surprise. A big thing is just that the idea of creating a non-trivial tool is suddenly a valid answer to the question. Previously, I know would have had to spend a bunch of time reading docs, finding examples, etc., let alone the inevitable farting around with a minor side-quest because something wasn't working, or rethinking+reworking some design decision that on the whole wasn't that important. Instead, something popped into existence, mostly worked, and I could review and tweak it. It's a little bit like jumping from a problem of "solve a polynomial" to one of "verify a solution for a polynomial".
I was just getting pretty sick and tired of programming, instead now AI can write the code down while I do the fun things of figuring out how shit works and general device hacking + home projects
I recently used AI to help build the majority of a small project (database-driven website with search and admin capabilities) and I'd confidently say I was able to build it 3 to 5 times faster with AI. For context, I'm an experienced developer and know how to tweak the AI code when it's wonky and the AI can't be coerced into fixing its mistakes.
Numbers don't matter if it makes you "feel" more productive. I've started and finished way more small projects i was too lazy to start without AI. So infinitely more productive? Though I've definitely wasted some time not liking what AI generated and started a new chat.
From one personal project, Last month: 128 files changed, 39663 insertions(+), 4439 deletions(-) Range: 8eb4f6a..HEAD Non-merge commits: 174 Date range (non-merge): 2025-12-04 → 2026-01-04 (UTC) Active days (non-merge): 30 Last 7 days: 59 files changed, 19412 insertions(+), 857 deletions(-) Range: c8df64e..HEAD Non-merge commits: 67 Date range (non-merge): 2025-12-28 → 2026-01-04 (UTC) Active days (non-merge): 8 This has a lot of non-trivial stuff in it. In fact, I'm just about done with all of the difficult features that had built up over the past couple years.
I kinda feel the same way, don't get me wrong, I'm a developer at soul level, I absolutely love programming, but I love more getting shit done, automating things, taking the human out of the equation and putting the computer to do it, AI lets me do that. I work in cybersecurity as a WAF admin, my job is 100% that, but I'm also the only developer so anything that needs to be scripted or developed I get to do it. One week I created 4 different scripts with Gemini Canvas to automate some tedious work, it took my I don't know, 3 hours? Instead of 1 or 2 weeks? Yeah sign me in.
AI makes finishing projects easier. But I would steer away from starting them. In order for me to be comfortable with a code base and consider it mine I need to have written the foundation, not merely reviewed in. Once the pillars are there, LLMs do make further development faster and I can concentrate on fun details (like tinkering with CSS or thinking about some very specific details).
> But I would steer away from starting them. I find just the opposite. Before, starting from nothing was a huge impediment. Now you can have a working prototype and start iterating right away. If you figur e out that you've gone down the wrong path, there's little remorse in tossing it out and starting over.
Setting up build system and prototyping sure. As a replacement for Figma it’s great. But I would throw away all the code and start from scratch if I wanted to be able to maintain the code in the long term.
My guess is that the amount of total software people use will significantly increase, but the total amount of money made from SaaS will significantly decrease I've replaced almost all of the App subscriptions with stuff I built for my self. The only subscriptions I pay for are things that are almost impossible to replace like online storage (iCloud) or Spotify
I really agree with this. For me it just feel so much more fun and rewarding to build my weekend projects, especially those projects where I just want to produce and deploy a working mvp out of an idea. If trying out a new framework or whatever I find it quite the opposite though, that AI removes all the fun parts of learning (obviously)
As someone who always dabbled in code but never was a “real” developer, I’ve found the same thing. I know the concepts, I know good from bad — so all of a sudden I can vibe code things that would have taken me months of studying and debugging and banging my head against the wall. If you’ll forgive a bit of self promotion, I also wrote some brief thoughts on my Adventures In AI Prototyping: https://www.andrew-turnbull.com/adventures-in-ai-prototyping...
More related to the title, i've found the same. I was always an aggressive pixel-pusher, so web dev took me AGES. But with shadcn + llms I'm flying through stuff, no lie, 5-20x faster than I was before. And i dont hate it anymore
One thing is true: now I go to the bar with the other guys in the group, drink whatever and let Claude or Codex do the work while I supervise, then merge PR in the morning... I wish I was kidding, but for non critical projects this is now a reality
Strong agree! Forget all those studies that say “but developers are slower” or whatever — I’m actually building way more hobby projects and having way more fun now. And work is way more fun and easier. And my node_modules folder size is dropping like crazy!
Like, fine, here's a personal example: I wanted to build a system that posts web links I share to a bot account on the fediverse. That seemed like a fun result to me. I wanted to self-host the links, so I installed Linkding. (I didn't write Linkding.) For the fediverse bot, I installed gotosocial as the service host (I didn't write gotosocial.) From there, a cronjob running a small program using Linkding and gotosocial APIs could do the trick. Decided to do it in golang, because the standalone binaries are easy to deploy. Writing that small program didn't seem like fun - I've already played with those APIs and golang. What I wanted, for my enjoyment, was the completed system. So, I took 10 minutes to write out a quick spec for the program and what I wanted it to do. I loaded that up as context for Claude Code along with some pointers for building CLI apps in golang. I let it rip and, in about 20 minutes, Claude produced a functional tool. It also wrote a decent README based on my original prose. I reviewed the code, did some testing, made some tweaks, called it done. My bookmarks are now regularly posted to a bot account on the fediverse. This is an enjoyable outcome for me - and I didn't have to type every line of code myself. For bonus points, I also had Claude Code gin up some GitHub Actions workflows to lint, test, build, and release multi-platform binaries for this tool. I've done these things before, but they're tedious. More enjoyable to have the resulting automations than to build them. And now I have them: I can make tweaks to this tool and get builds just through the GitHub web UI. I've since repeated this pattern with a handful of other small personal tools. In each case, I wanted the tool and the utility it offered. I didn't care about the process of writing the code. It's working pretty well for me.
I agree with this. I've been able to tackle projects I've been wanting to for ages with LLMs because they let me focus on abstractions first and get over the friction of starting the project. Once I get my footing, I can use them to generate more and more specialized code and ultimately get to a place where the code is good.