Peopleware
The Solution to Technical Debt
This post can be used as a great reference for ongoing handling of Technical Debt. Henrik Kniberg offers a simple way to measure your satisfaction of your code quality and how to improve it over time. Eliminating Technical Debt should be part of your planning (e.g. part of writing features, or as tasks in the sprint/backlog). My advice is to pay attention as you don't want to invest time in eliminating Technical Debt in features/systems that are not useful for the business. It will always be cheaper and more beneficial to cut out some features and reduce your code-base. Share it with your technical leads and have a discussion about your current satisfaction with your code, and the approach you should use for handling quality in the long run.
Time investment: 15 minutes, add to:
Pocket,
Instapaper.
Inspire others: share it via
twitter or
email.
6 Secrets For Building A Super Team
Greg Brockman shares 6 lessons learned from hiring at Stripe, a company with probably one of the best engineering team in the world. My favorites are "Only hire people who make others want to be around them" and "Everyone gets a veto". Having these guidelines for hiring can help you check candidates for culture fit.
Time investment: 5 minutes, add to:
Pocket,
Instapaper.
Inspire others: share it via
twitter or
email.
How do I Tell my Team to Work More Hours to Hit A Launch Date?
What a great post by Edmond Lau (ex-Quora Engineer). If there is only one thing I could take from it, I'd choose "Focus on the overarching mission of the project, team, or organization, and why it's critical to that mission to meet the launch date". It is nearly impossible to enforce a commitment. Build relationships with them now, to allow such openness in the future. Invest the time, share your thoughts, help them succeed. It would pay off when you'll need their help.
Time investment: 10 minutes, add to:
Pocket,
Instapaper.
Inspire others: share it via
twitter or
email.