this post was submitted on 15 Oct 2024
321 points (99.4% liked)

Programming

17492 readers
22 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] janAkali@lemmy.one 6 points 1 month ago (1 children)

I believe for many companies, developers work on giant codebases with many hundred thousands or even millions of lines of code.

With such large codebase you have no control over any system. Because control is split between groups of devs.

If you want to refactor a single subsystem it would take coordination of all groups working on that part and will halt development, probably for months. But first you have to convince all the management people, that refactor is needed, that on itself could take eternity.

So instead you patch it on your end and call it a day.

[โ€“] MajorHavoc@programming.dev 3 points 1 month ago* (last edited 1 month ago)

So instead you patch it on your end and call it a day.

Yep!

I'm looking forward to the horror stories that emerge once some percentage of those changes are made solely by unmanaged hallucination-prone AI.

I would feel bad for the developera who have to clean up the mess, but honestly, it's their chance to make $$$$$$ off of that cleanup. If they manage not to, their union is completely incompetent.