41–50 of 354 posts
I heartily agree -- once you add a wireless keyboard to an iPad, it stops being a toy. I use the keyboard and an iPad 1 to write my first drafts (both locally and google docs, if need be) and with VNC, I code on my remote servers as well.
How do you keep the iPad's screen comfortably facing you if you're not holding it?
Can you really write code efficiently on such a small (9.7") screen?
When I switched to a new smartphone, the resolution was the most important change - with 854x480 pixels I can read forums and sites easily, as opposed to a 320x480 display...
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.
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…
When you do this, much less important data is stored locally, on developer's actual machines.
You can pry my dual 24" monitors + high performance desktop from cold dead body.
You could actually do the same thing WITH a Macbook Air/Pro. The beauty of a cloud linux instance + gnu screen isnt limited to the ipad and so you could still have a bigger screen and the possibility to go back to GUI apps if you need them. I like this for travelling on the go, but spending my normal workday in 1024 resolution ? Naaa.
This is true, but I'd be sacrificing the silence, the portability and the battery life. And the hipster factor, I guess. 102x768 isn't for everyone, but in text-mode it's all the same. I've no idea how many hours I've spent on a huge high-res monitor staring at a relatively tiny terminal window surrounded by a pretty desktop picture.
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…
I respectfully disagree, or partially, anyway. I've been developing software in Vim, Netbeans, and Visual Studio (with about a year or so of Eclipse thrown in for good measure). I've worked on projects in all three ranging from tiny 1kloc one-offs to several million line systems, using C, C++, Java, Bash, and a smattering of Perl and Python. For Java and C++ code bases beyond a few thousand lines, I certainly agree t…
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…
If this guys thinks having a single 10" screen with no ability to switch between tasks easily and quickly is the wave of the future for developers, I don't want any part of that future. You can pry my dual 24" monitors + high performance desktop from cold dead body.
I plug the iPad into large monitors sometimes. When an iPad with double the resolution comes out, this won't seem nearly so silly.
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.