Came up with a cool strategy to make prod debugging of browser JS easier: keep all asserts, replace message with err code, report err code
-
Also it makes sense for having some sanity in module territory. I'm relying on type systems in my framework-land code.
Yeah, I dont want to write compile-to-js languages of any flavor; asserts + unit tests help catch most errors for me (:
-
-
(They can't solve my bad design decisions tho lmao)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.