Live data from Hacker News

From novice to master, and back again (2013)

blog.djmnet.org

101–110 of 150 posts

Re: From novice to master, and back again (2013)

#101
Reading the comments here I'm under the impression that people think OP wrote the manual for `su`, but the interesting fact here is he wrote the GNU coreutils implementation of `su` itself.

Debian (stable, at least) doesn't use his version anymore. The HISTORY section of the current manual says

> This su command was derived from coreutils' su, which was based on an implementation by David MacKenzie. The util-linux version has been refactored by Karel Zak.

Re: From novice to master, and back again (2013)

#102
Once I had a question about APACS, circa 2008, not a lot of information. found a tool using it, some lateral browsing, dns, simmilar usernames and finally i got to talk to the authour of the tool who gladly helped me :)

I was discussing how the only info I found was in a remote wikipedia article, yet incomplete. the guy told me he had written that article too.

good times

Re: From novice to master, and back again (2013)

#103

Earlier quoted context omitted.

Sorry, but ”computers work by ones and zeroes” is one of my pet peeves. It is true in the sense that 1 and 0 are common representations for true and false in computer science, but really, it is false and almost certainly establishes magical thinking in the layperson. Modern computers run on electricity, and in electrical circuits such as computers, true/false is represented as a transistor semiconductor being in a co…

> 1 and 0 are common representations for true and false in computer science Long before standing for true or false, 1 and 0 have stood for the presence or absence of something arbitrary, so I don't see any issue here.

In fact, if we consider the presence or absence of truth in a statement...

(There is no completion. The trailing off is intended.)

Re: From novice to master, and back again (2013)

#106
I can't even tell you how often this happens to me. People come to me because I wrote something and I then tell them: "Let me go read the manual" (because I can't remember what I did a month later, so I'm always consulting my own docs).

I always tell people: "You think I wrote this manual for you, but I'm not that altruistic. I wrote it for future me."

To be fair, not exactly the same thing. I typically remember I wrote it, just not what it does or how it works. :-)

Re: From novice to master, and back again (2013)

#107
post #94

Earlier quoted context omitted.

Worse : You Google a question and realise you yourself asked it many moons ago and it never got answered.

Oh man this happened to me last month. I was even wondering how this guy had the exact same issue that I was having and only realized after a while that it was literally me who posted it. I eventually found an answer and decided to post an answer in case future me forgets it again.

I've also had this happen, but never figured out the solution.

This is especially frustrating because your question is likely to pop up first in your search results because you probably phrase things the same way even years later!

Re: From novice to master, and back again (2013)

#108
post #97
post #35

Earlier quoted context omitted.

I go through the same thing but with a few "popular" GitHub issues. Every time I encounter those bugs I Google it and the first result in my comment on the issue that explains the workaround I used. That's probably how early Alzheimer feels.

I sometimes have to go back to GitHub issues I created, that I bookmarked for this specific reason. I think that the Internet has modified how our brains retain information. I don't think this is an original idea, but I've observed that I'm real good at indexing where I saw some piece of information and very poor at storing the actual piece of information. I have to physically write things down to commit them to reca…

I suspect our brains have always been better at remembering meta-information than information itself. E.g. where you last saw an item of clothing vs the configuration of colours on it. In most cases this makes sense, and is essentially a space-saving trick, but there must be some point at which the meta-info becomes too inaccessible or too slow to utilise that remembering the full detail directly becomes worthwhile. Convincing your brain of that before it becomes too late can be a regular challenge with so much readily available externally stored information.

Re: From novice to master, and back again (2013)

#109
post #72

Earlier quoted context omitted.

I use the `ln` command a lot. I use the `man ln` command _almost_ as much.

What finally got the `ln` argument order engraved in my mind was learning that you can skip the destination argument: ln -s /foo/bar/baz will create a soft link in the CWD named baz, pointing to /foo/bar/baz. So you see, if you know that you can always skip the destination, then, logically, the source must be the first one!

I'd say the easiest way to remember the argument order is that it's conceptually the same as for mv and cp: ln -s x y is the closest possible symlink-analogue of cp x y.

Re: From novice to master, and back again (2013)

#110

Earlier quoted context omitted.

I think what a lot of people don’t get about the Unix command line is that learning to use the tool is part of the experience. Sure I forget the precise flags to get various tools doing what I need, but browsing the man page and rediscovering the breadth of the tool is half the beauty.

What? That’s some intense Stockholm syndrome right there.

How so?

I remember the times before I learned Bash and the Unix userland. Those where dark times. I was stuck on Windows 98, which I really didn’t like. It just felt so needlessly crippled. When I discovered Bash, Debian, the Unix way, it felt like a breath of fresh air.

These days I’m on macOS. And one of the best things about it is that it’s a great desktop operating system, with a Unix under the hood. The userland Apple ships is quite dated, but that’s easily solvable by installing GNU Coreutils etc via Homebrew.

Post reply on HN