I haven’t played it in a while (due to performance issues,) but I remember parrying in Deadlock being really satisfying. The timing was so generous, and led to mind games, fakeouts, mixups and all kinds of shenanigans about when you parry, bait parry, hold parry so the enemy doesn’t know if you’ll parry, training the enemy to expect when you’ll parry before changing when you parry. And because melee isn’t the only focus in combat, it made it a nice skill expression without being a win button.

Last year in February I uninstalled the app on a perfect, 2000-day streak when I got the first whiff of AI; I’m probably never going back

As someone who’s worked on printer firmware before, it makes me really sad that a company can get away with making a consumer decide between getting access to any of the actually useful changes that engineers — who have no say over ink cartridge policy — put effort towards making the best product they could, or not having said ink cartridge policies forced on them.

From later in the article (emphasis author’s)

Earlier in this article I intimated that many of us are already dependent on our fancy development environments—syntax highlighting, auto-completion, code analysis, automatic refactoring. You might be wondering how AI differs from those. The answer is pretty easy: The former are tools with the ultimate goal of helping you to be more efficient and write better code; the latter is a tool with the ultimate goal of completely replacing you.

When I managed a pool, I remember the Virginia Graeme Baker act being something I was told about pretty early on; it was a prevalent enough of a thing that sometimes trying to start up my spa’s motor wouldn’t provide a clear enough suction, and the motor would shut off for safety. A properly managed pool should never have had this risk.

This is how I approach these: that square only has a single traffic light, not multiple traffic lights like the prompt is asking for