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.

Great TIL, I hate it.

Excellent how the page alludes to other horrible things to imagine, like “don’t pour hot oil into your ear”, and “don’t pour it in if there’s a hole in your eardrum”

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 🤔

I use VSCode with config options to disable telemetry. Probably not perfect but good enough for me, I’m very happy using VSCode

Now you switched when you shouldn’t have idiiot

Oops yeah I did

Haha, got a “network error” on my first attempt so clicked send again, I guess it did go through the first time after all :D

You can tell when I’ve started to lose hope when my commits start becoming “Probably won’t fix CI”

Yeah, there currently seem to be a bunch of rough edges with Lemmy. Another is that iirc editing a comment increases the comment count shown on a post.

Nothing that can’t be fixed though, and it’s encouraging how good Lemmy feels already compared to reddit (for me at least).

Yeah, there currently seem to be a bunch of rough edges with Lemmy. Another is that iirc editing a comment increases the comment count shown on a post.

Nothing that can’t be fixed though, and it’s encouraging how good Lemmy feels already compared to reddit (for me at least).

When it happens docker+wsl become completely unresponsive anyway though. Stopping containers fails, after closing docker desktop wsl.exe --shutdown still doesn’t work, only thing I’ve managed to stop the CPU usage is killing a bunch of things through task manager. (IIRC I tried setting a cap while trying the hyper-v backend to see if it was a wsl specific problem, but it didn’t help, can’t fully remember though).

This is the issue that I think was closest to what I was seeing https://github.com/docker/for-win/issues/12968

My workaround has been to start using GitHub codespaces for most dev stuff, it’s worked quite nicely for the things I’m working on at the moment.

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.

9 minutes 34 of audio bible anyone?? https://youtube.com/watch?v=mdEttg1lN0I

deleted by creator

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”

I’ve often ended up guessing what things do and messing things up.

One example is when I couldn’t remember the difference between git checkout -b and git checkout -B, so in my infinite wisdom I decided to use -B because surely capital letters are better! Tried using it to switch back to a branch, and… Yeah, that was annoying.