Software Lead Weekly Software Lead Weekly

The Push Train: Managing the Human Side of Continuous Delivery
8 minutes read.

Anyone who had experience with writing tests in a large system will really love this presentation (/site) as it's so hard to do right. This, I believe, is key: "We eventually came to a realization that there was no point to the rituals we were performing with revision control. It’s better to conceive of a website as a living organism where all of the versions of it are all jumbled together."

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

The Feeling When You Realize the Robots Will Steal Your Job
1 minutes read.

My humble effort to help you start the weekend with a smile on your face. Cats are awesome, robot or not.

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

How I Adjusted My Startup Life to Become a Hands-On Dad
6 minutes read.

Yoni Tsafir with an honest post about something that deal with a lot as well, what is "good enough" dad? How can I be that for my son while still feeling I accomplish my own personal goals? Finding balance is hard, and reading others share their personal story really helps.

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

Two Thirds of Developers Work Remotely at Least Some of the Time, and This Number Is Highly Correlated With Job Satisfaction.
4 minutes read.

Having the option to take a day or two to work from home without having to ask for special permission is truly important: "much of the value of working from home is understanding that it's an option even if you don't exercise it very often. I too work in our team's office most days of the month, but will sometimes take day at home to recharge mentally."

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

How Stripe Teaches Employees to Code
4 minutes read.

When you reach to a certain size, helping your company grow and improve is a function of marginal growth in big numbers. We do something similar at Forter, where we teach Analysts how to write code in a complex system and run a 10 weeks long Team Leads course, to give them the tools they need in order to multiply their teammates and become better leaders. Great experiment by Stripe, and I'm sure they'll do more of those going forward.

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

The Startup CTO’s Guide to Ops (1 of 3): Guiding Principles
6 minutes read.

If you're in a leadership position, check Chuck Groom's notes on "What I Care About" and "Things I Don’t Worry About" -- you solve 90% of the problem when you're able to clearly and explicitly communicate that to people you work with. This reduces any tension and creates strong alignment on what is important in order to win. Don't read this post judging whether or not you agree with him, but rather ask yourself how clear is it in your team. Try to write your "I care about" and "Don't worry about" and see if you can share it with others.

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

You Can't Understand the Problem Up Front. The Act of Writing the Software Is What Gives Us Insight Into It. Embrace Not Knowing. (Twitter Thread)
5 minutes read.

Senior engineers will find this thread so relevant and true. Code evolves as you learn more about the problem and the how to extract more value for the user in a way that will enable your company to scale. Highly recommend reading the entire thread, it's packed with great insights.

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

Great PMs Don’t Spend Their Time on Solutions
5 minutes read.

There are so many ways to execute a product, that I feel that every post I read provides me with some interesting lessons to learn from. A good way to challenge my approach and thoughts on building products. There are very few companies on Intercom's quality of execution, and there are very few Product Managers with Paul Adams's skills.

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

@bphogan: Don’t confuse learning with videos, lectures, and reading. Learning happens through practice, performance, and feedback.

@Padday: If you talk about process more than product then either (a) you've too much process or (b) you need to write it down.