hashkb

Next time you're talking to a capture-the-whole-board believer, if you want to blow their mind, first do some basic combinatorics to explain how many captures you'd need for the variation on a basic board; then ask them how many positions there are on a wah.

I had the pleasure of working with Jeff in ... I want to say 2012 - he taught me so much, is a fabulous developer and teammate, and we had some great times together.

Edit: mise rocks.

But why? The best thing about vim is normal mode. Emacs with evil-mode is so cool.

I love this take. I was a die-hard Vim/Neovim zealot... but these days I absolutely love the ecosystem of tools that support normal mode. For so long hand-cramping emacs keybindings were sort-of-standard-in-a-few-places.

If you're not convinced vimming is the best way to interact with your editor, you probably haven't seen a really proficient vimmer.

You can mock the RNG. You don’t need to test/prove it’s random, you need to test your code which is not random.

You'd have a lot more time to find and boot them prior to running the lottery. Assuming you didn't/couldn't detect them, at least you spare your users the anxiety and inconvenience of the on-sale while they get screwed.

I don't understand what's so hard about this problem - if you have a platform that's impacted by bots and scalpers, and if you want to do the right thing, or give the appearance of doing the right thing with almost no cost to yourself or your business, you should release your product in a fair lottery with reasonable purchase limits.

You have plenty of time before the product is released to register and verify everyone. You completely avoid traffic issues. Accounting is easy - you'll sell out when you run the lottery. You'll build a reputation for releasing inventory fairly and without causing undue stress on your customers, and avoid the suspicion that you're in cahoots with the scalpers (looking at you, Ticketmaster).

I'm accustomed to stressing out over concert tickets and struggling to get gaming consoles, and have a deep hatred of scalpers and the platforms that enable them, but I had no idea that scalpers were ruining the educational/hobby markets too. That seems really low.

You can build very fast reloading yourself, easily. If I'm smart with persisting state on the client, I find I don't really miss "hot" reloading.

Or easily write your own dev server. Once you use the API instead of the CLI, if you have any experience with Express or Connect it's trivial.

I'm trying to improve discourse by fighting against the downvote. It's my opinion it harms discourse significantly. It's low signal, and not constructive. It has an obvious chilling effect on dissent. Nothing upholds echo chambers more than the downvote.

You could try. I'd assume it was downvoted by folks who perpetuate said double-talk. If there was a defense, they'd have articulated it. But, since anonymous downvoting is easier and less risky, that's what happens. Silencing the discussion about downvotes is a meta downvote that we shouldn't accept just because it's in the guidelines.

Management often already got a deal or has worked their tech choice into a financial projection.

Sometimes, they are even right. And "I told you so" rolls downhill.

Screw the site guidelines - drive-by downvoting this comment is highly suspicious, and cowardly.

I think you're in a tiny minority but I'd love to hear more about how it impedes you.

Just to add on to this - remember the first time you saw syntax highlighting? And before that, the code was all in one color? You didn't know you needed it before, but you didn't go back, did you?