Software Lead Weekly

How to Do Less
6 minutes read.

Alex Turek will make you stop and think about your team's execution discipline and stress levels. Controlling WIP (work in progress) is indeed the right direction. I disagree with picking WIP=1 as the correct number. The Engineering Manager should iterate and learn how many t-shirt size WIPs the team can own to maximize business impact and personal growth plans. EMs should optimize for at least two people working on the same project, which will help reduce the team's WIP projects.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

Engineering Candidate Sends You a Pic of This WFH Setup. Do You Hire Them?
1 minutes read.

My humble effort to help you start the weekend with a smile on your face, even in this difficult time.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

The Maybe Great Idea
14 minutes read.

Read Tanya Reilly's deck to improve the probability of your ideas hitting production and making a significant impact. It's worth looking for Tanya's post "Iterating on our RFC Process" if you prefer reading about their journey at Squarespace in a more accessible reading format.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

Another Common Question I’m Answering Working With Scaling Tech Companies Is: Q. What’s the Worst Leadership Advice You’ve Heard? A. By Far the Worst Is “Hire Great People and Get Out of Their Way”. Let Me Explain… (Thread)
7 minutes read.

"I prioritized autonomy over alignment. It's a million times easier to measure and feel high autonomy than it is to measure high alignment. [...] The biggest alignment problem is the gap between how much people think they have to align versus what they should align on. There are many strategic decisions in the how. eg, what technologies to use, new system vs integration, build in core or in an app." -- This thread is packed with so many gems. Jean-Michel Lemieux with one of the most important insights I've seen on leadership. Read it, share it, practice it, and re-read it again.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

Don't Go for the Incremental, Pursue the Transformative
4 minutes read.

"attack the inherent complexity of the problem, not the incidental complexities, which time and improvement in technology will take care of." and "The point of prototypes is to fail fast, learn, and move on to the next attack. If you have a plan of attack for a worthy problem, sketch it, model it, pursue it to see if it holds water. As the first/easiest step, write down your idea to explain it." -- Murat Demirbas with powerful reminders worth reading. Will it inspire you to try (or keep going)?

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

When to Delegate, When to Say No
6 minutes read.

Lara Hogan shares a simple and effective mechanism to review your efforts and decide what to promote now, delegate, delay, or decline. Use it when you feel overwhelmed to create some focus on things you should decline or delay to reduce immediate noise.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

15 Visuals That Will Motivate You to Read More Books
4 minutes read.

I love all of the visuals Alex shares. Use one of them as a background for your phone. A daily reminder can be useful to boost your reading habits.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

How to Be a More Effective Internal Product Manager
9 minutes read.

Share Rui Zhang's post with internal product managers or "pure makers" (those who strive to do things end to end, from ideation to production). I love the HEART framework to gauge products, internal or external.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

@omervk: The question I found most impactful to ask when I get a document to review is What kind of feedback would you like me to give?

@NavalismHQ: Free education is abundant, all over the internet. It’s the desire to learn that’s scarce.