fwiw I find "optimize for readers over writers" arguments to prove too much. Boilerplate has costs for readers too
-
-
Replying to @wycats @batemanchris
definitely a balance. Prudent to avoid dogma.
1 reply 0 retweets 0 likes -
Replying to @kentcdodds @batemanchris
confirm. My personal style is to use precious signal to point out unusual things, not common things.
2 replies 0 retweets 1 like -
Replying to @wycats @batemanchris
seems like a good approach. For me, reassignment is uncommon, so it's useful to call it out with let.
1 reply 0 retweets 1 like -
Replying to @kentcdodds @batemanchris
but function parameters are `let` bound, which means (1) not uncommon, (2) no visual signifier
2 replies 0 retweets 1 like -
I used `const-first` for a few months and hit this again and again as a source of mistakes.
1 reply 1 retweet 1 like -
Another common cognitive confusion for me: const options = {}; // later http://options.name = "kent";
1 reply 0 retweets 1 like -
Rust doesn't have these issues and I appreciate const-first in Rust. Too many inconsistencies in JS for me.
1 reply 0 retweets 2 likes -
Replying to @wycats @batemanchris
interesting. I have yet to have cognitive issues personally, but it's great to hear other perspectives.
1 reply 0 retweets 0 likes -
so you prefer let most places?
2 replies 0 retweets 0 likes
In my own projects, I use const at top of modules with SCREAMING_CASE, otherwise let. Otherwise follow local style
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.