Leading Without Losing Yourself
The hardest part of technical leadership is learning without losing yourself.
The hardest part of technical leadership is learning without losing yourself.
Why engineering leaders need a philosophy before the system chooses them as the problem.
As generation gets cheaper, engineering management shifts toward judgment, validation, and learning.
I have worked with GitStart for three years and two months and have seen low and aha moments in the short spell. I've interviewed candidates from different continents; worked with Engineers, CTO, and CEOs from various companies and product offerings. I've bootstrapped distributed Engineering teams and managed developer growth. I've experienced what it means to run lean operations and navigating through the path of customer success. I've seen client frustration.
Quality software development requires an efficient process for code reviews. Tech teams spend about ~15% of their time doing code review and handling the resultant effect. Whereas this is a great habit for tech team, not everything falls under the category of code reviews.