It comes all down to the triangle of doom: good, fast, cheap: can't have all three. Want a set of features in a given time? The only thing that can be bent into submission to allow this is quality. Devs become sick when forced to deliver inferior quality.
But it's only a prototype, management will say. Fine, says the developer, but if we don't throw away the code and start from scratch afterwards, it'll cost us even more time. Sure, sure, says management, only to break the promise after the success of the prototype. The developer's prediction soon comes to pass, but now, the developer is fed up and looks for a new job.
I've been that developer. I know that 99% of deadlines only exists because management has bonus goals that are fulfilled if feature X is out by date Y, so my friendly advice is: choose meaningful goals that actually advance your company over those damaging it. For example, reduce customer and developer churn by 5% until end of year.
For further actions, you may consider blocking this person and/or reporting abuse
It comes all down to the triangle of doom: good, fast, cheap: can't have all three. Want a set of features in a given time? The only thing that can be bent into submission to allow this is quality. Devs become sick when forced to deliver inferior quality.
But it's only a prototype, management will say. Fine, says the developer, but if we don't throw away the code and start from scratch afterwards, it'll cost us even more time. Sure, sure, says management, only to break the promise after the success of the prototype. The developer's prediction soon comes to pass, but now, the developer is fed up and looks for a new job.
I've been that developer. I know that 99% of deadlines only exists because management has bonus goals that are fulfilled if feature X is out by date Y, so my friendly advice is: choose meaningful goals that actually advance your company over those damaging it. For example, reduce customer and developer churn by 5% until end of year.