945
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Jul 2026
945 points (100.0% liked)
Programmer Humor
32422 readers
1019 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
letting your agent run commands without reviewing them first is peak stupid
Creating an environment that incentivizes not thinking is peak stupid.
I for one welcome that change. Let them sloppify their brains once the rug is pulled and token cost skyrockets (or AI isn't able to fix its own fuckups) the human developer will rise again.
*after the ensuing recession/greater depression...
"I'll be swimming in jobs if I don't starve first!"
Basically this. If the starving gets to intense, switching professions it will be.
I'm not so sure about that. Kids need access to PCs in order to gain tech skills and they're trying hard to take that away.
That is true. Unfortunately also true is companies not hiring juniors anymore because AI does their jobs. The companies somehow believe seniors grow on trees or something.
The thought is that other companies can grow the seniors.
Doesn't fucking work when everyone's doing it but I can tell you that at least round me that was starting to happen even before AI. Maybe 10% of companies would hire juniors.
Now they're lobbying the government to be able to import seniors from developing countries because "we need better talent in our own country"
I would like to strangle some CEOs. And those aren't even big companies, this is Estonia not Silicon Valley lol
It looks bad in the short/medium term, but the bubble will pop, it's only a matter of time until memory prices come down again and we move past the insanity of burning tokens like there's no tomorrow. I don't mean to downplay this though, lots of people and companies are struggling because of the AI bubble and the rush to build datacenters.
The bubble will pop, but I'm not convinced the hobbyist PC hardware market is going to recover.
Realistically, the consumer market for PC components existed because there was a business market for desktop computers as employee workstations. That's mostly dead now. Businesses mostly buy laptops or mini PCs for employee workstations, they have less and less need for desktop hardware because most of the computing tasks have moved to SaaS platforms. The consumer PC hardware market isn't that profitable on its own, it exists on the margins of production for business purchasing, and it's been coasting on momentum built up in the 2010s.
Processor architectures are changing to support machine learning tasks, GPU production is shifting toward ML-specialization, and everyone in the design field is trying to remove the barriers between the CPU and the RAM, which means shortening the path, which means getting rid of the socket and end-user upgradability in favor of soldered components. With SaaS taking over everything in the business world, we're trending back toward the mainframe computing model and away from powerful local hardware.
I'm not saying there won't be a consumer PC market in the future, I'm just saying that it will be different. There won't be enough demand for common desktop components to keep the custom PC build market alive as it was five years ago.
I think it depends on what happens in countries like China, as they develop more productive capacity in sectors like memory and graphic cards the prices will eventually go down, I hope they keep the components separate for non-datacenter customers but I guess time will tell, and sadly you might be right
Having production credentials in a dev environment is more stupider but they'll never learn because they outsourced their thinking.
The thing is Claude would have told them that too, it probably did tbh and they just clicked right through the warning
Dev cycles now.
Everyone has a development environment, but not everyone has a separate production environment.
This is almost certainly the case of dev happening in the live environment.
I think you meant to flip that. The only time one has a dev with no prod is prior to first release.
If environment is the live one, that's production not dev. Using it for development doesn't make it a dev environment. It means you only have prod.
It's a sarcasm about corporate spending decisions. The joke is:
The point being that if management has decided not to spend resources on a test environment, then "production" is in fact test.
Claude code even added an auto mode so that you don't get blocked by that pesky reviewing anymore. Since then, the usual mode of asking before running a command, for instance when the thing wants to read the entire codebase looking for information only available in an online doc, is now called manual mode; the non 10x developer mode.
Cursor just added this too. Some auto mode which is "safe" because of some sandbox bs.
Took me 10 mins to find how to turn it off. And they keep trying to sneak it on again.
At least twice a week I have to cancel it when it asks to run something which will fuck things up.
.envfiles are wild to me, environment variables have never been a good way to pass data to applications, let alone secret data.So the solution people came up with was to store them in plain text next to the binary, and then have a loader apply them before running the main app.
But they needed those .env files to transplant an entire software stack from the developer's laptop into production in a reproducible manner! How else were they ever going to get software into prod? By good documentation, broad version requirements, and following the Robustness Principle? Ha! How are you supposed to move fast and break things then?
What's the point of AI if you need qualified review?
Normally, speed. Especially if you aren't a picky writer; which you should be; for scenarios like this one.
It’s still so much faster. An experienced engineer spoon-feeding the AI the exact logic/algorithm to use is still faster than writing it by hand. I think a lot of people stopped early when AI was worse and/or before they started being good at using it.
Ah yes, faster spaghetti. Wonderful.
If you’re getting spaghetti it’s a skill issue.
If you vibe code, sure you’ll get slop. Ask it to do something to get X result, you’re leaving it room to think so you get slop. Tell it exactly what logic you want it to use, step by step like it’s a child, then you get the same you’d do yourself but faster.
Look at the PRs for quality-critical projects like the linux kernel and I guarantee you coudn’t tell which PR has some AI and which does not.