S
stembolts
Break your system down with a block diagram. Define the minimum functions and properties for each block. Then create an inventory from that.
In short, break down your problem into smaller bits. No one knows your requirements and vision better than you. You can do it.
I use a laptop connected to some external drives managed by a Sabrent 5-Bay Hard Drive Docking Station. The laptop runs Ubuntu Server and hosts media via Jellyfin on raid5 logical volumes shared between disks (to increase read speed).
I learn by writing documentation. Learn how you learn, that information will be priceless in value to you.
First time hearing of a"demake", neat.
I agree with your sentiment regarding confusing syntax, however I think that confusion simply requires a calculated approach to dispell it.
It's a prime example of why I use scripts as reminders as much as I use them functionally. I work out the syntax once.. save it to an example script, then save myself 20 minutes of remembering by just $ cat ./path/to/script.sh and copying said syntax.
So if you can change your workflow such that learned things stay around as examples, I feel that you will pick it up much more quickly :)
awk
..for parsing the output of other commands quickly and simply. Then that parsed output can be used to create simple log messages or be passed as args to other scripts. Powerful.
The comment is stating that you treated it as a gotcha moment. Which I agree with.. I mean, just read your post again.
What the other commenter described is exactly what you did. Stating otherwise means you may need to pause and ask yourself, "Am I deluded?"
Or even better, just ignore us all and reassure yourself that we're all crazy. That probably feels the best, and we should always just go with what makes us feel good.
Anyway, just come back and check the vote tallies later if you have any doubt that what I say is the prevailing opinion.
And of course, if I'm wrong, I'm wrong. Sometimes I am wrong. Are you?