The Keys to Scaling Yourself as a Technology Leader

Jan 3, 2019 | Newsletter

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

This week features posts on: Leadership, Process, Communication, Programming, and Context-Setting.

 

LEADERSHIP

The Keys to Scaling Yourself as a Technology Leader

Adam Pisoni’s advice is directed toward CEOs but is applicable to anyone scaling a team or organization — “if you’re still required to answer every question, you’re never going to scale.” Here’s how to get out of the weeds and make the biggest possible impact with your time.

Read the full post → 

 

PROCESS

One Size Fits No One

Rob Moffat, IT Consultant at HSBC Private Bank, offers an interesting take on choosing software methodologies and makes the case for matching the choice of methodology to the “risk profile” of a project.

Read the full post → 

 

COMMUNICATION

A Company is Not a Family

Jean Hsu, Engineering Leadership Coach at Co Leadership, says that asking your direct reports, “what’s next?” — and being direct about people’s departures from companies — will build immediate trust and alignment, while uncovering opportunities for feedback and their growth.

Read the full post → 

 

PROGRAMMING

Effective Mental Models for Code and Systems

Cindy Sridharan, co-author of an upcoming book on distributed systems, shares some guidelines that developers can use while authoring code to help ease the cognitive load of future readers and help them understand the mental models under which it was authored — which, when practiced across teams and over time, will keep the complexity of the codebase in check as it evolves.

Read the full post → 

 

CONTEXT-SETTING

Avoiding Mistakes with your Manager README

Matt Newkirk, Sr. Software Engineering Manager at Etsy, furthers the discussion around Manager READMEs by outlining some common pitfalls to avoid while you’re assembling and editing your README. He emphasizes that the focus should be on the recipient’s value of the document, and reminds us to treat the document as one piece of a multi-pronged communication strategy.

Read the full post → 

 


 

Ben Thompson

Ben Thompson

Ben Thompson is a co-founder at GitPrime where he leads design and customer experience. He is a Y Combinator alumni, with a background in product design, branding, and UX design. Follow @thebent on Twitter.

Get Engineering Impact: the weekly newsletter for managers of software teams

Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.

Get the Guide on Data-Driven Engineering Leadership

Gut feelings in engineering are being replaced with data. By analyzing over 7 million commits from over 85,000 professional engineers, we share how you can incorporate concrete metrics to guide engineering productivity.

Success! Please check your email for your download. You might also be interested in Engineering Impact: the Weekly Newsletter for Managers of Software Teams. Keep current with trends in engineering leadership, productivity, culture and scaling development teams.

Share This