| I think you’re overlooking this: > I won't say they are worse at coding, but more that I am more familiar with how dependencies work because I've already done the same thing when I was a junior. Also, knowing who to ask for help also helps a lot. I might phrase this a bit differently, but I think it’s getting at my thoughts as well. I work with developers who would destroy me in a race to implement various search algorithms, or whatever discrete metric of coding prowess you want. What they struggle with is: - Efficiently getting other teams to answer their blocking questions in a way that makes the other team happy to work with them. - Understanding the existing features of our fairly complex stack. - Judging when to ask for help, and who to go to about a particular problem. - Identifying dead ends quickly, and pivoting to alternative solutions at the first sign of trouble. - Incorrect assumptions about the company’s priorities, and how the priorities can help shape the request. I end up in a lot of meetings, but I also occasionally (a couple times a year on average,) take a few weeks and implement a business goal that a team has been stuck at for months/years. |