Post #2512208
2026-05-14 04:52 UTC
Replies (4)
-
@the@sh.itjust.works 2026-05-14 06:34
Yeap. As a software engineer, this is 100% my experience.
-
@cinoreus@lemmy.world 2026-05-14 07:39
Yeah, it looks like it’s largely this, with a few exceptions
-
@ExperiencedWinter@lemmy.world 2026-05-14 16:19
How do you deal with the lack of understanding of the codebase? The company thinks they pay programmers to write code, but in my experience they actually are paying for someone to understand the whole thing. When something goes wrong in production do you just ask AI to identify the problem?
-
@baller_w@lemmy.zip 2026-05-14 19:00
Enterprise Architect here. This is the answer. All the way. At my job, employees haven’t written code since the asp classic days and it was garbage back then. This meant almost all new code is written by contractors, which is often garbage. And slow, expensive garbage at that. Now, AI can at least make better code than the contractors at a fraction of the price. It also tightens the feedback loop between getting half-assed requirements and getting the deliverables back to those who requested them so they can say how it’s not what they asked for. That process used to take months, now it takes like a day between iterations. I honestly don’t know where people are working where they say they have tight control of first party deliverables and clear requirements with a cogent SDLC. All companies I’ve worked for have been about 1-2k employees. Are these people working in 10k large organizations where people can afford to be an expert in only one thing? Also, remember those debugger skills because we’ll all need it.