17 Metrics for Modern Dev Leaders


Motivation to be data-driven

As dev leaders, we spend most of our time translating between two groups of people in two parallel universes. Most CEOs and board members come from the business side (sales, marketing, finance) and while they enjoy the outcomes of engineering, they don’t fully understand how we work. At the same time, many engineers don’t fully understand the business side of the organization. This is the background of most dev leaders. The right software metrics can help provide a common language between dev leaders and business executives.

Save or share “17 Software Metrics for Modern Dev Leaders”.

Git pull request review strategies from three dev teams

Most of us know the definition of a git pull request:

Software developers submit a pull request (often abbreviated to PR) in their git system like GitHub, GitLab or BitBucket to signal to their teammates or manager that a branch or fork they have been working on is ready for review.

The git pull request usually happens in the software development process after coding and before merge.

Abruptly WFH: 11 Things Changed and 8 Things Stayed The Same

Work-life balance is taking on a new meaning for many. The dev team at LinearB is no exception now that we’re abruptly working from home.

My team works out of our Tel-Aviv office. There are 10 of us here. Recently, we decided to prepare for our team to operate remotely for an extended period. To do this, we decided to run a remote “test day.” What we didn’t know at the time is that the remote prep day ended up becoming the first day of the new “normal” way for our team to work.