3 ms·

Nothing. I work on many different systems from time to time. I don't like to get too used to things that aren't universal. I have found out (the hard way) th

by brk 17y ago

Nothing. I work on many different systems from time to time. I don't like to get too used to things that aren't universal. I have found out (the hard way) that relying on convenience can bite you in the ass when it's 3AM and you've been up for 67 consecutive hours and you execute some keystrokes from habit and they don't do what you expected. I'll admit, I probably cripple my productivity overall for working this way, but it's what I'm used to.

karanbhangui 17y ago
Out of curiosity, why not just wget or curl -O a file from a webserver?
- brk 17y ago
  Most of my work the last few years has been in the compliance and IT or Physical security (or converged) space. The machines I am working on are not my own, and often have no access to the Internet directly. However, I'm generally doing more "editing" than "coding" so it's not a major limitation anyway.
pyre 17y ago
> I have found out (the hard way) that relying on convenience can bite you in the ass when it's 3AM and you've been up for 67 consecutive hours and you execute some keystrokes from habit and they don't do what you expected. You really could say that about anything. You could say that one shouldn't program in dynamically-typed languages because 'one day' you'll have to program in a statically-typed language and all your habits will 'bite you in the ass.' I think that you should really blame this part: > and you've been up for 67 consecutive hours Unless you're trying out for the SEALS, I don't think this is normally part of any job description. And I hardly think this is some sort of 'common case' that you should be planning for. There's a difference between preparing for the worst and over-preparing for the worst.
- brk 17y ago
  Don't get me wrong, there are many conveniences that I DO use. However, for editors I've just always preferred to stay as basic and reliable as possible. vi is quick, easy, simple and has been on every *nix machine that I've ever walked up to. Relying on customizitions beyond that is, for me, sub-optimal. I have had more than a handful of workdays that spanned 2 or 3 or 4 continuous days with little or no sleep at all (although thankfully not in several years). In those cases we were usually recovering from planned maintenance gone wrong. In one case I was trying to edit/update some config files, force software upgrades into a bunch core switches and dispatch pilots with spare parts. It was helpful, to me, to be able to rely on the basics as I hopped through SSH sessions from server to server (but, I did use host keys to speed my logins). My case is moreso for edits and small customizations and not long sessions of coding, so I really don't NEED a whole lot beyond the basics of what I can memorize.
jacquesm 17y ago
> when it's 3AM and you've been up for 67 consecutive hours That can't be healthy. My longest stretch (age 17) was something like that and I fell down half a flight of stairs without waking up when going home. Please be careful.

by brk 17y ago

karanbhangui 17y ago

Out of curiosity, why not just wget or curl -O a file from a webserver?

brk 17y ago
Most of my work the last few years has been in the compliance and IT or Physical security (or converged) space. The machines I am working on are not my own, and often have no access to the Internet directly. However, I'm generally doing more "editing" than "coding" so it's not a major limitation anyway.

pyre 17y ago

> I have found out (the hard way) that relying on convenience can bite you in the ass when it's 3AM and you've been up for 67 consecutive hours and you execute some keystrokes from habit and they don't do what you expected. You really could say that about anything. You could say that one shouldn't program in dynamically-typed languages because 'one day' you'll have to program in a statically-typed language and all your habits will 'bite you in the ass.' I think that you should really blame this part: > and you've been up for 67 consecutive hours Unless you're trying out for the SEALS, I don't think this is normally part of any job description. And I hardly think this is some sort of 'common case' that you should be planning for. There's a difference between preparing for the worst and over-preparing for the worst.

brk 17y ago
Don't get me wrong, there are many conveniences that I DO use. However, for editors I've just always preferred to stay as basic and reliable as possible. vi is quick, easy, simple and has been on every *nix machine that I've ever walked up to. Relying on customizitions beyond that is, for me, sub-optimal. I have had more than a handful of workdays that spanned 2 or 3 or 4 continuous days with little or no sleep at all (although thankfully not in several years). In those cases we were usually recovering from planned maintenance gone wrong. In one case I was trying to edit/update some config files, force software upgrades into a bunch core switches and dispatch pilots with spare parts. It was helpful, to me, to be able to rely on the basics as I hopped through SSH sessions from server to server (but, I did use host keys to speed my logins). My case is moreso for edits and small customizations and not long sessions of coding, so I really don't NEED a whole lot beyond the basics of what I can memorize.

jacquesm 17y ago

> when it's 3AM and you've been up for 67 consecutive hours That can't be healthy. My longest stretch (age 17) was something like that and I fell down half a flight of stairs without waking up when going home. Please be careful.