This reminds me of an old joke I heard a while back, which is that the opposite of "it's like riding a bike" is "it's like the UNIX command line". No matter how many times you do it, you will have to re-learn it every single time.
I get a little offended by people who think stackoverflow is a character flaw. I go there because it will tell me things like if you get the arguments to ‘dd’ wrong you’ll zero out the drive you were trying to back up. That the function breaks if you pass in null for the second parameter. Or that it simply doesn’t work properly.
From novice to master, and back again (2013)
111–120 of 150 posts
Re: From novice to master, and back again (2013)
#112Related: From Novice to Master, and Back Again - https://news.ycombinator.com/item?id=9098635 - Feb 2015 (1 comment) From Novice to Master, and Back Again - https://news.ycombinator.com/item?id=8443981 - Oct 2014 (27 comments)
Re: From novice to master, and back again (2013)
#113I 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 wr…
you get into a task, you cram stuff in as you go, you finish it, and then you dump everything go onto another task.
i find my most valuable skill is to slow the pace to ensure retention of information
Re: From novice to master, and back again (2013)
#114Earlier 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…
Is 1 indicative of current flowing? Or not flowing? Is that consistent with a given chip, let alone an entire system? Is it always DC current, or can it be AC? In fact, is the 1 represented by current, voltage, and/or frequency? There's lots of different answers here in different contexts. The reason 1s and 0s are good is because they represent the information in the digital domain, not the implementation in the anal…
Re: From novice to master, and back again (2013)
#115Earlier 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…
You contradict yourself here. > (A) Modern computers run on electricity [not ones and zeroes] > (B) one could build a computer out almost anything that lends itself to both being on and off You got it right in B, which is exactly the point when people say computers are just 1s and 0s. Computers are a mathematical concept, not just some electrical device, as you seem to claim in A. The fact that you can build a comput…
Re: From novice to master, and back again (2013)
#116I wish there was even better way to preserve the context of what you were doing at the time (env variables, current path at the time etc).
Re: From novice to master, and back again (2013)
#117Earlier 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.
- byte and word size,
- endianness,
- semantics of what means what in a string of bits (think Two’s Complement, IEEE 754, ASCII, ISO-8859-1, Shift-JIS, Unicode),
- what it means to do certain operations on bits (Boolean algebra),
- how different binary operations can be constructed from transistors / logic gates (ALU design),
- how information can be retained in and recalled from memory (basically just flip-flops),
- how said memory is laid out with respect to internal/external devices and program regions (conventions!)
- how said memory can be addressed, and how information can be transferred between CPU and memory (bus architectures),
- how the computer architecture can be programmed to do things (processor instruction sets),
- and whatever I forgot just now…
And then some people design and build trinary computers, imagine that.
Re: From novice to master, and back again (2013)
#118I write this shit down so I don’t have to remember it, thanks. Back in the age of modems, when PPP was still the new hotness, I was proud of myself for memorizing the IP addresses for a few of the services I used regularly. Two or three times I got to punk my friends when the DNS servers got messed up, and they’re sitting with me in the computer lab wondering what else we could do to pass the time when they looked ov…
Re: From novice to master, and back again (2013)
#119Earlier quoted context omitted.
Where exactly does that message come from? Su itself, PAM, some other library?
I think it's from sudo, not su.
https://github.com/sudo-project/sudo/blob/SUDO_1_9_9/plugins...
But this particular message was removed in sudo 1.9.10:
https://github.com/sudo-project/sudo/commit/6aa320c96a376136
Re: From novice to master, and back again (2013)
#120I 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 wr…
this kind of job is very memory constrained you get into a task, you cram stuff in as you go, you finish it, and then you dump everything go onto another task. i find my most valuable skill is to slow the pace to ensure retention of information