Developer on Fire
Developer on Fire
Episode 080 | Jared Smith - Check Your Fear At the Door
Guest:
Jared Smith talks with Dave Rael about being motivated by solving real problems, the importance of education, seeking feedback, and the benefits of letting go of fear
Jared Smith is a Software Engineer for YCombinator backed One Month, inc. He is passionate about programming and learning all he can about computer science. Everything from DevOps to building awesome software, from how the electrons move through a circuit to how a hard drive writes data.
Chapters:
- - Dave introduces the show and Jared Smith
- - Jared's definition of value
- - The things that "light Jared up"
- - "Any sufficiently advanced technology is indistinguishable from magic." - Arthur C. Clarke
- - How Jared got started in software
- - How Jared became associated with One Month and ultimately employed there
- - Jared's story of failure - infrastructure migration and tackling a problem outside expertise - underestimating the problem
- - Jared's story of success - advancing from a support person to lead developer and transforming an unstable organization to a more modern operation
- - Secretly changing code with authorization is not advisable, but fear is also the enemy
- - Introducing source control, process, practices, and more sanity - using disaster as an opportunity to sell positive changes
- - How Jared learned patterns and practices to introduce to stablize the organization
- - The things that have Jared most excited
- - Jared's greatest sources of pain
- - Jared's top 3 tips for delivering more value
- - Keeping up with Jared
Resources:
- Jared's Blog
- One Month
- Clarke's three laws
- Rahm Emanuel - "Never Let A Good Crisis Go To Waste"
- Dave Thomas on Developer On Fire
- DHH on Developer On Fire
- Six Sigma
- Code Climate
Jared's book recommendation:
Jared's top 3 tips for delivering more value:
1. Listen and and actually hear what people want - listen deeply
2. Seek and get feedback
3. Don't be afraid to iterate, don't be afraid to throw away your code and redo it to get the right solution
