Culture
How to Evolve an Engineering Organization 6 minutes read.
Will Larson's thinking and frameworks are always fun to read and experiment with. I think that learning how to measure an engineering organization's effectiveness and happiness can be one of the most important skills to develop. It's hard because what you need to measure often holds a lot of emotions in it, i.e. how people feel about alignment and execution speed, and not only how many "story points" (or other metrics) the team has accumulated. My advice is to agree (team leads & product managers) on how a great outcome looks like in advance, say on a quarterly cadence, while taking the time to challenge (read: argue) the "must have" vs. the "nice to have" before you start.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Name It, and They Will Come 4 minutes read.
The art of storytelling is a skill that we should all practice and be measured on as we grow in our career. It's how you promote a new product to the world, and how you create internal buy-in inside the team to promote a change you'd like to see happening. Dan Abramov with an excellent story to learn from.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Why Data Science Teams Need Generalists, Not Specialists 7 minutes read.
"With data science, you learn as you go, not before you go." -- the entire post is useful for (almost) any development of software, even more so during pre-product/market fit. One thing that I'd change is the title - we should aim for building autonomous teams, not to broadly prefer generalists over experts. As a leader, you should understand how to build a puzzle and a team, where coordination and empathy are part of the equation.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.