A Startup CTO’s Guide to Ops

May 11, 2017 | Newsletter

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


 

This week: 7 types of technical debt, team dynamics that foster great work, a minimum starting point for ops, the tragedy of 100% code coverage.

 

communicate costs and business trade-offs by identifying technical debt

TECHNICAL DEBT

7 Distinct Types of Technical Debt

David Cottingham, a Product Director at Citrix, proposes that the term “Technical Debt” is too imprecise. By providing a more specific categorization we can communicate costs and business trade-offs more easily.

 

foster excellent work environments for engineering teams

CULTURE

What it looks like when an engineering team eats their vegetables

Duretti Hirpa, an Engineer at Slack, on they team dynamics that help people do their best work, and how to foster excellent working environments with minimal process.

Read the full post→

 

minimum starting point for ops infrasturcture

OPS

The Startup CTO’s Guide to Ops

Chuck Groom, previously the Head of Engineering at SurveyMonkey, serves up a three part series with a scrappy perspective, on what is a minimum decent starting point for infrastructure.

Read the full post→

 

software architect questioning the usefulness of unit tests

TDD

The tragedy of 100% code coverage

Daniel Lebrero, a software architect at IG Index, “For fifteen years I have been preaching TDD and unit tests. However, in recent times I have found myself saying more often, ‘Why did you write that test?’ instead of, ‘You should write a test’…”

 


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.

how to use data to lead a successful software teams

A Data Driven Approach To Leading Software Teams

Learn how engineering leaders are using data to help their team increase productivity and become even more effective. We've analyzed over 40 Million commits to help you understand the important questions every software engineering manager needs to know.

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