Re:How To Write a Learn X the Hard Way
by jeebusroxors on Friday November 05, 2010 @10:20AM
(#1873248)
Just because you used it as an example here are a few quick resources to help understand filesystem layouts a bit better.
A real quick overview:
* http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
More in depth:
I prefer "man hier" at the command line. Much more succinct than either of those:
Re:How To Write a Learn X the Hard Way
by SkyMarshal on Friday November 05, 2010 @07:47PM
(#1875404)
Agreed, and man hier is always there if you forget something, don't have to go track it down on the web.
However, I found these useful too when I was learning it. Sometimes it just helps to read different explanations of the same thing till it sticks:
Cool! "TIL", as they say on reddit.
For non-redditers, TIL stands for "Today I Learned".
I feel the same. If you're lucky programs come with a readme.txt that explains the steps required to install it. Why the heck didn't they code that in shell script instead of english? It practically doubles the value of the software.
I used to not know that stuff. Then I installed Gentoo Linux, and was forced to learn it the hard way. I don't use Gentoo anymore, but installing it was like a crash course in how to get uncooperative Linux software to bend to my will.
This was years ago, so maybe Gentoo has become more user-friendly since then.
You're relentlessly modest.
Do you know C or would be interested in learning it?
Re:How To Write a Learn X the Hard Way
by raganwald on Saturday November 06, 2010 @01:50PM
(#1877360)
I used Lightspeed C many years ago to write a plugin for Aldus PageMaker. I later used C++ to make Jprobe Threadalyzer, but the experience was very different.
So honestly, I do not think I know C in any non- trivial sense.
I feel like a charlatan some days. On the other hand... I certainly can tell you if your "how to install" instructions are actually any good for reaching new programmers.