This is the very essence of teaching. You must have something worth passing down. Something you have personally built-up, found valuable and can speak authoritatively on (the same root word as "author")

That means "principles not products".

In my experience only FOSS tools are stable enough for this to even be a possibility.

Most proprietary products have very little worth passing down, because they change every six months, which they have to do to keep making money.

> so I wanted to package them into book form. In the end, it's a > fairly eclectic set of topics.

Like many technical authors, the first book I wrote started out as a book for myself, just a collection of notes to remind me, then to use to teach others, and finally to release as a guide for complete strangers.

> You'll find full HTML, PDF and ePub versions (all built with Sphinx) at the link.

Thank you (and on behalf of future students)

I, too, got annoyed when Microsoft Office introduced the ribbon interface and moved everything around, but that's ridiculous. Entire industries standardize around proprietary software packages. Photoshop, Autocad, Resolume, Avid, Matlab, After Effects. Just because some stuff gets moved around doesn't mean people can't teach classes on how to do things with that tool. The screenshots just get outdated so you update the materials and keep on teaching.

And, to be fair there are Free Open Source applications that are chaotic - forever being forked and losing maintainers or having petty internal political spats.

But I think the comment below us by ozim nails it better; that there's a commercial incentive to keep changing stuff just for it's own sake, to lend the appearance of adding value.

Proprietary tools don’t have to change to keep earning money. They need to change to earn more money and grow profits. No one is investing in company that makes stable income and doesn’t have potential to grow 10x or 100x.

Also, I was straight-up surprised to see the spectrum from "this is a Folder" to "self hosting with vpn and email". I would enjoy hearing your experiences from folks who have read it because that realm of pedagogy fascinates me

I haven't uploaded the book source to the github but I guess I should so that it's easier to just send in PRs for typos and url updates.

Lots of people have only experienced computing through mobile and tablet devices that try to hide the file system. They need to be taught the concept of a file. File types. Folders. Permissions. Drives. File transfer between computers.

I’m not sure of the point of the book, generally people learn from doing, when they have a pressing need that provides the motivation, rather than learn new skills in advance “on spec”, so what’s really needed is a reference or wiki, or something like StackOverflow with better curation.

As for the point of the book, it's mostly intending to be a FYI about some useful tools that are out there. How can one know that regular expression find/replace is even a thing if no one ever tells you? I've found that people just manually do their migrations tediously without always wondering if there's a better way.