Software Lead Weekly Software Lead Weekly

Dunbar’s Number and How Speaking Is 2.8x Better Than Picking Fleas
7 minutes read.

Matt Webb's post will make you think about the number of participants you have in various forums in your life. It fits well with the "Two Pizza Rule" some companies like Amazon use to structure teams or consider meetings' audience size.

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

Startup Meme
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.

The Cone Model for Teams' Support Network
4 minutes read.

"You should minimize your dependencies and maximize the network between your team members. Instead of letting all your team depend on you for their growth, you should create a connection between people, leveraging the different strengths and weaknesses." -- Shy Alter covers how you can use the "Cone Model" to formalize relationships between the teammates. This approach can also be used to pair teammates with members outside of the team, e.g. getting a Principal Engineer to mentor one of the Senior Engineers.

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

On Getting Support
5 minutes read.

"Only recently did I understand a problem with relying ONLY on my manager for growth. While it was true that my managers always showed care for me and my growth. They were on my side, but they were also on the company’s side. The overlap between my growth agenda and the company agenda is never 100% full - not even now when I am a founder in a company. For me it makes perfect sense to rely on people outside the system to support your growth. Not only do they give me a better perspective, they also are more on my side than my manager could be." -- Learning continuously to get help, consult with others, and learn from their experience is a superpower. Oded Blayer shares his approach, one that you can copy and use yourself.

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

Early Security for Startups
12 minutes read.

Devdatta Akhawe will help you create awareness and understand the language for Security at early-stage companies. These areas covered by Devdatta should be known by the business, product, and engineering to create a healthy mindset.

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

The Anatomy of A Rotten Codebase
6 minutes read.

Shai Yallin is spot on with this one: "Running fast is important. But, as the cliché goes, it's not a sprint - it's a marathon. It's better to work at a sustainable 80% velocity than at 100% but burn out after 6 months. And surprisingly enough, if you follow the first tip and avoid unnecessary structure and dependencies early on, you'll find that you're actually more productive as time goes on."

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

Master Your Questioning Skills
5 minutes read.

This post made me think a lot about the questions I've asked recently (not enough and probably not with high quality) and how I want to change it going forward: "A good question is like a good joke. It has an unexpected element and provides a perspective change. After I get through some questions and I eventually arrive to a good question, I have a visceral reaction similar to that of hearing a good joke."

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

Best Practices for Writing Code Comments
8 minutes read.

Share Ellen Spertus's post with your teammates and discuss insights and examples of high-quality comments in your codebase.

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

@GiladPeleg: Your managerial investment priorities: Retention> Onboarding> Hiring This is in contrast to popular wisdom that hiring is the most important thing you should work on

@naval: You can’t imitate your way to greatness because you can only copy the effect, not the cause.