Software Lead Weekly Software Lead Weekly

How I Interview Engineers to Assess Ability to Deliver Impact
7 minutes read.

Siadhal Magos shares a great framework to go deeper in interviews to assess the impact level the candidate seeks to achieve and is capable of. The framework can be used to drive existing employees to be more impact-driven, so steal it away and share it with your teammates.

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

Joining a Startup as a New Grad
1 minutes read.

My humble effort to help you start the weekend with a smile on your face.

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

Be Critical or Be Corrupted
5 minutes read.

CJ Cenizal is spot on observing Goodhart's law in action: "But by definition, the purpose of the rotation was to resolve users' issues. An engineer on rotation had one job: resolve as many issues as possible. This approach was so simple and effective that the organization never adopted the rotation as a driver for change. Ironically, treating users' problems as mere symptoms of an underlying problem and then solving the root causes would have reduced the number of problems in the long-term." -- one way I learned to deal with it is by figuring out KFIs (Key Failure Indicators) to balance KPIs.

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

"If You Don’t Make It Beautiful, It’s for Sure Doomed": Putting the Vault in GitHub’s Arctic Code Vault
5 minutes read.

This is a mind-boggling project by the folks at GitHub: "Our hope is that by storing and indexing millions of repositories we have captured a valuable cross-section of the world of modern software."

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

Rewriting the Story of Compensation
5 minutes read.

Companies trying different compensation methods, especially when they cross a certain size (as a public company like Shopify), open up ideas for many other companies to experiment with. Many times legal and finance teams don't want to risk it. This take by Shopify might trigger more ideas that will benefit employees everywhere.

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

The Leader’s Journal: Become an Inspiring Leader in Ten Minutes a Day
5 minutes read.

"While a developer can push code to Git and receive instant feedback from his peers, there’s no PR process for a leader’s decisions, insights, or creations. Our impact isn’t easily measured." -- Ofir Sharony covers how he uses journaling to iterate on his impact as a manager and find a better balance to avoid burnout.

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

This Is the Best Definition of Focus by Jony Ive With a Lesson From Steve Jobs (Video)
2 minutes read.

Saying no is (relatively) easy. Saying no to things you are desperately looking to do and cannot stop thinking about - now that takes some serious focus and discipline.

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

Guiding Principle: Think Big, Work Small
3 minutes read.

"Think Small, Work Small is a typical mistake for Agile novices." -- Jason Yip captures so well the common pitfall of the planning <> execution most teams and companies fall into. Thing Big (Roadmap, Milestones, ADRs) and Work Small (usable releases) is easy to say yet hard to execute, but a muscle teams should learn to develop.

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

@funcshawnal: 24 but instead of defusing a bomb Jack Bauer has to figure out why his unit test fails only in CI, only ~20% of the time. His next meeting starts in 7 minutes.

@alexkyllo: One important lesson I've learned working in data is: do not listen to the "storage is cheap" people. They do not understand the cost of sorting through massive piles of unmodeled, poorly organized data when you need to query it.