Post History

I've been persistently advocating for an analogous effort in the Software community, and generally think that any Codidact community could likely benefit from doing something similar. As a practical matter, *everything that can meaningfully be "mastered"* has far more beginner practitioners than experts and masters. I saw your self-answered Q&A on `find`, which I understand is intended as an example (since you linked it here), and it looks like a great start.

I have one main caveat to offer here, specific to the idea of doing this here: it's important to distinguish between *general computer literacy* and Linux-specific literacy. Many useful skills are applicable to other operating systems, and can be even more fundamental than what you describe. In particular, before teaching the most common shell commands, the student needs to be familiar with the concept of a command line (many people coming from Windows or Mac will never have had to use one, even though the option has been there the whole time) and a current working directory. (GUI filesystem windows will teach the concept of a path; but most people will naturally associate each path with the *window* that has it in the title bar, and will associate that window in turn with "the operating system". They won't necessarily have a separate concept of a file-explorer process, and certainly won't mentally associate CWDs with processes).

Because of that, an effort like this would IMO greatly benefit from *coordination with* the Power Users community. Content here should focus on the issues, and aspects of issues, that are Linux specific (so for example, the idea of treating "text files" separately from "binary files" is platform-agnostic, but a Linux-specific treatment might cover shebang lines, along with having a stub to explain how Linux treats newlines in text files and how that differs from Windows). Unfortunately, I don't really know how best to accomplish that kind of inter-community coordination on Codidact.

Re your proposed list of topics, I would also hold off on Git stuff; that's rarely if ever relevant to non-programmers, and it's not really necessary to learn programming to "take back control" of the computer (just like how learning to drive using manual transmission, without cruise control, parking assistance features etc. doesn't require becoming a mechanic). By my understanding, the basic use of Git should be perfectly on topic for the Software community already.