Wolf surfaces five fundamentals to becoming a better developer (that you probably didn’t even know you didn’t know)! This is a fiery one! Jim asks questions, and also questions Wolf's choices. Takeaways The problem comes first—ask more questionsStart with the simplest thing that could reasonably workMeasure before you optimize (but don’t be stupid)Understand what’s actually an errorTest so you can evolve, and so that you don’t waste time, money, and effortLinks Solution from Marlon for Jim's ...
All content for Runtime Arguments is the property of Jim McQuillan & Wolf and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
Wolf surfaces five fundamentals to becoming a better developer (that you probably didn’t even know you didn’t know)! This is a fiery one! Jim asks questions, and also questions Wolf's choices. Takeaways The problem comes first—ask more questionsStart with the simplest thing that could reasonably workMeasure before you optimize (but don’t be stupid)Understand what’s actually an errorTest so you can evolve, and so that you don’t waste time, money, and effortLinks Solution from Marlon for Jim's ...
10: Command-Line Superpowers: Connecting Simple Tools for Complex Solutions
Runtime Arguments
1 hour 36 minutes
2 months ago
10: Command-Line Superpowers: Connecting Simple Tools for Complex Solutions
Most programmers are comfortable in their IDE but still click through file managers and manually handle repetitive tasks outside of it. You might know basic command line navigation, maybe even write the occasional script, but you're missing the real superpower: composition - the art of connecting existing tools to solve complex problems without writing any code. This episode reveals how thinking like a conductor rather than a programmer transforms your relationship with the command line. We'l...
Runtime Arguments
Wolf surfaces five fundamentals to becoming a better developer (that you probably didn’t even know you didn’t know)! This is a fiery one! Jim asks questions, and also questions Wolf's choices. Takeaways The problem comes first—ask more questionsStart with the simplest thing that could reasonably workMeasure before you optimize (but don’t be stupid)Understand what’s actually an errorTest so you can evolve, and so that you don’t waste time, money, and effortLinks Solution from Marlon for Jim's ...
