Issue #42, 6th September 2013

This Week's Favorite


Getting Your Team to Adopt New Technology
5 minutes read.

Brilliant post by Ben Kamens (Lead Dev at Khan Academy), one that you should share with every Technical Lead in your company. From my experience, being able to create a solid game plan for adopting a new technology (or concept) is one of the key parameters of great Technical Leads. It involves both figuring out every technical details while also leading the team through this change - dealing with concerns, conducting risk analysis, being open and communicative, break the change into smaller chunks, educating the team etc. Highly recommended!

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Culture


Behind the Scenes: How the Tesla Model S Is Made (Video)
5 minutes read.

Five minutes of engineering perfection. It's really hard to add anything to such a remarkable process, other than you have to watch it.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Make Every Word Matter
5 minutes read.

Des Traynor (of Intercom.io) with a really important post about the connection between companies' communication and results. This observation also applies to each and every one of us, as individuals. If you care about your career path, you simply owe it to yourself to read it and judge the quality and style of your own communication. Great read!

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


How to Scale a Development Team
12 minutes read.

Adam Wiggins shares his own story of scaling the team at Heroku, ranging from picking the right tools and process at each phase, to breaking responsibilities without losing product or ownership cohesion. It's packed with insightful examples!

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Peopleware


How to Get Busy People to Take Action When You Send an Email
5 minutes read.

Mark Suster with 7 tips you can use to write an effective email. I've used Mark's advices when I wrote emails for high-profile individuals, asking for quick help or advice both for SoftwareLeadWeekly and TeamLeadToolbox. It works.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


How to Go From Google Engineer to First-Time CTO
20 minutes read.

If you're a technical person who's eventually aiming for a CTO position, you'd appreciate Ian Langworth's (of Artillery) thoughts and lessons learned. If you're short on time, you have to read "Failures in communication" and "Engineering utopias aren’t easy".

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


The Part They Don't Tell You About Startup Team Building
3 minutes read.

Tomasz Tunguz talks about the transition of a manager who successfully scaled his team, and now figuring out how to stay out of the way. As someone who experienced this transition before, it can be very fulfilling while also scary, as it's hard to imagine your next challenge. Read this post carefully and share it with your management team. A great way to overcome this problem is by making it visible to others and allowing the business owners to offer a few possible suggestions for a new role or adjustment. Visibility and open communication are a great way to retain talent for the long run.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Inspiring Tweets


@alignedleft: Please Stop Posting Jobs for “___ Ninjas.” It Is Disrespectful to the Ninja Community, and Confusing for Ninjas Actively Looking for Work.

@KentBeck: If You Can't Make Engineering Decisions Based on Data, Then Make Engineering Decisions That Result in Data.

- Oren

P.S. Can you share this email? I'd love for more people to experiment and improve their company's culture.

Subscribe now & join our community!