Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

66%
+2 −0
Meta Suggestion: Basic Linux skills compendium

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'...

posted 1y ago by LAFK‭  ·  edited 1y ago by LAFK‭

Answer
#2: Post edited by user avatar LAFK‭ · 2023-11-13T13:00:32Z (about 1 year 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 user avatar LAFK‭ · 2023-11-13T12:27:16Z (about 1 year 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.