News for hackers. Stuff that matters.
Re:The Senior Engineer’s Guide to Helping Others Make Decisions by ilaksh on Sunday November 12, 2017 @04:54PM (#15682835)
My thought is that really good juniors need to be treated as less experienced peers in most (but not all) interactions. A smart, hard working, capable programmer is going to need to feel respected. So the number of times 'junior' and 'senior' get thrown around here is problematic.

Which is not to say that there shouldn't be clarity in terms of who gets final decision making or that there is no hierarchy at all. But in most discussions you should treat them as a smart person who probably has good ideas that should be respected. Otherwise why did you hire them? I'm not _quite_ getting that tone from this article.

Re:The Senior Engineer’s Guide to Helping Others Make Decisions by avleenvig on Sunday November 12, 2017 @06:06PM (#15683063)
I completely agree, and in writing this post it was one of the pieces of feedback that came up. Ultimately we decided to go ahead with the verbiage because it would be the most easily understood, but the _message_ here is not about junior vs senior or organisational hierarchies. It's about peers and interactions between more and less experienced persons.

I interact with people daily who are far more "senior" to me on specific topics, and I to them on other topics.