I hate to ask, but here goes.

I'm looking for a role as a #frontend #developer. #Contracts or #fulltime. Preferably #UK where I have previous #remote work ex from.

I've been looking a while and nothing with the right fit has come along. Work life balance is super important. If UK, happy to work completely in your timezone!

My site is rusingh.com and I'm happy to email you my CV/resume. Will start immediately once we're on the same page. 💯

#Boost please?


I just did away with my makeshift home office setup, and it's great to have a living room dedicated to living again.

I also feel like I've nailed the future of office work: working with friends. It's still easy to do social distancing and I get a short commute by bicycle, without missing out on friendly banter during the day.

This looks great: property-based end-to-end testing.

Define some general conditions that should hold (e.g. the value of this input field should always be shown here), and it will perform arbitrary actions in your UI to see whether they break the condition (e.g. clicking this button replaces the displayed value by [object Object]).


The resemblance between this endangered animal and the browser named after it is uncanny.

Libro FM is looking for Blind/VI developers! Send an email. No complicated account or lengthy resume process. Send links. They really care about and openly welcome Blind devs. blog.libro.fm/hiring/

I've been using git worktree a couple of times recently. I don't think I'll ever go back to stashing.

I have just been informed that apparently Web Replay is being developed as a separate product rather then as part of the Firefox DevTools: webreplay.io

Show thread

Just found out that the Web Replay experiment of the Firefox DevTools was discontinued.

Such a shame; it really would have been a killer feature: developer.mozilla.org/en-US/do

Screw chaos monkey randomly shutting down production machines to test resiliency

People should be given random vacation days to see what knowledge isn't distributed

Darn it. I listened back some of the clips I recorded for commonvoice.mozilla.org. Turns out I've got the fake "look at me I'm trying to pretend I'm posh English even though I'm clearly not" accent.

This is also a good way to introduce tests to an untested code base: ignore all existing files for the coverage report, then set the threshold to 100%.

Arbitrary thresholds are a great way to invoke Goodhart's law. Code coverage should be an assistant, not a stick to hit you with.

Show thread

I really like this quote:

> a lot of the value of code coverage data is to highlight not what’s covered, but what’s not covered.

Be liberal about marking code not worth writing tests for skipped for the coverage report, and set your coverage threshold to 100%. The report can then remind you about parts of your code you meant to but forgot to write a test for.


We're going to release the things I've been working on for the past couple of months officially in a bit, and I'm more excited than I expected.

It's been open source and publicly accessible for a while, but now it's in an 🌟announcement🌟. Shiny!

I just stumbled on this and it looks amazing: decentralized endorsement of publications!

Anyone tried it or knows of it?

#research #academia #publication #decentralization

Just realised that I never really shared that I wrote a small npm package to send a while ago. It's automatically tested against the full webmention.rocks test suite, work in both Node and the browser, and includes type definitions.

This work was supported by @NGIZero and is currently used in production on plaudit.pub.

You can find it here: npmjs.com/package/webmen

I just can't get over how great StreetComplete is. It looks fantastic, is incredibly easy to use, and actually makes it fun to contribute data about the Real World for the benefit of everyone.

If you run Android, be sure to give it a try: github.com/westnordost/StreetC

SemVer seems clear enough, but in practice often leads to questions like "is this bugfix a breaking change?" or "shouldn't a major new feature be a major release?"

I wrote a post to collect and answer those questions:


The tl;dr is: don't think about what your version "means", but about what conclusions you want your package's consumers to draw. That change of perspective can help resolve many common dilemma's.

Make sure your projects have a clear, descriptive name.

For example, consider these memorable projects that have had massive impact:

- property-based-dom-access
- data-bind-view
- state-function-view
- automock-tester
- server-side-javascript
- javascript-browser-automater

(Ten internet points to whoever can name the actual projects.)

Show more

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!