3 ms·
I think code reviews on teams without architects are awkward. Someone naturally might step up to take on that role, but if there’s no clear decision maker for h
by journalctl 7y ago
I think code reviews on teams without architects are awkward. Someone naturally might step up to take on that role, but if there’s no clear decision maker for hard technical choices, then it’s just a bunch of awkward, passive suggestions. And with no clear leadership, it’s hard to resolve disputes. People need to be empowered to do their jobs, but I’ve noticed that on a lot of dev teams that empowerment isn’t explicit. So you end up with the strongest personality being the one that makes important technical decisions or architecture decisions, regardless of whether or not they’re qualified. Personally, I’m not a fan of this approach.