4 ms·

I do not understand professional hackers working just off a laptop. Ability to take my work wherever I want with absolutely zero context switch.

by gruseom 14y ago

dredmorbius 14y ago
Sad but true. State retention/replication is among the biggest hassles of my multiple computing environments. OTOH, it's also a pretty persuasive argument to leave work at work at the end of the day.
- jsilence 14y ago
  ssh dev tmux attach workon project
  - batista 14y ago
    We don't all work solely in the command line which makes the advice worthless.
    - tverlinden 14y ago
      Only some people work solely in the command line, therefore that advice is worthless? I don't follow your logic here.
  - dredmorbius 14y ago
    My shell work isn't the issue. Or rather in isolation it's not. I'll run upwards of 40-50 shell sessions (on multiple hosts, with screen sessions on many of them). The net state of all of those sessions, including spatial relations between shells and color coordination (helpful for state recognition) is the hard thing to replace. Note: it's not that I carefully choose the colors of all shells, but I do have a couple of scripts that will kick out terminals in either lighter or darker shades (lighter == remote terminals, darker == local) to indicate stuff whose state I want to specifically register. Full desktop sessions and browser state are the big ones. I might be able to look at NX or another remote desktop solution, but those would be at best poor substitutes.
sneak 14y ago
Depends on the work, but I've found that all my dotfiles (including .ssh and .screenrc and .vimrc) linked into a directory on Dropbox, as well as my Development directory (containing all my local copies of git repos) goes a long way toward achieving this. I _really_ didn't want to build a computer, and the iMac is _substantially_ faster than the equivalent-costing MBP (and also frees me up to travel with an Air). It's a useful tradeoff, I think.
- gruseom 14y ago
  Dropbox probably does take care of the biggest issues. But I really do mean absolutely zero. The reason I quit using an external monitor is that I'd organize my windows differently on it and then have trouble readjusting to the laptop. Especially when lines of code started wrapping that didn't wrap when I wrote them!
  - mpdaugherty 14y ago
    I actually started writing shorter lines of code once I got my large external monitor. I've found it's really convenient to set my editor to take up 50% of the screen vertically and have either a command line or browser on the other half of the screen (and reference windows on the laptop screen). In this setup, the editor is actually slightly narrower and taller than when full-screen on my laptop. Switching between screen sizes really made me realize the importance of making sure all my code breaks at column 80, which makes it easier to read in terminals, on other people's screens, etc. as well. Good practice, I think.
    - eternauta3k 14y ago
      I try to avoid line wrapping, but SQL statements usually force me to have some >80 char lines.
  - porkbird 14y ago
    I used to have a problem with readjusting window sizes and positions between the laptop and my 24" display until I discovered full-screen apps in the recent OS X. Now I just run the text editor full-scren on both
drhowarddrfine 14y ago
You don't need a laptop as your main dev computer to do that. Especially with *nix/BSD where you can ssh, and even port forward, all your applications from your main box through your notebook.

I do not understand professional hackers working just off a laptop. Ability to take my work wherever I want with absolutely zero context switch.

by gruseom 14y ago

I do not understand professional hackers working just off a laptop. Ability to take my work wherever I want with absolutely zero context switch.

dredmorbius 14y ago

Sad but true. State retention/replication is among the biggest hassles of my multiple computing environments. OTOH, it's also a pretty persuasive argument to leave work at work at the end of the day.

jsilence 14y ago
ssh dev tmux attach workon project
- batista 14y ago
  We don't all work solely in the command line which makes the advice worthless.
  - tverlinden 14y ago
    Only some people work solely in the command line, therefore that advice is worthless? I don't follow your logic here.
- dredmorbius 14y ago
  My shell work isn't the issue. Or rather in isolation it's not. I'll run upwards of 40-50 shell sessions (on multiple hosts, with screen sessions on many of them). The net state of all of those sessions, including spatial relations between shells and color coordination (helpful for state recognition) is the hard thing to replace. Note: it's not that I carefully choose the colors of all shells, but I do have a couple of scripts that will kick out terminals in either lighter or darker shades (lighter == remote terminals, darker == local) to indicate stuff whose state I want to specifically register. Full desktop sessions and browser state are the big ones. I might be able to look at NX or another remote desktop solution, but those would be at best poor substitutes.

sneak 14y ago

Depends on the work, but I've found that all my dotfiles (including .ssh and .screenrc and .vimrc) linked into a directory on Dropbox, as well as my Development directory (containing all my local copies of git repos) goes a long way toward achieving this. I _really_ didn't want to build a computer, and the iMac is _substantially_ faster than the equivalent-costing MBP (and also frees me up to travel with an Air). It's a useful tradeoff, I think.

gruseom 14y ago
Dropbox probably does take care of the biggest issues. But I really do mean absolutely zero. The reason I quit using an external monitor is that I'd organize my windows differently on it and then have trouble readjusting to the laptop. Especially when lines of code started wrapping that didn't wrap when I wrote them!
- mpdaugherty 14y ago
  I actually started writing shorter lines of code once I got my large external monitor. I've found it's really convenient to set my editor to take up 50% of the screen vertically and have either a command line or browser on the other half of the screen (and reference windows on the laptop screen). In this setup, the editor is actually slightly narrower and taller than when full-screen on my laptop. Switching between screen sizes really made me realize the importance of making sure all my code breaks at column 80, which makes it easier to read in terminals, on other people's screens, etc. as well. Good practice, I think.
  - eternauta3k 14y ago
    I try to avoid line wrapping, but SQL statements usually force me to have some >80 char lines.
- porkbird 14y ago
  I used to have a problem with readjusting window sizes and positions between the laptop and my 24" display until I discovered full-screen apps in the recent OS X. Now I just run the text editor full-scren on both

drhowarddrfine 14y ago

You don't need a laptop as your main dev computer to do that. Especially with *nix/BSD where you can ssh, and even port forward, all your applications from your main box through your notebook.