I think even building domain expertise is partially "permissioned" in so far that the engineer needs to be allowed to spent time on deep-diving problems. If he can only spend just enough time to find surface-level fixes, then it's more difficult to build the deeper understanding of the domain.
Remember that “permissioned” doesn’t mean “sit around and wait for someone to give it to you”. There is action to be taken there! Definitely read Ryan’s How To Receive Scope, it adds a lot of value. 👏🏼
“Some of the strongest engineers I know chase problems further than anyone else because they are curious to understand the root cause.”
Sometimes it’s not about being the smartest in the room. Sometimes it’s about continuing to dive in, asking the questions no one else is, chasing your curiosity, and pushing through until you find things.
Fantastic insights, Ryan! Your breakdown of why most engineers aren't considered "10x" is spot-on. The combination of deep domain expertise and impactful influence sets them apart. Your distinction between "permissioned" influence and "permissionless" domain expertise provides a clear roadmap for aspiring engineers. Building expertise through curiosity is a gem of advice – the relentless pursuit of understanding root causes can truly set engineers on the path to solving unique problems. Congratulations on hitting 42,000 readers – your valuable content is clearly resonating with the software engineering community!
Love the classification between "permissioned" and "permissionless". Never had this perspective about the traits you described.
Thanks for sharing!
I think even building domain expertise is partially "permissioned" in so far that the engineer needs to be allowed to spent time on deep-diving problems. If he can only spend just enough time to find surface-level fixes, then it's more difficult to build the deeper understanding of the domain.
Does that imply that being a 10x engineer is in large part contextual? If a 10x engineer changes careers or domains, do they lose their edge?
Thanks Ryan for sharing this! In my opinion, the most straightforward way to gain more influence is to lead by example.
Remember that “permissioned” doesn’t mean “sit around and wait for someone to give it to you”. There is action to be taken there! Definitely read Ryan’s How To Receive Scope, it adds a lot of value. 👏🏼
This 👏👏👏
“Some of the strongest engineers I know chase problems further than anyone else because they are curious to understand the root cause.”
Sometimes it’s not about being the smartest in the room. Sometimes it’s about continuing to dive in, asking the questions no one else is, chasing your curiosity, and pushing through until you find things.
Awesome message, Ryan – thanks for sharing.
Fantastic insights, Ryan! Your breakdown of why most engineers aren't considered "10x" is spot-on. The combination of deep domain expertise and impactful influence sets them apart. Your distinction between "permissioned" influence and "permissionless" domain expertise provides a clear roadmap for aspiring engineers. Building expertise through curiosity is a gem of advice – the relentless pursuit of understanding root causes can truly set engineers on the path to solving unique problems. Congratulations on hitting 42,000 readers – your valuable content is clearly resonating with the software engineering community!