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.

@nolan I would prefer to not rely on my IDE for many things, because I have no idea (and don't want to impose) what editor other contributors are/will be using. Ideally, most checks and warnings are CLI programs that are able to run in CI, and you editor at best exposes those results in the context of your code to give you feedback sooner - but CI is always there as a guardrail.

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.)

@themystery @nolan Ha, I actually found out about it because I wanted to use that shortcut in VSCode, but it got in the way. I changed the shortcut to something else but can't remember what, though it was clumsy enough that I'm not really missing it.

@peregrine The Goldfinch by Donna Tartt is one of my all-time favourites, and Born a Slave by Trevor Noah is a very good book I read recently.

@nolan It's a GTK feature, so it won't work in most browsers or Electron apps. Appears to have been added in @gnome 3.28, so available since Ubuntu 18.04

@nolan Well, that method is still easier than switching to Text Editor/the Files location bar and pressing Ctrl+., which is what I've been doing so far. So thanks for that tip for when I'm not using Pinafore :)

I just saw a toot with an image that wouldn't load due to a choppy wifi connection. Luckily, the author had added a description of the image, so could still get the gist of it.

Which is to say, again: improving UX for the visually impaired helps a larger group than you might think.

@joacim Was going to suggest @Fairphone with @e_mydata as well. With the added bonus that you're reducing your contribution to the conflict mineral market.

/e/ supposedly has MicroG and should working with banking apps and all that. It's still in beta though.

@surma One complaint I've seen is that developers trying to debug problems with their users can not just ask for a screenshot, but will have to ask them to hover/focus the URL bar or use a different browser.

It feels like we're transitioning to a situation where it's getting increasingly difficult to blackmail politicians.

Not because they've got a squeeky-clean record. But because their voter base doesn't care.

That's not necessarily a bad thing, btw. Personally, I'm very happy that there are many successful politicians who are openly homosexual, for example.

In fact, it's practically unavoidable: as more and more of our lives are in permanent digital records, there is dirt on everyone.

@nolan I have exactly the same. Finally had a project that I could use it for recently, but then the desire to actually see that project to completion led me to switch back to a language I was already familiar with. Soon, though...

Just saw this quote:

> The person who says he knows what he thinks but cannot express it usually does not know what he thinks. (Mortimer Adler)

I feel like that should come with a disclaimer about speaking in a non-native language over a choppy video call connection.

Welp. Sigh. 

@Gina With that attitude only the worst-off person in the world would be allowed to feel sad. Something got blown off that you really need - you can feel sad about that while acknowledging that there are others that have it worse.

@nolan There's always the escape hatch of using data-testid, which is still less likely to be accidentally broken, but I've actually had to use that far less often than you might expect.

If I could make one software metaphor go away, it's the idea of code as Lego.

Abstraction is a balancing act between power and utility, and the idea that you should be able to combine everything with everything tips the scales all the way to power at the cost of even the slightest bit of usefulness.

A more apt metaphor would be Tetris: we have some idea of the general shape of the blocks that are yet to come, but we'll occasionally be wrong, yet we'll still have to try to fit them together.

@estebanm It's a portfolio rather than educational and I wouldn't call it beautiful, so it's probably not exactly what you're looking for, but it does sound relevant to your interests:

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!