Paradox

If you can swing it. I really like bun for more traditional node stuff, because it has a ton of goodies built in, like a bundler

Iirc Wikipedia supports it for tab notation

Personally I much prefer lilypond. I wonder if this tool supports lilypond. Would love to have a workflow to scan sheet music and get lilypond out the other end.

MacOS has had caffeinate forever, and it works great

Back before they went “independent,” kind of. When Sears sent legal threats to take down a post exploiting an xss bug to make a joke about grilling babies, reddit had a big public discussion on it, and ultimately left the post up

I still reach for sass for a lot of things, but now you don’t have to, which is really nice

Not only that, but with toolchains like deno, it’s almost enjoyable

I wrote some telegram bots in deno and it’s got one of the cleanest deploy chains around, just compile to an executable for the target architecture, and SCP it over. Exec is statically linked, and so it just works

And if that public company has stock in the toilet it’s worth fuck all to unload

Recently I had to do an update to the underlying environment a codebase ran on. This was a somewhat involved upgrade and took a longer period of time than most of our work usually does. I did it in a separate worktree, so I didn’t have to constantly rejuggle the installed dependencies in the project, and could work on two features relatively concurrently

It also provides some utility for comparing the two versions. Nothing you couldn’t do other ways, but still useful

And in elixir/erlang we’re spoiled with loads of options, from ETS to mnesia

On the subreddits I moderated, I used a big regexp to preemptively filter their comments

Letting one through was a rare event

Sign language yes, real time captions no. Only whatever live transcription crap your phone or computer could do

I’ve only ever worked in one codebase that didn’t need feature flags, and even then we could have used them.

Graphite is ok, but honestly it’s a solution in search of a problem

Maybe if you have a massive pr, splitting it up like this works, but that’s really a planning failure. Stories should be smaller, and if you need to keep them separate for a long time, use feature branches

This is actually built into vsc

An ad hoc sorting system for a grid of tiles on an enterprise app

Instead of sorting across row wise, it sorted columnar. So it was

A E I M
B F J N
C G K O
D H L P

Instead of

A B C D
E F G H
I J K L
M N O P

This was a requirement from the CEO. Since we used this project (dogfooding) we stuck a secret search box/command palette in, which you could hit . and then type the name of the thing you wanted and click it

Oh look the guy with the $50 upvote is responding to the guy who doesn’t have any karma. Come on!

JetBrains users kind of live in their own weird bubble. Of the ones I’ve worked with, a decent number didn’t even know how to use git, they just relied on the built in vcs tools

Check out Elixir’s Ecto. You basically do write SQL for querying, it’s just lightly wrapped in a functional approach.

Either way it’s a no effort account and you can basically ignore them, as their contributions will most likely be garbage either way

How can I use a sonoff to control my fireplace guys?