this post was submitted on 24 Jun 2026
349 points (99.4% liked)

Technology

85739 readers
4726 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
 

Archive link: https://archive.ph/NaK7K

top 50 comments
sorted by: hot top controversial new old
[–] Aceticon@lemmy.dbzer0.com 36 points 1 day ago* (last edited 1 day ago) (2 children)

Anybody who has worked through the life-cycle of large projects knows that as time passes and the software gets adjusted and expanded, code just accumulates problem and brittleness - especially because multiple different people change it and they tend to each do it their way, often without full understanding of the code base - not just at the code level but also at the software design level - and eventually that code gets so hard to change or fix that a whole new system has to be built from the ground up.

In my experience this happens maybe at around 5 - 8 years of age of a codebase.

So I expect we're headed for a spectacular industry-wide explosion because using AI code vastly accelerates this because for just about anything but small projects that can entirelly be generated in one go, AI isn't consistent in coding style, much less software design.

Throwing software engineers at it right now only works if they end up spending even more time reviewing and ajusting the AI code than they would if they did the work themselves, since having AI coding is pretty much the equivalent of outsourcing to a pool of random junior developers.

[–] Buddahriffic@lemmy.world 14 points 1 day ago

Hell, even with smaller projects, you're going to have debug cycles and if AI is driving those cycles, it will be acting as a new coder for each invocation (which happens multiple times per prompt for systems like claude code).

So you'll get shit like duplicate helper functions, other code not using those helper functions anyways, debug code added and then not removed, errors and warnings using a variety of styles, overly verbose and redundant arguments, support for enhancements that don't even make sense in that context, confidently incorrect assertions about what is and isn't happening or possible, etc.

My manager wants me to make a presentation that sells some AI debug solution but the hand holding I have to do for it to actually understand and not give useless conclusions means I don't even believe in it. Or the case where it did help, turns out it didn't even use the tools provided by the solution and was just CC.

I've mentioned the cycle of being impressed with what these LLM-based systems can do and feeling like I might have been unfairly critical, and then running in to a major issue that justfies the earlier critical view. Last times I mentioned it, I said I was in the impressed (but skeptical) part of the the cycle. Well, I'm back to the "this might just be a complete waste of resources" part of the cycle.

[–] anon_8675309@lemmy.world 10 points 1 day ago (1 children)

I wonder how many engineers they’ll have to pull out of retirement in a few years to fix a lot flawed logic.

[–] Aceticon@lemmy.dbzer0.com 4 points 1 day ago* (last edited 1 day ago)

I remember back in the day when they had to pull Cobol programmers out of retirement to update mainframe software because of Year 2000 and they got paid a bundle for it.

Similar thing for customization of older SAP systems after SAP changed the language used to Java but those systems were still done in the old language.

So I expect that freelance senior designer-developers are going to get paid A LOT of money to come fix things in a few years' time, especially since in places with high AI adoption this is going to be way bigger in terms of size, complexity and seniority of expertise needed that either mainframe code updating for Y2K and updating customizations in old SAP systems.

[–] masterspace@lemmy.ca 62 points 1 day ago* (last edited 1 day ago) (2 children)

Cory Doctor's recent book on Centaurs and Reverse Centaurs is worth reading.

The core idea of that is that centaurs are a human top and machine / alien body, they're effectively augmented humans with all this technology to help them excel.

Reverse Centaurs are human bodies and machine / alien tops, where the humans are just checking the work of systems and are subservient to them. He points out that that's one of the fundamental differences between Amazon and the Postal Service is that in the case of Amazon drivers, they basically function as a reverse Centaurs where they are just an appendage of the delivery car, tracked and managed by that car, to do the tasks the car can't do on its own.

[–] HugeNerd@lemmy.ca 9 points 1 day ago

Imagine being a horse waking up with a human torso and micropenis.

[–] gandalf_der_12te@feddit.org 16 points 1 day ago (1 children)

very interesting concept. another example might be railway drivers who are merely appendices to the vehicle. the vehicle largely drives itself, the driver is mostly there to check tickets, answer passenger's questions, etc.

[–] some_kind_of_guy@lemmy.world 7 points 1 day ago (1 children)

We used to have elevator operators

[–] bold_atlas@lemmy.world 41 points 1 day ago* (last edited 1 day ago) (3 children)

lol sure they are.

They're desperately trying to pump this AI shit up with these fake stories before they go public

Investors really are dumber demographic than MAGA.

[–] 87Six@lemmy.zip 1 points 10 hours ago

Investors really are dumber demographic than MAGA.

Hey don't slander my investor bros. We put our money in a passive index fund just so we don't lose to inflation. We dgaf as long as inflation doesn't beat our savings.

It's the stock trader morons that you really want.

[–] jj4211@lemmy.world 11 points 22 hours ago

Well, they are, but not for the takeaway the article gives. The article is so close, but fails to extract the accurate conclusion.

First are what he calls the "lazy" engineers — workers who rely heavily on AI to write code, answer questions, prepare updates, and complete tasks with minimal engagement.

Then there are the "craftsmen," experienced engineers who bear the burden of understanding, reviewing, and fixing the growing flood of AI-generated code.

This is accurate. You have a set of "developers" who just need to make a good showing on the telemetry, whether it's "tokens used" and/or prominence in commit activity. They are not held to account on actual productive outcomes, just that they supervised a credible volume of AI activity. If the AI generates code and tests and the AI is satisfied that the code passes the tests, then their job is done. You have another set of developers that have to live with the nightmarish consequences of the first, because they just generated a pile of shit that would have been better not to exist at all.

'The craft they loved is dead'

Wrong takeaway, the craft is alive, but mismanagement is diluting it with bullshit.

Incidentally, this isn't new, but the magnitude is new. I have had significant segments of my career consumed by management insisting that I somehow make the bottom dollar offshored developers "productive", and similar pattern, if they "looked busy", management was happy, and management didn't care about whether the work was useful, because frankly they couldn't tell. They could tell if some volume of "stuff" was happening and they just settled on that, and if the "stuff" alienated customers, well that was the fault of those "craftsmen" for failing to properly manage the output from the "lazy" engineers.

[–] MonkderVierte@lemmy.zip 15 points 1 day ago

Investors really are dumber demographic than MAGA.

Herd behavior.

[–] kescusay@lemmy.world 182 points 2 days ago (19 children)

Software engineer, here. Yep, the burnout is real. I consider myself fortunate, however; with the skyrocketing cost of AI, my employer has been urging us to do as much as possible by hand lately to cut back on token usage.

I think that's pretty much where the entire industry will go soon.

[–] Xuntari@programming.dev 7 points 1 day ago (1 children)

I really hope you're right. My company is still in the "use as much as possible" phase, and my manager is quoting Jensen about "you need to use half your salary on tokens!". I'm looking for other work, but everyone is looking for vibe coders at the moment it seems...

I've gone from really loving my job, to hate my life.

[–] kescusay@lemmy.world 5 points 1 day ago (3 children)

Mo Bitar had a bit of advice that I think is applicable here: Lie. Claim to be an extreme 10x vibe whatever. Put "AI enablement" (whatever the fuck that means) in your LinkedIn profile. And wherever you get hired, commit to using enormous amounts of tokens as they require.

Then just... write code. Oh, definitely use the LLMs, too, but not for anything important. Set them to work writing BASH scripts or something. Get them burning through tokens to summarize all the corporate documentation you can find. Have agents creating agents to test the output of other agents and report to more agents on what the agents are doing. Meanwhile, do real work. Make sure that for every PR, you have the AI do one thing on it, to give it that code-slop shine.

Sucks that this is where we're at, but it is what it is.

[–] jj4211@lemmy.world 4 points 22 hours ago (1 children)

I've had LLM generate so many web sites about various random animals I've crammed into a prompt. No one wants web sites about those random animals, but my management is pleased at my token utilization.

Can do my real work and get praised for my actual productivity, and burn the tokens to get praised on AI adoption...

[–] kescusay@lemmy.world 1 points 9 hours ago

Clever! And when sanity starts reasserting itself at your company, you can claim you're focusing on saving the company money by reducing your token usage and just... make fewer animal slop websites.

[–] kkj@lemmy.dbzer0.com 1 points 16 hours ago

AI commit messages for artisanal code.

load more comments (1 replies)
[–] MasterBlaster@lemmy.world 32 points 1 day ago* (last edited 1 day ago) (3 children)

Huh. Maybe I will have a shot at getting a job... Oh, wait, I have 35 years experience, am over 50 and have been unemployed for 16 months. Never mind.

I gave up the humiliating shit show called a job search 3 months ago, and frankly my last job killed any interest in software development anyway.

It's all idiots telling professionals they're wrong and incompetent while blaming them for the ongoing production failures we solved and explained every month for a year but still can't get the code past review because "it does too much". 30 fucking lines of code "does too much". Pompous morons.

We're a threat of competence, and they're excising us relentlessly. I will laugh bitterly as I watch the soon to be torrent of fiascos and lamentations these idiots spout while still finding a way to blame software engineers.

[–] Valmond@lemmy.dbzer0.com 1 points 9 hours ago (1 children)

Hey are you me?!

Yeah I wonder how low I will go for a job, it's not bright exactly...

[–] MasterBlaster@lemmy.world 1 points 1 hour ago

If, like me, you took it on faith (at the age of 23) that social security will be gone by the time I retire, you have been saving and investingcas much as possible. Then you can get by on low-end work.

Remember, jobs don't really give you prestige. A job is a job. The issue is whether it can help you pay your bills or not.

Note that Social Security is slated to not have enough money for full payments 3 years before I'm due to enroll (for full payments). You'd think I'd have earned Millions with my precognitive skills.

¯_(ツ)_/¯

[–] kescusay@lemmy.world 5 points 1 day ago (1 children)

I'm sorry that happened to you. I've also seen it happen to a lot of very good engineers I've known over the years. It's truly insane. I know some people who've had to dip into their 401k accounts early just to keep their heads above water, and it's going to be an economy-wide disaster soon.

[–] MasterBlaster@lemmy.world 2 points 1 hour ago

Yeah, I didn't want to retire yet, but like my father before me, the choice was not mine. I saved enough that I should be able to actually retire and survive on part-time low income jobs. Unless the market crashes for a year straight cuz after that I got to start selling stocks.

load more comments (1 replies)
[–] emmanuel_car@fedia.io 44 points 2 days ago (1 children)

Yeah based on WYEA’s articles recently I would say that is the case. As providers move to token based billing, trying to find a way to break even, the rising costs will lower usage, which will probably then drive up costs further as the (imaginary) capital has already been spent on the DCs.

[–] wonderingwanderer@sopuli.xyz 3 points 21 hours ago

Waiting for that glorious bubble to burst now that they've successfully landed the public with holding the bags

load more comments (16 replies)
[–] mereo@piefed.ca 119 points 2 days ago (5 children)

That makes sense. Software engineers have gone from being artists (because yes, software architecture is an art) to becoming AI managers. It's demoralising.

I believe open-source software will continue to provide a refuge for artists.

[–] Feathercrown@lemmy.world 20 points 1 day ago

Yup. I'm watching my artform die in real time. Not only will my career no longer exist in the form I enjoy it, but the art form itself will die. Nobody is going to appreciate artisan code like they do other forms of art.

[–] pinball_wizard@lemmy.zip 22 points 1 day ago

I believe open-source software will continue to provide a refuge for artists.

Yes. My work is open source, and pretty unchanged. We get some AI pull requests now that take longer to review than doing the work ourselves.

I think a key difference is that there was never any tolerance for bullshit in my team's code base.

We don't have thousands of points of boilerplate, or a big pile of "not invented here" crap code.

So we don't have somewhere for the AI to really shine.

[–] turkalino@sh.itjust.works 48 points 2 days ago* (last edited 2 days ago) (2 children)

I wholeheartedly agree with you that code can be art but I was never able to express myself on that level at my corporate jobs. I was always limited to writing code that aligned with the company’s rigid style guide, and never allowed to implement new design patterns that would’ve improved things but deviated from the way things were done in the existing codebase.

Thus, I’m not too miffed about being forced to use coding agents at work because writing corporate-sanitary code already felt like a robotic process before LLMs existed. Personal hobby projects and open source contributions are where we can express ourselves freely and create our art the way we want to. They’ll never be able to take that from us.

[–] wizardbeard@lemmy.dbzer0.com 22 points 1 day ago* (last edited 1 day ago) (4 children)

You worked places with style guides? Did... Did you have a real testing environment that wasn't prod too?

I got taken off a project recently for being too direct about how the rest of the team was just spray and praying entirely AI generated code with no standards or review whatsoever, and they were charging ahead like it was a race to implement features we hadn't even discussed if we wanted/needed.

If you can't tell me how it works, you can't confirm that we actually need it, you can't tell me the upstream and downstream effects (or confirm they don't exist), and you can't even confirm that we even want it to do the thing it only supposedly does, then we have better things to do than go on a wild goose chase trying to debug it when there's a looming deadline for things that legitimately do not work that we need. Stop vibe coding and actually review the existing shit for fucks sake. If the requirements have never been clear, solve that instead of generating more slop. Maybe update some of the existing documentation instead of having AI wholesale hallucinate entirely new not quite right ones over and over.

Anyway, please tell me more happy development bedtime stories. I need to chase away the nightmares.

[–] themaninblack@lemmy.world 2 points 22 hours ago

I feel seen. I’m trying to sort out how to socialise the idea that we should be working with a broader context in mind. Hard to break habits.

load more comments (3 replies)
[–] Zarobi@aussie.zone 15 points 1 day ago (5 children)

Most of my career I was allowed to write code how I wanted. I made it beautiful and nice to read. It was genuinely fun to find the best way to implement each feature.

My final job, I was forced to add semicolons on new lines for each if else statement, even for early returns, remove hyphens from my comments because they were "improper grammar", put a useless giant copy pasted comment at the start of each file so you can't even see any code without scrolling, one separate file for each class even if it's an internal helper class used nowhere else, and use interfaces and MVVM for literally everything, even when it was severely over-engineering (or should I say overengineering). It just felt soul crushing to make this ugly ass code that took forever to write, just because the style guide said so.

Then A.I. happened and I quit being a software engineer completely. Telling an A.I. to do my work for me is just depressing. What's even the point anymore? I still code for fun but I'm done with the industry.

[–] vinnymac@lemmy.world 6 points 1 day ago (2 children)

These days it’s very common to write whatever code you want, and a formatter automatically rewrites it to conform to the projects rules during precommit.

Which is great because it allows you to focus on intent instead of format, and completely avoids any team disagreements or change rejections for trivial bullshit.

[–] Aceticon@lemmy.dbzer0.com 3 points 1 day ago* (last edited 1 day ago) (2 children)

And then somebody changes the auto-formatter settings and all of a sudden every single file changed and committe appears as having most lines changes and you loose the ability find the real code changes between a version before that and the current version.

Guess how I found this out ...

Standardizing code format via that path only works well if you start it really early in the project and never change it after that.

(Also, it doesn't solve the problem of different software design styles)

[–] vinnymac@lemmy.world 5 points 20 hours ago* (last edited 20 hours ago)

I hear you, but these are solve-able human problems, not code problems:

Manager: Jose revert your commit, thanks. Jose: okay, it’s been reverted, I won’t do that again, thanks for explaining to me why exactly what I did was the wrong thing to do.

I’ve had this exact conversation about this topic at least a half dozen times over the last decade.

When it comes to legacy code, almost all auto formatting tools I’ve used allow you to ignore whole directories and files, which can be very handy for legacy areas of the codebase not yet ready for this transition.

As for scenarios where large rewrites are necessary, it’s best to separate from any actual work, so the blast radius is focused, and that commit can be marked properly using .git-blame-ignore-revs which completes fixes the history issues that are common amongst those who don’t know what they are doing.

Definitely a painful process it can be, but it’s better to fight this battle than it is to try and get 1,000 humans to agree on something as vague as “style”

[–] jj4211@lemmy.world 3 points 22 hours ago

Ah yes, some random intern suddenly has 'credit' for almost all the codebase because they ran a linter with different settings than previous linter settings..

[–] Zarobi@aussie.zone 6 points 1 day ago

My favourite part is when your style or the auto formatter changes over time and you have to decide between:

  • running the auto formatter on 200,000 12 year old code files
  • doing them one by one
  • formatting them when you have to change that file
  • or ignoring all the warnings forever (it's this one, this is what you do)

Plus it doesn't fix the problem of auto formatters writing ugly code. You can't easily tell the auto formatter that early returns can be bracketless for brevity, but nothing else can be. Unless you add a comment like \\ ignore-rule-2753674 which makes me want to throw up

load more comments (4 replies)
load more comments (2 replies)
[–] Pechente@feddit.org 30 points 2 days ago (2 children)

As a freelance dev it’s not quite as bad now but it’s insane to see that some of my clients think I got replaced by a machine now only to show me a buggy vibe coded mess of an app that is poorly designed and works half the time at best. I like some of the LLM tools but it’s important to understand their abilities and limitations especially in regards to future capabilities as there are hard limits to how capable they can become.

Way too many people think the tools are smart because they can „talk“ and these same people do not understand any of the underlying tech.

Some of my clients send ChatGPT written instructions now that are missing half the context of what I‘m actually doing.

[–] GreenBeard@lemmy.ca 20 points 1 day ago (3 children)

I call it "Turing's Revenge" where, once the bot can pass the Turing test, we find out the hard way if humans are intelligent... and we appear to have a lot of failed models, mostly in management.

load more comments (3 replies)
load more comments (1 replies)
load more comments
view more: next ›