Stitcher for Podcasts

Get the App Open App
Bummer! You're not a
Stitcher Premium subscriber yet.
Learn More
Start Free Trial
$4.99/Month after free trial
HELP

Show Info

Episode Info

Episode Info: After 112 episodes, Michael can’t introduce the show, Allen pronounces it “ma-meee”, and don’t make Joe run your janky tests as The Pragmatic Programmer teaches us how we should use exceptions and program deliberately. How are you reading this? If you answered via your podcast player, you can find this episode’s full show notes and join the conversation at https://www.codingblocks.net/episode113. Sponsors Datadog.com/codingblocks – Sign up today for a free 14 day trial and get a free Datadog t-shirt after creating your first dashboard. Survey Says … Anonymous VoteSign in with WordpressWhen you want to bring in a new technology or take a new approach when implementing something new or add to the tech stack, do you ...?a.) Ask peer's if it's a good idea before implementing it? The voice of many carries more weight.b.) Ask the relative team lead if you can implement it? If the boss doesn't like it, it doesn't matter.c.) Implement a proof-of-concept and get stakeholders to weigh in? Because they don't know about it, they need to be sold on it.d.) Just do it. I can't waste precious time checking if other's like my idea.e.) Abandon it. It's already too much effort.vote News Thank you for taking a moment out of your day to leave us a review.iTunes: MatteKarla, WinnerOfTheRaceCondition, michael_mancusoStitcher: rundevcycle, Canmichaelpronouncethis, WinnerOfTheRaceCondition, C_Flat_Fella, UncleBobsNephew, alexUniqueAutonomous ErgoChair 2 Review (YouTube)Come see us Saturday, September 14, 2019 at the Atlanta Code Camp 2019 (atlantacodecamp.com)Are they cakes, cookies, or biscuits? (Wikipedia)Intentional Code When to use Exceptions In an earlier chapter, Dead Programs Tell No Lies, the book recommends:Checking for every possible error.Favor crashing your program over running into an inconsistent state.This can get really ugly! Especially if you believe in the “one return at the bottom” methodology for your methods.You can accomplish the same thing by just catching an exception for a block of code, and throwing your own with additional information.This is nice, but it brings up the question? When should you return a failed status, and when should you throw an exception?Do you tend to throw more exceptions in one layer more than another, such as throwing more in your C# layer than your JS layer?The authors advise throwing exceptions for unexpected events.Ask yourself, will the code still work if I remove the exception handlers? If you answered “no”, then maybe your throwing exceptions for non-exceptional circumstances.Tip 34 Use exceptions for exceptional problemsExceptions vs Error Handling Should you throw an exception if you try to open a file, and it doesn’t exist?If it should be there, i.e. a config, yes, throw the exception.If it might be OK for it not to be there, i.e. you’re polling for a file to be created, then no, you should handle the error condition.Is it dangerous ...
Read more »

Discover more stories like this.

Like Stitcher On Facebook

EMBED

Show Info

Episode Options

Listen Whenever

Similar Episodes

Related Episodes