I think that's a good description. As I've become a more experienced software engineer, my job stopped being about making new features and switched to controlling chaos. Writing code that needs to be maintained for years is a very different problem than getting a lot of functionality out the door.
Experience teaches you how to adjust for the right spot on the spectrum between "build for business value" and "build for maintainability."
> As I've become a more experienced software engineer, my job stopped being about making new features and switched to controlling chaos.
Isn't that funny. Get the inexperienced folk to churn out features so the experienced folk can enjoy the nightmare of perpetually repairing the monster.
Experience teaches you how to adjust for the right spot on the spectrum between "build for business value" and "build for maintainability."