extensions.gnome.org/extension is a clipboard manager with a nice touch: you can see the current value in the UI!

Occasionally I think I've copied something when I haven't (or vice versa), so making the state visible seems really helpful.

Zulip has some really nice onboarding features. You get a private thread to learn the UI, and it helpfully lets you ignore any unread messages.

Rewriting, debugging, and fuzzing a new manual format in OpenBSD: openbsd.org/papers/bsdcan15-ma

I particularly enjoyed the root cause analysis of the fuzzing bugs found.

By contrast, I don't think code coverage services have an obvious default featureset. I personally like to see coverage trends, the ability to explore coverage, and context on tests.

I lean towards codecov at the moment, but coveralls has advantages too.

Show thread

Playing with GitHub actions today, and I realise how much testing services have become a commodity.

I really appreciate GitHub's organised, collapsible UI for output. The featureset seems comparable to alternatives though.

(The idea of an ecosystem of actions is tempting!)

Emacs package of the day: amx.


This makes your M-x better, by prioritising recently used commands, hiding irrelevant commands, and showing shortcuts!

(Shown with the excellent counsel package here.)

`npm outdated` is a useful command that colour-codes output based on semantic versioning compatibility.

I wonder if time information would help too? If I'm on 1.0.1 and 1.0.5 is the latest, but 1.0.1 came out in 2010, that's useful knowledge.

Cute feature I hadn't previously noticed in node: it will evaluate pure expressions before you've even pressed enter!

Looks like this even works for functions that it can recognise as having no side effects.

Jest has this wonderful feature where it suggests other equality checks you might want to consider if your test fails. It's super helpful and a really nice touch.

I've been experimenting with multiple link colours on my notes website: notes.wilfred.me.uk/HomePage

I tried mediawiki-style red for nonexistent links, but it confused my test user.

I'm relatively happy with grey here, but I can't think of other sites with different colour links.

Here's a cute lint feature I haven't seen before: an estimate of how long an issue would take to fix!

Link: codeclimate.com/github/Wilfred

(It's a really small project, so 2 hours seems pessimistic.)

I often merge simple PRs from my phone, so it's exciting to see a native GitHub app: github.blog/2020-03-17-github-

UI density still seems less than the web UI though.

Alternatively, built-in physical keyboards could come back into fashion. Writing on a Palm or a Nokia Communicator was much nicer.

Show thread

This is my favourite genre of web design: simultaneously advocating for a style and demonstrating why you should/shouldn't use it!


I built a thing this weekend: autogenerated emoji summaries for my new blog/wiki!


It's good to see websites acknowledging the grim irony that you need cookies to remember users' cookie preference.

I'm surprised that there isn't a microformat specification for this yet. If one browser enabled users to blanket hide all of these I think others would follow.

I'm taking an amateur radio exam today and reviewing mock papers.

I'm struck that they explicitly teach people to ignore trolling! This is the first time I've heard official advice on dealing with troll behaviour. (The expected answer is D in both cases here.)

Pharo's git integration (using Iceberg) is shockingly good.

All your commits are well-structured changes, so you can toggle at class/method granularity what you want to commit. Thanks to Iceberg, these classes in your *live* image serialise to text files! github.com/Wilfred/mal_pharo/c

The Rust mascot is a crab called Ferris. I've only just realised this is a pun! Ferris/ferrous.

Show older

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!