Comment by zx8080
20 hours ago
> I consider 99% of my "defense of the architecture" strategy to be teaching my team why the architecture is important, how to think about it, and invite they commentary on it as we own and evolve it together.
Nice way to avoid the responsibility for any team fuckup: it's not me, I only teach them, they decide themselves.
>Nice way to avoid the responsibility
Welcome to the tech industry. Its all about shifting responsibility in case something goes wrong. Thats the only reason companies use third party software in the first place, to have a scapegoat...
performance reviews are also a great time to find a scapegoat as well