Working Code
001: Adam's Secret Shame
Your hosts
Adam Tuttle -- Twitter, Website
Carol Hamilton -- Twitter
Tim Cunningham -- Twitter
Follow the show! Our website is workingcode.dev and we're @WorkingCodePod on Twitter & Instagram. New episodes weekly on Wednesday.
Triumphs & Fails
- Adam's Triumph: His team realized that they could write a tool that would log, per controller method, how many times it had been run, whether or not it threw exceptions, and some performance stats, which is reducing the pain of transitioning app server platforms without a comprehensive test suite. They're currently at 90% tested!
- Carol's Fail: Having just started a new job, she thought she would make a good first impression by bringing down the production site!
- Tim's Triumph+Fail: A product he's been working on developing in secret for FOUR years is finally going to see the light of the day... just not through his years of persistence trying to push it past the finish line.
- Ben's Triumph+Fail: A R&D project failed to get any traction, but on the plus side he got to delete thousands of lines of code!
Notes & Links
- The VS Code plugin that Adam couldn't think of is Git Lens
- Cargo Cult Programming
- CFML ("ColdFusion Markup Language") a.k.a. ColdFusion is a web-dev language and app server that the four of us have some shared history with. Lucee is its open source alternative engine.
- Spoiler alert: You can write awful code in every language!
- "Life with chapters" is a concept stolen from the No Dumb Questions podcast, which is fantastic, and a huge inspiration for Working Code. If you don't already listen, give them a shot!
- There are a variety of different ways people prefer to learn, but teaching a concept is the best way to help yourself find your weak spots.
- Never compare your beginning to someone else's middle!
- The Martian is a fantastic movie and a better book; and yes, the audiobook was narrated by Wil Wheaton, of Star Trek fame.
- GraphQL is an interesting new(ish) idea in the world of web API's.
- "The right tool for the job"? NOPE. The right tool for the job, for the team, at that particular point in time. You heard it here second!