I swear there's a lot of software engineering "best practices" out there that result from people talking themselves into believing that necessary workarounds weren't anti-patterns of a language's quirks but rather features of it.
-
-
In case you're wondering why this is bad: - You're assigning a variable you intend to do nothing with - You're forcing yourself into eating an exception - If you want to check for actual exceptions, you need yet more code - try-except patterns aren't for type checking
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Ugh, that solution totally violates my "3am, 3 month" rule: You should be able to understand any code (and comments) at 3am three days, weeks, months, years, etc. from when you write it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I know I sound like an obnoxious Haskeller here, but exceptions in general are a shitty, garbage abstraction resulting from the absence of an error monad
-
I disagree with Spolsky that error codes are better, but his criticism of them as "hidden gotos" (i.e. gotos with indeterminate targets) is spot-on
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.