Does your code leave a trail of slowness?

Mar 2, 2017 | Newsletter

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


 

This week: An excellent podcast for engineering leaders, programmers confessing their sins, trail of slow code, what a director of engineering does.

 

because your CS degree didn't teach you to lead

PODCAST

“Because your CS degree didn’t teach you to lead”

What began as a monthly CTO meetup, has become an excellent weekly podcast featuring conversations with engineering leaders from companies of all stages. Browse the archives to hear from leaders at SlackStripeSpheroSendGrid, and DigitalOcean. And be sure to subscribe… new episodes are released every Thursday.

Subscribe on iTunes→

Check out StartupCTO.io archives→

 

developer community roundup on interviews

CULTURE

Programmers are confessing their coding sins to protest a broken interview process

Here’s a powerful roundup of the meme that struck a chord in the developer community this week that highlights the absurdity of “whiteboard” interviews.

 

does your code leave a trail of slowness?

CODING

Does Your Code Leave a Trail of Slowness?

Jack Mott discusses how code from areas where performance is not important, may be causing other code, or even other programs to slow down.

 

Read the full post→

 

what does a director of engineering do

LEADERSHIP

What does a Director of Engineering do?

Dan DeMeyere shares about his journey from junior engineer to Director of Engineering, lessons learned, and how the experience has been the most rewarding of his career.

 

 


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