3 ms·
Reminds me when working on large scale project, we have maintained strict quality control. The PR wouldn't be accepted if it had even a tiniest bit of tech deb
by varispeed 4y ago
Reminds me when working on large scale project, we have maintained strict quality control.
The PR wouldn't be accepted if it had even a tiniest bit of tech debt or a hint of creating one.
Less experienced developers were struggling to put the work in and our reviews have given them a ton of extra work, often the PR would look completely different from what was first raised.
But the resulting code quality was great and the product had no issues whatsoever. The customer service never had to deal with problems with the project itself, just typical billing or "how to do something as I didn't bother to look into manual, please lead me" stuff.
Then we had a new CTO who was unable to get the board to understand why things take long time. We got mandated to let all PRs through as long as there is reasonable amount of tests and they pass.
This is where problems started to pile up. More experienced devs were now spending most of the time dealing with production bugs. Then they were quitting.
Company also found a brilliant idea that it's better to hire 3 junior devs than one experienced.
From there project turned into unworkable mess, nobody wants to touch.
CTO got fired and most of the developers. Company then decided to outsource the whole thing and commissioned a rewrite.