Rocket developers Brandon Aaskov, Dave Oelfke, Simon Ingeson, and Matt Merrill dive into the topic of clean code. When is it worth it? When is it unnecessary? Will it get you in trouble with your teammates? We also share some practical tips for walking the line between "You ain't gonna need it" and when it's worth it to spend that extra 20 minutes cleaning up code. This podcast was inspired by the article "Goodbye Clean Code" by Dan Abramov which ignited a lot of talk in the Rocket Insights engineering slack channels!
03:20 - Human readability is the most important thing. Are there any hard and fast rules? Cyclomatic complexity is a fancy word that's discussed06:00 - It's hard to break out of a bad abstraction. It's hard to predict the future11:00 - There's nothing more permanent than temporary12:15 - Spreading out your code over lots of folders is probably not a great idea14:30 - Flexing your muscles... Unnecessarily?15:26 - A word from our sponsor16:30 - Wait for the pain19:30 - Give yourself flexibility for the future, but don't implement it right away20:40 - How did we get to this point? A little history. Memory management wasn't always done for us27:00 - There are no hard and fast rules. Be an adult29:45 - The golden hour rule. Readme's are important37:45 - Back to what makes code readable41:00 - Testability. Using tests to learn about existing codebases45:00 - File driven development46:30 - Why refactor?51:15 - The good samaritan rule51:50 - Picks:- Matt - HBO Silicon Valley Season Six
Simon - 1917 (the movie) Dave - Nest.jsBrandon - Master Class