Post History
Neat idea. In favour. Bottom-up is better I'd propose bottom-up here, instead of grand idea to strive for. I'd cut the list of topics down to real basics. I agree with @KarlKnechtel on Git. I'...
Answer
#2: Post edited
by
LAFK
·
2023-11-13T13:00:32Z (6 months ago)
I've put together a question to push this forward and linked it along with some points it shows
- Neat idea. In favour.
- ## Bottom-up is better
- I'd propose bottom-up here, instead of grand idea to strive for.
- 1. I'd cut the list of topics down to real basics. I agree with @KarlKnechtel on Git. I'd skip compilation from source until much later (not basic). Etc.
- 2. Basics means installation and commands. Perhaps a why Linux section.
3. Commands have aspects. Say, `ls`. `ls` shows `.` and `..`, why. Do not rely on `ls` output. Don't parse `ls`. Understanding `ls` styling and changing it (why some files are green, why some files have * next to them...). Not sure new users, indexing and SEO would like to see all that in one question.- ## Q&A format
- This forum uses only Q&A format. So, all points from the Linux Basics Curriculum (work term) need to have it. This means IMO:
- 1. having multiple questions about command aspects (see `ls` example above)
- 2. artificial Q&A, aimed at... yeah, who exactly?
- 3. getting new users to ask their questions and answering them - naturally, organically (I'm deliberately NOT raising the "how to be higher in search terms than other sites).
- I take it you mean 2. I'm leaning towards 1 for to me brevity of the answer is key. Just meat. Which also would mean examples.
- Neat idea. In favour.
- ## Bottom-up is better
- I'd propose bottom-up here, instead of grand idea to strive for.
- 1. I'd cut the list of topics down to real basics. I agree with @KarlKnechtel on Git. I'd skip compilation from source until much later (not basic). Etc.
- 2. Basics means installation and commands. Perhaps a why Linux section.
- 3. Commands have aspects. Say, `ls`. `ls` shows `.` and `..`, why. Do not rely on `ls` output. Don't parse `ls`. Understanding `ls` styling and changing it (why some files are green, why some files have * next to them...). Not sure new users, indexing and SEO would like to see all that in one question. Consider https://linux.codidact.com/posts/290222 and see that other natural questions could be "What is whatis and how it differs from apropos?" or "Why can't I get a man page for `exit`?" or "Is there a tool that gives me just man examples or do I need a shell script for that" or even something like "does anyone use `info` anymore and what is it for?".
- ## Q&A format
- This forum uses only Q&A format. So, all points from the Linux Basics Curriculum (work term) need to have it. This means IMO:
- 1. having multiple questions about command aspects (see `ls` example above)
- 2. artificial Q&A, aimed at... yeah, who exactly?
- 3. getting new users to ask their questions and answering them - naturally, organically (I'm deliberately NOT raising the "how to be higher in search terms than other sites).
- I take it you mean 2. I'm leaning towards 1 for to me brevity of the answer is key. Just meat. Which also would mean examples.
#1: Initial revision
by
LAFK
·
2023-11-13T12:27:16Z (6 months ago)
Neat idea. In favour. ## Bottom-up is better I'd propose bottom-up here, instead of grand idea to strive for. 1. I'd cut the list of topics down to real basics. I agree with @KarlKnechtel on Git. I'd skip compilation from source until much later (not basic). Etc. 2. Basics means installation and commands. Perhaps a why Linux section. 3. Commands have aspects. Say, `ls`. `ls` shows `.` and `..`, why. Do not rely on `ls` output. Don't parse `ls`. Understanding `ls` styling and changing it (why some files are green, why some files have * next to them...). Not sure new users, indexing and SEO would like to see all that in one question. ## Q&A format This forum uses only Q&A format. So, all points from the Linux Basics Curriculum (work term) need to have it. This means IMO: 1. having multiple questions about command aspects (see `ls` example above) 2. artificial Q&A, aimed at... yeah, who exactly? 3. getting new users to ask their questions and answering them - naturally, organically (I'm deliberately NOT raising the "how to be higher in search terms than other sites). I take it you mean 2. I'm leaning towards 1 for to me brevity of the answer is key. Just meat. Which also would mean examples.