The problem is that LLMs inherently lack the virtue of laziness. Work costs nothing to an LLM. LLMs do not feel a need to optimize for their own (or anyone’s) future time, and will happily dump more and more onto a layercake of garbage.
This is an insightful point I haven’t seen made before. I’m going to start referring to vibe code as “subprime technical debt”
I’m in between 3 and 4: both copyright and copying are amoral (they are just tools), but copyright as it exists today is obsolete, arguably to the point that it actively hinders the betterment of humankind.
Based if true
Is it the attacks themselves that have become a daily occurrence, or the detection thereof?
I’m fully talking out of my ass here, but I feel like a quick “five whys” exercise at any given company would reveal that the real issue is neither engineers nor code, but rather something systemic.
deleted by creator
The bit about people bringing their laptops to the beach smells like RTO propaganda
In this economy?
Maybe the real slop was the code we wrote along the way
Well, yeah, as soon as you start trying to turn your hobby into an income stream, it becomes a job. That’s 100% on you. You’re allowed to just do something because you enjoy it.
Its always DNS
Personally I’d say every single product and service being transparently wrapped in a personal information honeypot
Follow-up question: why do AI companies so often have buttholes for logos?
I guess despite how intimidating it seems, un-fucking vibe code can be approached just like every other complex programming problem: by breaking it down into smaller problems and solving them incrementally.
I generally like content that highlights small indie releases, I’m just a little put off by the way it’s presented here. It feels contradictory to the community description in the sidebar.
It sounds to me like you have two viable options:
Accept that your role at the company is now “prompt ‘engineer’” and do your best to optimise your workflow for quick turnaround, since the business is prioritising speed. If you want to do programming, start a personal project.
Optionally, you can think about how to frame the issues with code quality in terms of financial risk to leadership–but be prepared for them to continue not giving a shit (and maybe start viewing you as “not a team player”).
Find a new job.
Makes about as much sense as linking a top 10 FOMO list in a patientgamers space 🙃
In case anyone else is curious, the essay is simply titled “On Noise.”
Edit: here’s a Project Gutenberg link