A shining example of how to teach

Nov 17, 2016 | Newsletter

Subscribe to Engineering Impact, the weekly newsletter for managers of software teams.


This week: A framework for providing better direction, the cost of cross-cultural teams, critical rendering path, chow to identify and respond to code churn.


effective critiques


A shining example of how to teach

Dan Kim breaks down the best teaching moment he’s ever experienced, and provides a framework so you can provide better direction to people on your team.


cross-cultural teams


Offshoring roulette lessons from outsourcing to India, China, and the Philippines

“If you’re looking at hourly rate as a metric for outsourcing success, you’re doing it very, very wrong!”

Troy Hunt tackles a delicate topic head-on, and shares his experiences from working around the globe as a software architect, and the true cost of cross-cultural teams not understanding each other.


critical rendering path


Critical Rendering Path

Prioritize the display of content to improve the first render of your pages. This well structured documentation from Google will explains the fundaments of critical rendering path and lays the foundation for building well-performing applications.


how to identify, respond, and prevent code churn


6 Causes of Code Churn and What to Do About Them

Code churn is the proverbial canary in the coal mine for software teams. Use this powerful metric to spot operational issues before they snowball and identify the actions to take when you find them.


If you enjoy Engineering Impact, sign up to get it weekly.

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