101–110 of 354 posts
Earlier quoted context omitted.
I would observe that with DVCS, if your hard drive crashes you can still lose several days of un pushed code, too. I recommend and use cron jobs to push and/or rysnc things around on a more frequent basis for my really important stuff.
What's wrong with a remote branch you push to and then merge back into master afterwards?
I don't see how releasing a full Android version would be anti-competitive in any meaningful sense.
Especially since the Android app and webapp support for Google Docs is unbelievably horrible. It amazes me that something as simple as editing a document (or simple spreadsheet) is almost completely impractical on Android tablets.
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
It's the poor craftsman
Who points the blame at his tools
Y U NO COMMIT?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…
Screen is great. Though not it's fault, the only downside is that it cant persist through a machine restart.
I've got a little bash script for my VM that launches tmux, and starts a development web server in one of the windows, and tailing logs in another, and then dumps me into my project directory.
I also found tmux much, MUCH easier to script than screen.
Anyone tried to do this as a web developer? I know theres an app or two geared towards being a web dev environment, the one good one i found (its called Gusto on the app store) i didnt get to test properly because it didnt support SFTP yet (due to apple requiring some permission from the gov or something, not technical limitation).
Still.. even plain HTML is a lot more visual than code. so much switching can suck.
.. now, two or three iPads, that's the ticket.
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…
Having used git for four years, I now feel absolutely filthy if I'm not coding on a branch. If I start coding anything, I make a branch first, because the overhead is nearly zero, if I screw something up I can easily revert, and the downside of being scared to push code is too great.
Example: Yesterday I started a new feature. Step 1 was to branch from our develop branch. A bit into the coding I realized that this feature was going to take longer than expected. I committed what I had on my branch and pushed it to the remote repository (github in this case). This affects no one else, because the code is on a branch.
What really makes this possible is that merging is so easy. Branching and merging in svn was scary. I was never sure if something horrible was about to happen. With git (and hg) branching and merging is the expected behavior, and it's easy.
Always being on a branch also makes it easier to deal with interruptions. "Hey, there's an emergency, can you fix Foo?" No problem, commit what you have on your branch (or use `git stash` which is amazing) and jump back to the branch that has the code you need to fix. Need that fix in your branch as well? You can merge or simply `git cherry-pick` a single commit across branches. You no longer have to worry about the dreaded "Did I already merge this? What if I merge it again, what will happen?"
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
Earlier quoted context omitted.
This is really true. Back then we were still using CVS, and I was writing a feature that I thought wasn't quite big enough to branch and remerge for, but turned out to be a bit more involved to get right than I'd thought. Now we're on Mercurial and life is better. Edit: A nice win with the Linode is that they back it up for me for $5 a month. Sure, there are solutions for the desktop too, but somehow I never got arou…
I would observe that with DVCS, if your hard drive crashes you can still lose several days of un pushed code, too. I recommend and use cron jobs to push and/or rysnc things around on a more frequent basis for my really important stuff.
Earlier quoted context omitted.
Since we're pimping terminal multiplexers, I quite enjoy tmux ( http://tmux.sourceforge.net/ ). I used to use screen, but found tmux to be faster, smoother, and have more logical key-combos (your mileage may vary).
I saw two people below who say they prefer tmux over Screen, so I just looked it up. What I care about most is persistence; I use multiple terminal sessions if I want to have multiple windows. Did you find any difference for that feature?
This is partly a testament to what a great app iSSH is. I haven't used it as a daily work environment, but I've gotten some pretty great things done with it, even the iPhone version. My favorite was sitting in a crappy motel room with barely Edge, and still managing to build a GPX converter (not build as in write, build as in download and compile), convert some map routes to a format I needed for another phone app, a…
This is really true, although depending entirely on a low-price, commercial app makes me uneasy. I'd be happier if I knew iSSH made enough to support a small company. I'd be happiest with an open source version I could contribute to.