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 ...
8: I’ve Been Using AI to Code for a Year. Here’s What I Learned
Runtime Arguments
1 hour 19 minutes
2 months ago
8: I’ve Been Using AI to Code for a Year. Here’s What I Learned
If you’re expecting AI to write entire programs for you while you sit back and watch, we're going to disappoint you right up front—that’s not what these tools do well, and chasing that fantasy will waste your time. But what if we told you there’s a tool that could help you interpret cryptic error messages, navigate tricky syntax in unfamiliar languages, write the documentation you always skip, and spot those needle-in-the-haystack bugs that eat hours of your day—but only if you understand wha...
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 ...
