Re:The Myth of Architect as Chess Master
by nitrogen on Tuesday February 18, 2020 @12:43AM
(#22353769)
I've seen this in a couple of places. Junior dev assigned to design new system. Senior dev assigned to mentor junior dev. Senior dev encourages junior dev based on experience. Junior dev ignores everything senior dev says. Manager listens to whatever junior dev says and sidelines senior dev. Senior dev goes on vacation. System explodes.
[ Parent
| on HN ]
Re:The Myth of Architect as Chess Master
by Ididntdothis on Tuesday February 18, 2020 @01:12AM
(#22353874)
At my company management often gives new stuff to interns while senior people are stuck with maintenance work. It’s really weird.
Re:The Myth of Architect as Chess Master
by cbm-vic-20 on Tuesday February 18, 2020 @08:06AM
(#22355705)
I've been at a mega-corp that let newly hired developers to build new stuff while senior devs are busy putting out customer fires that in many cases, were caused by those junior devs in the first place. "We want to make sure the junior devs have interesting things to work on so they stick around."
Re:The Myth of Architect as Chess Master
by rimliu on Tuesday February 18, 2020 @04:53AM
(#22354742)
Not really. A new system means it is not in production yet, so if something goes wrong there is little impact. Breaking the working system doing maintenance can cause lots of problems, so it is seniors who are tasked with changing it.
Re:The Myth of Architect as Chess Master
by Ill_ban_myself on Tuesday February 18, 2020 @10:12AM
(#22356580)
Your manager should be called a practice lead and they should have recently been a senior dev. They should have been picked by other senior devs as the obvious choice since he’s the guy who spends more time on lunch and learns than writing code.