Thank you for this post. I feel that this and your other linked article describes exactly my role. I code, I mentor, but my more important function is to guide technical decisions. That means knowing the business and the tech and doing my best to be easy to work with. It is really a different role than I thought it would be when I decided to pursue this career path years ago. I think I wanted to be the guy who knew all the right answers of software design. It turns out nearly every answer is "right" in a specific situation. Then ranges from "viable" to "dead wrong" in other situations. The trick is knowing and being able to articulate those factors in a helpful way.
I find also that in many situations the right answer is already known and is a kind of obvious. It's just about making it happen. Significant and time-consuming changes are often hard to sell and get aligned with other company priorities.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for this post. I feel that this and your other linked article describes exactly my role. I code, I mentor, but my more important function is to guide technical decisions. That means knowing the business and the tech and doing my best to be easy to work with. It is really a different role than I thought it would be when I decided to pursue this career path years ago. I think I wanted to be the guy who knew all the right answers of software design. It turns out nearly every answer is "right" in a specific situation. Then ranges from "viable" to "dead wrong" in other situations. The trick is knowing and being able to articulate those factors in a helpful way.
I find also that in many situations the right answer is already known and is a kind of obvious. It's just about making it happen. Significant and time-consuming changes are often hard to sell and get aligned with other company priorities.