GitPrime is Renaming to Pluralsight Flow Learn more

Understanding Motivations


Understanding Motivations

Engineering Impact is a weekly newsletter that highlights trends in engineering leadership, productivity, culture, and scaling development teams.

This week features posts on: 

  • Understanding Motivations
  • The Different Skills Needed to Be a CTO
  • Fast Software, the Best Software
  • A Year of Working Remotely
  • Engineering Advice From Non-Technical People.


Understanding Motivations

Ian Nowland, VP of Engineering Metrics and Alerts at Datadog, explains why he thinks “understanding motivations” is the core of good people management. His framework and checklist for understanding team member’s motivations are worth saving to incorporate in your 1:1s. 

Read the full post [10 mins]


One Job, Many Roles. The Different Skills Needed to Be a CTO

Jonas Van Schoote, CTO at madewithlove, walks through the different stages of scaling an engineering organization—from small group to managing multiple teams—and illustrates how a CTO’s skills need to adapt with each new phase of growth. 

Read the full post [7 mins]


Fast Software, Great Software

Craig Mod reflects on a critical element of great software: speed. “Speed can be a good proxy for general engineering quality…Fast software is not always good software, but slow software is rarely able to rise to greatness. Fast software gives the user a chance to ‘meld’ with its toolset.”

Read the full post [12 mins]


A Year of Working Remotely

“The way to look at remote work is that it’s a series of tradeoffs. You enjoy benefits in exchange for disadvantages.” Mike Davidson, VP at InVision, shares a thoughtful discussion on the tradeoffs of remote work. 

Read the full post [18 mins]


All the Best Engineering Advice I Stole From Non-Technical People

“It’s intriguing that the stuff that really seems to make a difference in the quality of software never seems to be about software.” Here’s Marianne Bellotti, Senior Engineering Manager at Auth0, shares five pieces of wisdom she’s collected and how they’ve changed her approach to writing software and working with software teams. 

Read the full post [15 mins]