A) Create something that works, is fast, minimum bugs, have edge cases covered, nice testes, clean code. Cool, you did your job. END.

B) Create something shitty with bugs, performance issues, non or poor test coverage, mess code, etc. Cool, you did you job. But...

Next week you reduced bugs by 50%. Wow, you're rockstar.

Another week you improved performance by 15%. Again, you're the hero.

2 weeks later, you reached 85% test coverage. Management is so happy that almost got orgasm.

"A" took 3 months, "B" took 3 months plus few months of fixes. The only time where B was winning was first 4 weeks, where A was carefully building it's architecture and quality.

Yet B is seemed more successful.

This industry is F****d Up beyond my understanding.

!!!rant
f**king cooperate d**ckheads this ppl are work-shipped like gods who just ask stupid questions just for name sake and they don't know what the heck is going on underneath...they use fancy words like cloud/docker/etc and they please top management d**kers and this guys are top in chain...f**king cooperate political word... _|__

I'm pretty sure remote teams don't work with the remote team doing all the coding and we have the same exact JD and in the same department...*sigh* when management are foreign, they really are afraid of letting the local tech team help out. No wonder we are 3, sorry 2 since a fellow dev left to a better job in Amsterdam