For example, I want to make:
- A mini OS on top of SeL4
- A UI framework based on SolidJS, for native apps, in rust.
- My own photo manager (which can do backups & sync across all my devices). And a gallery to share photos with friends
- A local first data store, built on top of CRDTs
- My own programming language
And lots more.
Each of these projects on their own would take months of time. If LLMs can speed up development, that's great! I don't care if nobody else uses what I make. I want a personal computer full of my own software.
I actually want less software for myself. Less things to maintain. I've become a "digital minimalist" in that I use very few software, only ones maintained by others who can afford and are willing to keep them working.
There are a ton of opportunities available right now to make new things. And make them better, more customizable, and more sovereign.
To the replies: be the change you want to see in the world, guys. That may be trite but focusing only on the negative will just make your own life shitty.
For example, the photo backup system I want to make will let me manage my ~400gb photo library. I want my library backed up on a couple devices, running linux and freebsd. I want my mac and iphone to have a local mirror of all the favorited photos, and when I'm at home, I want to be able to browse all photos from those devices by streaming them over the local network. I want native macos & ios app interfaces to view and manage all that.
I don't know any existing software that meets my requirements. I don't think any such software exists. Apple, Dropbox and Google will solve this problem for me if I store all my photos in their cloud and pay them an ongoing subscription for the privilege. I'd much rather make something myself, and back up my photos on my own hard drives.
Making something like this is simple enough, but very time consuming. If claude can take the drudgery out of it, well, I think that's just delightful.
AI is seen as a way out of drudgery but you're just trading one problem for another.
Is it not engineering anymore even if you micromanage and relegate the machine to a better typist, following patterns and doing research around?
Since you said you want to make those things that you list, I assume none of these things have been built yet. If so, I would encourage you to consider how excited you will be to constantly maintain those things you build. But even if the maintainence cycle won't be as exciting, since you are the sole user you have the advantage of being able to proceed at a leisurely pace even while doing maintainence work.
In a professional setting, the dopamine hit of being able to build something quickly that works in an area that you have little to no knowledge in makes you more dependent on the AI in the maintaince cycle as you want to chase that dopamine high by maintaining the same development speed. This in turn leads to a bigger burnout crash after that peak dopamine hit. Maintainence is a phase of diminishing returns even without AI, but when your coding agents are introducing new bugs at record pace with their bugfixes with no new features to write home about you are in a special place in Hell.
I'm all for using AI to build ambitious projects. I have yet to see a person/company/organization continuously release huge software endeavours in a stable professional manner day in and day out with a coding agent harem in tow.
If something like the Ladybird browser, or any browser that is "built by scratch", achieved Chrome parity in six months and consistently maintained the same level of stability with continuous releases then I would see that as proof that this approach has become professionaly sustainable.
The reason people are getting away with so much using AI is because of the open secret in most enterprise engineering practices: the customer cares more about the response time for fixes they report than they do about overall or longterm product quality.