171–180 of 354 posts
One fateful day, VMWare and OS/X conspired to trash my shared filesystem, losing several days of uncommitted code in the process. Several days of uncommitted code? We need to have a heart to heart talk about your process.
$800 gets you a pretty nice laptop. I don't see the advantage of this approach at all.
One fateful day, VMWare and OS/X conspired to trash my shared filesystem, losing several days of uncommitted code in the process. Several days of uncommitted code? We need to have a heart to heart talk about your process.
So, this is something i worry about. I'm using time machine for backups, so i don't think i'll lose much ... but i'm sorta hazy about how i should be using svn for all these little incremental steps. I'm uncomfortable with committing code that's going to break the whole system. Should i be creating a branch for projects longer than an afternoon, and just committing that fairly often? I feel like eclipse's history is…
I'm a big fan of tmux* and vim but there's a limit to the complexity of system that you can develop efficiently with vim. A good graphical IDE used by a skilled operator will be more likely to generate correct, consistent code faster. If you're using vim and think you're developing as well and as fast as you can, you're probably wrong. * 17 years of screen and I've finally switched over to tmux. None of the features…
After spending a little under a year learning vim, I've found that while I make the occasional error in command mode, nothing has helped me "think in code" quite as well.
I'd say most of my time is spent thinking while programming anyway, but when I am typing, nothing has made me faster than vim. "Small" things like "hmm, I don't like what's in this block" can be as slow as reaching over to the mouse and selecting a bunch of code by hand, trying very hard to be precise, or typing "ci{". Which is easier?
Perhaps I've been missing out on all these years on the true power of IDEs and not using them to their full potential, but when it comes to programming, I like to be the one typing, not some fool machine. Do I occasionally make mistakes? Of course. Is my overall output better because I have fewer distractions? Absolutely.
Of course, that's just me. I know plenty of people who are a lot faster with autocomplete and auto-quote closing and everything else.
For anyone who spends their day (or most of some days) in a terminal connected to a remote server, I can't recommend using GNU Screen enough (brief tutorial: http://www.kuro5hin.org/story/2004/3/9/16838/14935 ). I've worked almost exclusively on remote servers, using the command line and vim, for about eight years now. It's only been in the past year that I started using Screen, and I feel stupid for not using it soo…
In other words, it seems like I've been working in 'the cloud' for the past 16 years and it can appear to me that everyone else is slowly catching up to this nifty idea.
The reality is that trends swing between thin and thick clients, centralization and decentralization. They are competing forces.
Imagine an "iPad Pro" that had similar battery life and even an integrated keyboard. In addition to supporting the SSH workflow, it can run traditional GUI applications if you really need them. You don't have to wait: it's called the MacBook Air.
Earlier quoted context omitted.
Screen is great. Though not it's fault, the only downside is that it cant persist through a machine restart.
This is true, but: 11:12:52 up 44 days, 54 min, 63 users The machines I connect to are restarted rarely. I expect this particular machine to be up until Christmass time, at which point there will probably be some scheduled maintenance.
Screen/tmux/dtach are so trivial to implement and use and make the connection much more bulletproof that if you foresee there ever being a possibility that you might disconnect and lose work, then you should probably be using one of them.
I don't see the difference compared to owning a MacBook Air. Is it that the screen and keyboard are separated?
For anyone who spends their day (or most of some days) in a terminal connected to a remote server, I can't recommend using GNU Screen enough (brief tutorial: http://www.kuro5hin.org/story/2004/3/9/16838/14935 ). I've worked almost exclusively on remote servers, using the command line and vim, for about eight years now. It's only been in the past year that I started using Screen, and I feel stupid for not using it soo…
One fateful day, VMWare and OS/X conspired to trash my shared filesystem, losing several days of uncommitted code in the process. Several days of uncommitted code? We need to have a heart to heart talk about your process.
Insightful, and so close to a haiku as well... Here's an attempt: Mac lost my data Many days of work gone Cloud to the rescue
There once was some data I lost:
Days worth of work just got tossed!
So I decided to write code
On an iPad plus Linode
Getting backups for minimal cost.