With LLMs I get work done about 3-5x faster. Same level of maintainability and readability I’d have gotten writing it myself. Where LLMs fail is architecting stuff out- they can’t see the blind alleys their architecture decisions being them down. They also can’t remember to activate python virtual environments, like, ever.
I think it depends on what you’re writing code for. For greenfield/new features that don’t touch legacy code or systems too much? Sure, I agree with that assessment.
Unfortunately that’s a small fraction of the kind of work I am required to do as most of the work in most places doing software dev are trying to add shit to bloated and poorly maintained legacy systems.
Working in those environments LLMs are a lot less effective. Maybe that’ll change some day. But today, they don’t know how to code reuse, refactor methods across classes/design patterns, etc. At least, not very well. Not without causing side effects.
With LLMs I get work done about 3-5x faster. Same level of maintainability and readability I’d have gotten writing it myself. Where LLMs fail is architecting stuff out- they can’t see the blind alleys their architecture decisions being them down. They also can’t remember to activate python virtual environments, like, ever.
I think it depends on what you’re writing code for. For greenfield/new features that don’t touch legacy code or systems too much? Sure, I agree with that assessment.
Unfortunately that’s a small fraction of the kind of work I am required to do as most of the work in most places doing software dev are trying to add shit to bloated and poorly maintained legacy systems.
Working in those environments LLMs are a lot less effective. Maybe that’ll change some day. But today, they don’t know how to code reuse, refactor methods across classes/design patterns, etc. At least, not very well. Not without causing side effects.