Agree. Software engineering is a marathon - not a sprint. These AI tools are useful to get something up real quick, but I have a hard time seeing how they can be useful for long term maintenance work.
It’s still a marathon, even if the name ”sprint” is used. The point is the same: software engineering is about ensuring long term maintenance. It’s about building software that can sustain through multiple sprints.
The typical code from an AI agent can barely sustain a single sprint without having to restart from scratch.
I know, but in most companies they don’t give a fuck.
What’s done is done, sure there can be some minor maintenance, but goodness forbids you need to rewrite something that handles the 10x throughtput that built up over the years.
I am usually able to get some cleanup tasks in, but from what I’ve heard, not many people are.
It’s just sad, that some think ‘sprint’ means ‘this is done and dont dare to tell me you need more time, what have you been doing the last X sprints?’.
The first draft is fun.
The second draft is pain.
The third draft is cathartic.
Figure out features, add add add.
Add/change features, realise the spaghetti mess and poor design decisions you made in the first draft.
Clean everything up with better design and code.
Agree. Software engineering is a marathon - not a sprint. These AI tools are useful to get something up real quick, but I have a hard time seeing how they can be useful for long term maintenance work.
Oh BOY do I have this ‘brand new shiny’ thing called Agile at almost every fucking company ever.
Agile doesn’t claim that a project can be completed in a sprint.
Tell that to middle management
My middle management knows this. I don’t stick around for shit management, we don’t deserve each other. There are always other opportunities.
It’s still a marathon, even if the name ”sprint” is used. The point is the same: software engineering is about ensuring long term maintenance. It’s about building software that can sustain through multiple sprints.
The typical code from an AI agent can barely sustain a single sprint without having to restart from scratch.
I know, but in most companies they don’t give a fuck.
What’s done is done, sure there can be some minor maintenance, but goodness forbids you need to rewrite something that handles the 10x throughtput that built up over the years.
I am usually able to get some cleanup tasks in, but from what I’ve heard, not many people are.
It’s just sad, that some think ‘sprint’ means ‘this is done and dont dare to tell me you need more time, what have you been doing the last X sprints?’.
If the company you work for truly does not value this effort, then do not do it.
It’s not your code base. It’s theirs. You are not being rewarded for saving them from themselves. Don’t work for free.
Plus “getting something up real quick” is the fun part.
The first draft is fun.
The second draft is pain.
The third draft is cathartic.
Figure out features, add add add.
Add/change features, realise the spaghetti mess and poor design decisions you made in the first draft.
Clean everything up with better design and code.