APFS (Apple filesystem) calculates free/used space in a non-intuitive way which causes users to be confused about file size.

Link from the same publication on this exact topic.

https://eclecticlight.co/2020/04/09/where-did-all-that-free-...

I made this! Thanks for posting it, I'll gladly answer any questions.

The samples are available here on GitHub: https://github.com/matteason/scotrail-announcements-june-202...

...and here on Google Drive: https://drive.google.com/drive/u/0/folders/172W6sXnvlr7UcNLi...

We crowdsourced transcriptions for all the clips and Simon Willison built an interactive dashboard to explore them: https://scotrail.datasette.io/scotrail/

The announcements are read by voice-over artist Alison McKay: https://www.alisonmckay.com/

Wrote professionally about taste in a previous life. It is related more closely than we expect to techne or competence from physical knowledge.

When we think of poor taste, we tend to think of symbols that are separated from their function and meaning, where instead of representing that, "I do this thing," something gaudy says, "I have this thing!" That's what crassness is, and it comes down to our relative apprehension of the real vs. the represented, where typically, something real is powerful independent of who is observing it, and the representation is not. It's whether something legitimately represents power. Taste may be an instinct for honest signals, which would seem like its own sort of intelligence.

Viewed this way, taste is the expression of what you percieve to be power based on your experience, good taste is the inverse of the distance between them, and poor taste is measured in the gap between what is affected and of-what it is the effect.

That difference between effect and affect is one of the sneakiest bits of the english language and perhaps even the culture's most cunningly set trap. Do not underestimate the value of good taste, it's an intuition about power.

I try to start any UPDATE or DELETE by writing out a transaction first:

    BEGIN TRAN;
    
    -- TODO: update statement
    
    ROLLBACK;

Usually I'll run it with the ROLLBACK first, to confirm that it impacts the number of rows I'd expect, and only then change my ROLLBACK to a COMMIT.

A long time ago, my boss at the time taught me a valuable lesson: every meeting needs an official record(/log/minutes/whatever) documenting all noteworthy decisions (D), tasks (T, with deadline and responsible person), and information communicated (I), with that record being sent to all participants by end-of-day.

The reasoning being simple:

If anything of consequence was discussed in the meeting, then the official record is a valuable documentation (and the basis for the next meeting).

If nothing of consequence was discussed in the meeting, then the meeting was a waste of time and should never have taken place in the first place. Somebody wasn't prepared for the meeting they scheduled.

Like a good commit message, an official record as described above is cheap (doesn't take more than 2-3 minutes to write) and often delivers a fantastic ROI.