Think about it: everyone has characterized AI slop, as slop. Which means that we negatively value it in terms of originality. Combine that with the fact that there will be a lot of it, this means that original work will 1. stand out or be very distinct from slop, and 2. have its value amplified as a result of this polarization.
basically, we value originality more AND are able to identify it more readily.
related is also the fact that originality will literally be valuable as training data for future models
Also there have been dozens of HN submissions and comments where the poster didn't even bother to remove the em dashes. Most people just don't care. The people who continue to post like this wouldn't have been as visible had they not discovered AI and pounced on it, but they were always there. The idea of posting with an AI voice, em-dashes and all, would likely have still appealed to them if you'd asked 5-10 years ago. Nowadays it takes hardly any energy for them to have a persistent voice.
Slop has always been around. AI has cheapened its creation.
If something is able to generate things with soul and true originality... we're talking about something incredible, a new intelligent species potentially
think about how in music, when an artist comes out with something original and awesome, and then everyone starts copying it and creating their own derivative works, like Jimi Hendrix or something.
Did Hendrix become useless? Did everyone end up thinking he sucks or something? No, he is even more revered, as the originator of a new type of sound that probably created multiple genres
The same thing applies here. Originality will be valued and even empowered as extrapolation and development off of it can increase in speed and quality in the case you mention
True, but some nuance is that a LOT of artist/creative types lean exclusively on the mechanical skill needed to create, without anything really much to say. They also very frequently copy other's styles, etc.
I'm not defending AI pumping out crap, but this also shows a lot of folks don't have much to offer beyond the mechanical aspects and we shouldn't glorify churning out stuff by hand as high art either.
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.
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.
Is it not engineering anymore even if you micromanage and relegate the machine to a better typist, following patterns and doing research around?
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.
Take woodworking for example. When I build a kitchen cabinet, I can get lumber that's already smooth and treated, I can buy drawer tracks, I can use power tools instead of a handsaw and a screwdriver, I can use a pocket hole jig to make joints easier. I still have to do more planning and assembling than with the Ikea cabinet, which also takes more work than having a contractor do everything for me.
I'm doing it my way because it's fun for me. Other people might enjoy other parts of the process - or different things altogether.
There's a whole spectrum between doing everything from scratch and paying someone to have it done for you.
It's actually quite similar to buying the services of a programmer off Upwork to build something for me, only with LLMs it's way cheaper and faster, with a shorter feedback loop.
What do you think architects do? Or interior designers? Or civil engineers?
Architecture certainly isn't building, and neither is interior design. Civil engineers calculate and specify the loads in excruciating detail, because if they didn't, people would die.
You can accomplish most of that by installing Syncthing.
But the objection is that you’re not really building anything new even if you think it’s a new idea. By your definition you’re building for yourself and not sharing…so what good are your little projects. Reading your original list it just seems like you want to build and run software without having to do any research, even if a solution already exists.
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.
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.