231 karma · joined August 29, 2026
Teslas are death machines which should be treated as such.
More ambitious would be valuing the software we write today more in terms of quality. Not using LLMs to generate more code so that we can do large amounts of largely unjustifiable work.
More ambitious could mean scrapping the lowest common denominator processes that enable bad software like scrum. Like corporate "code review" that is just a rubber stamp because noone cares. Like junior developers who refuse to learn and insist they are always right and force garbage code into the system. Like business people who instead of working with engineering teams engage in sidelong hacks to avoid the process.
The cultural/organizational/process/tooling forces that create bad/mediocre/barely passable (from all perspectives) software are everywhere.
Life sucks on software island. Because WE made it suck and we continue to LET it suck.
As for gitlab...yuck. But whatever. Most of the dev tool space is really just "sh* we have to put up with now", none of it is any good, all of it is dated from the early aughts, and taken as a whole is even worse because none of it works together.
While software development itself got better in the last ten years these tools stayed the same or got worse (enshittification). And this is part of why folks are self hosting.
The other part is that AI is destroying the Internet and its time to pack your bags anyway. The smart people already have.
When Apple cant sell you the same exact thing over year after year, what you get is pretty rough.
In fact I lost real any desire to "work in chat", its never been a good experience its just a place to hide from email. Waste time in chat, make jokes in Chat, bitch to my manager in chat ok. Work in chat? F-that.
The only way you can get work done in a place that uses (abuses) Slack is to turn off notifications and forget it. Its a distraction app and nothing more.
People who have wired in their CI and AWS Alarms and metrics, I feel sorry for you. You took the bait.
So yes teams is a red flag. Slack is a flag of a different color. When you take a companies stack in as a whole, it will (no matter where you are) remind you of how TRULY SHITTY software products are. And that should humble you so you dont go add to the pile.
I dont think the author is right to say it because of all the vibe coding that this is pointless.
I think it might be pointless because we are witnessing in essence the destruction of computing itself. And writing code with or without AI will eitehr not be possible (hardware unavailable) or become so unsavory and unenjoyable (jobs nobody wants) that computing for any reason but subsistence (or world domination) will die.
Its even conceivable that the platforms LLMs generate all this code for (the web, mobile, desktop) will die.
Also I been thinking about how we can (re?)create offline open source or fully obfuscated OSS online that has some kind of tooling to prevent exposure to training.
It would be interesting if there was a metaphor we all understand but we could repurpose for this. Undoubtedly new CPUs would need to be made.
First they forced their malware bot farms on us, now they want to rent them to us so they can turn the entire web into the dark web.
And eventually rug pull off the major retail sites and just redirect traffic to their own darker sites to scrape commissions, sell direct and keep the change.
I'm sure the teams thinking this up buy their lunches from a ghost kitchen run by illegals that's never had a health inspection,
located in the back of a laundromat with a phony business license and website that only accepts crypto.
Why would you?
Dont change. Software developers do not have to change anything they control their means of production and we dont HAVE to use any of this stuff. IF you are saying that there will be non-engineers willing to step in to hit enter (as in the business/product people) and LLMs will be good enough to do with it, Im ok with that.
I encourage business people to go down that path, especially since I have no organizational responsibility to help them. So if they run into even one little issue, I wont look at their code, I wont let it into a repo and I can just walk away.
There will be people who cross over and will want to help the people using LLMs and some will be technical. But it wont be in large numbers and it will be based on extraction and not pay very well at all. It will pay less every day as the LLM usage goes up to the CTOs desk.
More power to them! At the end of the day someone WILL have to hit enter, and it wont be me in some low paid slopshop.
What Im saying is the industrys future and mine are not intertwined. The tech industry is of no interest to me as a software engineer. They have jumped their own fake shark.
Anyway, nothing has changed for me, except that I dont have to deal with google search results anymore for things. When the LLM gets stuck I do still go out there. But its rare.
Nothing has changed in the way I do my job, except having to put up with slop from people around me, or from business people pushing slop towards the dev team and wanting a pat on the back for it. That part has changed for the worse.
The complete willingness to traffic in nonsensical documentation that doesnt represent any real requirements as an excuse for doing a job is pretty sad, and I take note of who does it and I make sure to never trust anything they publish. And usually stop reading it.
I call it "crossing over", once I see someone do it and replace their work product with LLM slop and distribute it, they have created a barrier that will prevent me from working with them forever.
Sorry, garbage in garbage out doesnt fly. I feel sad for open source maintainers having to deal with this massive slop-ageddon.
So maybe they are trying to create an infinite loop among agents intentionally so that they overwhelm systems requiring humanity to call on the tech industry to "save the human race".....
You might as well take an old iPod and stick it to the wall. (Yes I said iPOD, not iPad)
The biggest difference in experience with seniors is that we already know the standard patterns, I dont have to ask what the inside of a microservice looks like, or the inside of a react app. Or how event driven systems work.
Engineers should learn that stuff by doing. And reading the massive amount of (non-LLM) written documentation on the subject. Written by real people.
When someone says "Didnt lose its...", A mine that is shutdown is a loss, because its no longer financially viable to operate. So are we debating what "lose" means?
Open up any old idled steel plants lately?