Eric Brandes talks with Dave Rael about about community, culture, impact, enigeering, and making a successful business
Eric is one of the founders and current CTO of TrackJS, a growing boostrapped business focusing on JavaScript error monitoring. Prior to founding TrackJS he spent over a decade consulting at Fortune 500's on large web projects. From building MVPs to overseeing development on billion dollar web properties, he has strong opinions about building software and delivering value. Sometime he gives talks and writes about it. When he's not writing code, he's making bad 80's music and rap beats.
Chapters:
0:36 - Dave introduces the show and Eric Brandes5:16 - Eric on speaking at and sponsoring conferences7:32 - PubConf9:54 - Building a positive culture14:04 - TrackJs and cloud computing16:18 - Minnesota developer communities and the passing of a great in David Hussman19:55 - Eric's thoughts on becoming a business owner and operator25:16 - Eric's story of failure - slow (rather than fast) business growth, failure to to convince project teams that big integration at the end was a bad idea32:50 - Origins of TrackJs38:18 - Eric on travel and social interaction as an introvert40:49 - Roles at TrackJs and the sometimes butting of heads of running a business together42:32 - Eric's book recommendations47:08 - Eric's top 3 tips for delivering more value51:13 - Keeping up with Eric
Resources:
TrackJs
The TrackJs Blog
Todd Gardner on Developer On Fire
Let It Be - The Beatles
PubConf
Erik Dietrich
Bryan Cantrill on Developer On Fire
David Hussman on Developer On Fire
A Protocol For Dying - Pieter Hintjens on The Changelog
YAGNI
Manifesto for Agile Software Development
Eric's book recommendation:
Code Complete: A Practical Handbook of Software Construction, Second Edition - Steve McConnell
The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win - Gene Kim
Atlas Shrugged - Ayn Rand
Eric's top 3 tips for delivering more value:
Use boring technoolgy ("There's no place in software for optimism")
Do the hardest thing first
Keep it simple (and really think about what you mean by "simple" and if it really is)