I don’t know. I look at it like firing all your construction contractors after built out all your stores in a city. You might need some construction trades to maintain your stores and your might need to relocate a store every once in a while, but you don’t need the same construction staff on had as you did with the initial build out.
Most extension today is enshitification. We’ve also seen major platforms scale to the size of Earth.
If you’re only going to maintain and don’t have a plan on adding features outside of duct taping AI to the software, what use is it maintaining a dev team at the size you needed it to be when creating new code?
I’m not saying you can fire everyone, but the maintenance team doesn’t need to be the size of the development team if the goal is to only maintain features.
I don’t know. I look at it like firing all your construction contractors after built out all your stores in a city. You might need some construction trades to maintain your stores and your might need to relocate a store every once in a while, but you don’t need the same construction staff on had as you did with the initial build out.
In my experience, you actually need more people to maintain and extend existing software compared to the initial build out.
Usually because of scalability concerns, increasing complexity of the system and technical debt coming due.
Most extension today is enshitification. We’ve also seen major platforms scale to the size of Earth.
If you’re only going to maintain and don’t have a plan on adding features outside of duct taping AI to the software, what use is it maintaining a dev team at the size you needed it to be when creating new code?
While true, that is a weak analogy. Software rots and needs constant attention of competent people or shit stacks.
I’m not saying you can fire everyone, but the maintenance team doesn’t need to be the size of the development team if the goal is to only maintain features.