noughtnaut

Look, slack is 1000% better than Teams will ever be. But, Slack is also enshittifying themselves, eg. with their 3-month event horizon.

Anything Slack can do, Mattermost does – and Mattermost is free, open source, and self-hostable.

This is my hill.

Check the capacitors anyway please.

🎶 Es fährt ein Zug, nach Nirgendwo…

(and that’s all I can remember from the song, which I heard on the 80’s Hit parade)

I have never put it into words like that, more like “make zero assumptions”.

I suppose that being overly thorough can make documentation prone to becoming tedious (unless cares is taken to not talk down to the reader) or too tightly coupled (incurring the need to be updated more often as details of the process change).

How do you usually deal with that aspect? What I do is to make the documentation easily skimmable (for advanced readers) and just accept the need for rework.

You’re brutal. You’re not wrong tho.

Reluctant upvote

I’m grateful to you for digging those up.

As well as the yeet keyword, I’m really friggin’ diggin’ this. [modernisation required]