Ask HN: What does mastery look like in software engineering?
I’ve been pondering this a lot lately, as an engineering leader.Masters in my organization have an extremely high ratio of value shipped to hours worked.This means two things. They are able to discern and avoid work that does not provide value (this is often their greatest skill), and the best ones can direct a whole team away from large swaths of work that is not valuable.  And they are able to build systems such that the cost of adding more value to the system remains constant as the system grows in complexity.