Software Lead Weekly Software Lead Weekly

My Leadership Document — 2021 Edition
11 minutes read.

So many gems in this post by Subbu Allamaraju, I found myself marking and taking notes on almost every paragraph. I'd add Subbu's post to the recommended reading list for managers and technical leads. Interesting idea to try out: Pair managers and tech leads together and ask them to discuss their observations on "Watching for excuses" and "Using your leverage."

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

"I'm Inheriting Too Much Tech Debt"
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 Instapaper.
Share it via Twitter or email.

Encourage Teams to Take Risks
4 minutes read.

"In our work we may not always be the best guardrails for a team member. But, with a little work we can identify what those guardrails should be. I love using RFCs(Request For Comments) for large features and new services because they provide opportunity for team members to grow with minimal long term risk. The checkpoints and conversations help them learn architecture by doing it, and allow the team at large to help them grow." -- Letting people make mistakes is hard. But you were in that place before. You want to cap the risk while also ensuring that a failure won't discourage them too much.

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

Incident Writeup as Sociological Storytelling
3 minutes read.

This is such an excellent take on how to write an incident report: "good incident writeup is a sociological story about our system. Yes, there are individual engineers who were involved in the incident, but their role in the writeup is to serve as a narrative vehicle for telling that larger story. We care about those engineers (they are our colleagues!), but it’s the system that the story is about."

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

It’s Time to Fight for a Dual Product Management Career Path
9 minutes read.

As a parallel career ladder become more common on the engineering side, Ken Norton suggests we adopt it for the Product Management route. People should not be forced upon management of people to increase their impact, and this should be true for more and more professions as our industry matures.

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

The Power of Product Thinking
5 minutes read.

Learning to improve your inquiry and observation skills is critical to increasing your impact on the organization. It will impact how you build tools and products (internal and external): "The simplest way to define product thinking is that it is the skill of knowing what makes a product useful — and loved — by people. As with all skills, it can be nurtured and developed; it’s not just an instinct one does or doesn’t have (and even instincts are trained, after all)."

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

Someone Asked, So I’m Curious to Hear What Others Recommend: What Are the Best Resources for Learning to Be a Better Presenter and Storyteller? (Thread)
3 minutes read.

I've picked up many resources to read and watch, and I believe you'll find it helpful as well. I can recommend Made to Stick as an inspirational book to drive ideas from. If you look for structure, Molly Mielke's response is spot on.

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

The Thinking Ladder
22 minutes read.

You'll find yourself being inspired while also getting some serious laughs. It's a long one, and wonderfully written by Tim Urban. So grab a coffee or tea, and enjoy.

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

@BrianNorgard: Product is philosophy.

@david_perell: The Law of Work: Communicating an idea requires a finite amount of work. The more work the writer does to clarify their ideas, the less the reader has to work to understand them.