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 ...
4: Functional Programming - You're probably already doing it
Runtime Arguments
28 minutes
4 months ago
4: Functional Programming - You're probably already doing it
People throw around the term Functional Programming but it's not always clear what they mean. In this episode, we describe what it is and how you could already be doing it. Show notes and things to think about: Functional programing isn't academic. It isn't overwhelming. It isn't impossible to use. It isn't inapplicable to ordinary problems like the ones you're solving right now.You can use functional techniques in almost any modern programming language. In fact, you p...
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 ...
