Hacker News new | ask | show | jobs
by battery423 2165 days ago
So i introduced Code Review in our Project after i joined it.

The other 2 senior people never came up with the idea of introducing it.

One of them is still putting Tickets in Review which still lack basic quality expectations.

My biggest / most used quality right now is persistence and pointing out the same misstakes/issues over weeks and month...

And don't get me wrong, there are only two options to this: 1. Get your collegues up to speed and be persistent 2. Search for a new Team

The obvious choice of not caring doesn't work for me.