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
-
-
Replying to @yoshuawuyts
Was surprised to see the asserts in your test snapshot code. Interesting to see explanation.
1 reply 0 retweets 0 likes -
Replying to @TatumCreative @yoshuawuyts
Also it makes sense for having some sanity in module territory. I'm relying on type systems in my framework-land code.
1 reply 0 retweets 0 likes -
Replying to @TatumCreative
Yeah, I dont want to write compile-to-js languages of any flavor; asserts + unit tests help catch most errors for me (:
1 reply 0 retweets 1 like
Replying to @yoshuawuyts @TatumCreative
(They can't solve my bad design decisions tho lmao)
6:36 AM - 21 Jul 2017
0 replies
0 retweets
1 like
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.