My last place also called it promotion-driven-devevlopment.
It got to the point where some dude built a system that completely floundered but got him a promotion. He then re-wrote it so it sucked slightly less and got another promotion. Last I heard he was working on v3.
Never mind that someone with actual domain knowledge would have either not built the system (since it didn't _really_ need to exist) or would have built a much simpler/more reliable system to get the job done.
Can't disagree. He's was doing what the incentives in place said he should be doing.
I would find it boring/tedious to keep rebuilding the same thing since I'm more of a solve the problem, operationalize the solution, then move on person.
Ah, but he "de-risked" the project by getting it out the door quickly, he started "delivering immediate value" despite the rough edges, and "has the technical acumen to optimize it further."
I got downleveled in a job offer recently after being interviewed about a project which I labored to make as simple and efficient as possible. They said after careful evaluation, the project wasn't technical enough to merit the title I wanted. Live and learn!
It got to the point where some dude built a system that completely floundered but got him a promotion. He then re-wrote it so it sucked slightly less and got another promotion. Last I heard he was working on v3.
Never mind that someone with actual domain knowledge would have either not built the system (since it didn't _really_ need to exist) or would have built a much simpler/more reliable system to get the job done.