> It is sad that one of the most influential engineers or our time thinks that to be the best engineer he has to be on the bottom of the org chart. Says quite a

> It is sad that one of the most influential engineers or our time thinks that to be the best engineer he has to be on the bottom of the org chart. Says quite a bit about where we place value. It's because he knows what org charts mean. Being at the bottom of the org chart doesn't mean being the least compensated or least respected, many engineers that are leaf nodes in an org chart are some of the highest paid and most respected. Being at the bottom of the org chart means that your job is to write code, not to go to lots of meetings, make lots of slide decks, not to manage people with all of their weird quirks, not to persuade a bunch of executives, etc, etc, etc. What he's saying is that knowing what it means to be in other positions in the org chart, he'd happily be the guy whose job it is to write code all day.