It probably really depends on the project, though I’d probably try and start with the tests that are easiest/nicest to write and those which will be most useful. Look for complex logic that is also quite self-contained.

That will probably help to convince others of the value of tests if they aren’t onboard already.

Yeah they’ve put them in a couple places, It’s pretty bad. Had to work out how to create a custom uBlock Origin rule to block them.

I’d be happy if we’d just accepted “referer” as the correct spelling for everything, but instead we have the “Referrer-Policy” header, so now I need to check the correct spelling for anything involving referring…

I do sort of like the idea that because we want to keep backwards compatibility on software we just change the language instead since that’s easier.

What sort of features 🤔

My experience using docker on windows has been pretty awful, it would randomly become completely unresponsive, sometimes taking 100% CPU in the process. Couldn’t stop it without restarting my computer. Tried reinstalling and various things, still no help. Only found a GitHub issue with hundreds of comments but no working workarounds/solutions.

When it does work it still manages to feel… fragile, although maybe that’s just because of my experience with it breaking.

Assuming x and y are totally ordered 🤮

(for anyone wondering, a monad is just a monoid in the category of endofunctors)

Ah, that’s too boring. I have a range of responses to pick from to keep things interesting:

• LGTM
• Nice
• Looks good
• Thanks
• Looks great
• :thumbsup:
• Looks good to me
• :shipit:

For me, no text means “I haven’t really reviewed this properly so don’t want to write anything that could be used against me if (when?) this breaks something in prod”