4
purist
3y

Management suddenly decides they wanted to see if a new process is any good and decides to load all the work on 2 people ( including me ) and keeps the deadline 5 days later ( when one person is taking a 3 day leave in this 5 days ).

In this situation, the other person involved in the process, routinely infuriates me by suggesting we fix up something within these days and not worry about readability or code quality. My argument is the POC is subject to heavy changes, so why not make it more "modifiable" from the start and not create a sphagetti which i would be left trying to fix when he goes on leave.

I would be blamed for slowing down things unnecessarily if i put forward my argument too sternly. Genuinely conflicted about whether to go on the offensive or to accept the reality and make myself uncomfortable by doing this faster.

Comments
  • 1
    POC should be a throwaway project that just proves something can be done. Normally those types of projects are quick and code quality should be ignored. I think it’s a mistake if you continue building on top of a POC codebase, just my 2 cents
  • 0
    @PappyHans Thats true. I wasnt suggesting that we should use the same code for the actual implementation. Just that when we show the POC to higher ups , they usually want us to make 100 different tweaks, and that would be easy if they are modifiable.
Add Comment