Remove Development Remove Engineering Culture Remove Engineering Management Remove Software Engineering
article thumbnail

A Software Engineering Career Ladder

James Shore

It’s been a fascinating opportunity to rebuild an engineering organization from the inside, and I’m loving every minute. We’re introducing a lot of cutting-edge software development practices, such as self-organizing vertically-scaled teams and Extreme Programming. Culture doesn’t change easily. It tends to snap back.

article thumbnail

Establishing and Enabling a Center of Production Excellence

Honeycomb

Collecting this information up front is crucial because it will inform the development of a twinned strategy involving both passive and active tactics. To counter this, one might consider adopting the model of the Engineer/Manager Pendulum or other techniques of rotating leaders like sortition.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

The Rise of the Front-End Developer

LaunchDarkly

On May 21, for the Test in Production Meetup on Twitch , Yoz Grahame, Developer Advocate at LaunchDarkly, moderated a panel discussion featuring Rebecca Murphey, Senior Technical PM at Indeed, and Ben Vinegar, VP of Engineering at Sentry. Prior to taking on the tactical project manager role, I was in a senior engineering manager role.

article thumbnail

Why did file sharing drive so much startup innovation?

TechCrunch

Expensify founder and CEO David] Barrett, a self-proclaimed alpha geek and lifelong software engineer, was actually Red Swoosh’s last engineering manager, hired after the failure of his first project, iGlance.com , a P2P push-to-talk program that couldn’t compete against Skype.

article thumbnail

On Becoming a VP of Engineering, Part 2: Doing the Job

Honeycomb

This is particularly hard on engineering teams, where we always have to balance multiple priorities: security, reliability, performance, UX, shipping new features, iterating on existing features, internal developer experience, maintainability/tech debt, quality, scaling, etc.