this post was submitted on 25 Jan 2024
330 points (97.1% liked)
Asklemmy
43965 readers
1111 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy 🔍
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
What you're missing is that 95% of programming projects fail, and it's never because the programmer didn't code fast enough.
Speed-up isn't why I have a team instead of being a solo act.
There's also the pure reality that, yeah, it's easier today to get a project off the ground than ever before, and AI is good at that, but you know what AI is absolute shit at? Modifying ludicrously cumbersome, undocumented, brutally hacked together legacy code and addressing technical debt - the two most common tasks of most actual software engineers.
True.
Good thing most companies aren't stuck with ludicrously cumbersome, undocumented, brutally hacked together legacy code bases. /s
I can't even type that with a straight face.
So true.
Working with GPT actually helped me write better code, because it's more familiar with good patterns in unfamiliar languages and frameworks and can write idiomatically. It got me out of one-language-centric habits I hadn't known I had.
Yes, it's 100% true that the person driving the AI needs to have good design sense of what they want the final system to look like, and still work well with their team. You can fuck it up faster if you can code faster, absolutely that's true.
What you said, I know that. Do the people that run these companies know that?
Yeah. Exactly. They did the same to various degrees when web frameworks first hit the scene, and numerous other advancements before and after.
But as you said, the new tech genuinely does make us both faster and better.
It just doesn't fix the crap parts of the job that the CEOs always hope it will. (As someone else pointed out, it specifically doesn't magic wand away decades of technical debt, haha.)