News for hackers. Stuff that matters.
Re:If you love automation, why is your development environme... by qwerta on Wednesday May 08, 2013 @09:18AM (#5673940)
>If you love automation why is your development environment manual?

Because I usually do it once in 5 years :-)

My setup: Linux, Kubuntu LTS. Entire system is backed-up with rsync, so I have daily snapshots for last 6 months. There is also weekly backup to cloud and external hdd.

I have primary 250GB SSD which usually sits in my workstation. Whan I travel I physically move SSD to laptop (takes 10 minutes).

If something went wrong and my primary SSD would die: I just boot from Livecd, copy 200GB, setup bootloader and reboot. No need to 'reinstall' system from scratch.

Every six months I take one afternoon and update all my tools (IDE, OS, apps...). I dont use automated updates except critical stuff such as browser.

Re:If you love automation, why is your development environme... by gtaylor on Wednesday May 08, 2013 @10:50AM (#5674418)
It's a lot different when you're working with certain teams of mixed technical aptitudes. An automatically assembled VM image I can distribute means much less time supporting our less technical members of the dev team (front-end, designers, biz dev guys).

If it's just you, absolutely, don't bother. But it gets much more difficult to support a variety of platforms and configurations as your team size grows. This is where vagrant+chef/puppet really shine.

Re:If you love automation, why is your development environme... by qwerta on Wednesday May 08, 2013 @11:06AM (#5674567)
> An automatically assembled VM image I can distribute means much less time supporting our less technical members of the dev team

Absolutely. At my previous work we had 'standard' VM with all necessary tools such as Visual Studio 97. I just dont understand if it brings so much benefits if all you just need is different version of Ruby.

Re:If you love automation, why is your development environme... by to3m on Wednesday May 08, 2013 @09:58AM (#5674134)
I've found this too, as an individual. When running Windows I used to have to reinstall everything about once every 2 years. Took about half a day each time. I've reinstalled everything once in 4 years on Mac OS, from Time Machine, so I just left it running overnight. I don't know how long it actually took but I got up the next day to find my computer just as it was. Reinstalling things is annoying, but just doesn't take up enough of my time to be a problem worth fixing.

Then again, maybe if I had the ability to quickly set up a new development-ready VM, I'd come to find all sorts of unexpected uses for it? I've certainly found duplicating Parallels VMs handy a couple of times. But I have to say that I'm still skeptical that the time spent learning Chef and trying everything out would be worth it for me.

If I were looking after 5 (10, 20...) programmers then my back of the envelope calculations would look a little different.

Re:If you love automation, why is your development environme... by dasil003 on Wednesday May 08, 2013 @01:22PM (#5675511)
I hear what you're saying, but I don't think the time spent learning Chef (or Puppet) is ever wasted. It's sort of like mastering a unix shell or getting good at automated testing: initially there is this steep learning curve where you are definitely less productive, but over time it pays huge dividends.

Have you ever had to install multiple versions of some package on the same machine? Have you ever had to help a colleague debug a weird issue that was particular to their setup? Have you ever had to work on the same project from multiple platforms and some component didn't work on one of them? Have you ever had a bug only appear in production because of a platform subtlety?

Re:If you love automation, why is your development environme... by hosh on Wednesday May 08, 2013 @05:35PM (#5677110)
I don't think the time spent learning Chef (or Puppet) is ever wasted.

Exactly!

It might not look like it right now, but skills in using these tools are moving from cutting edge to essential job/contracting skills in the near future.

I don't know much about the Puppet community, but I do know that within the Chef community, the learning curve is flattening. The big thing of 2012 was that we're very close to getting these VM+Chef+Berkshelf setup in a way where you can get onboarded on an existing open-source application without knowing you are using Chef under the cover. How deep you want to dive in is up to you from that point.

Re:If you love automation, why is your development environme... by peterwwillis on Wednesday May 08, 2013 @09:46AM (#5674069)
Ditto. Backing up your dev environment is less time-consuming and more reliable than scripting it.
Re:If you love automation, why is your development environme... by StavrosK on Wednesday May 08, 2013 @10:07AM (#5674169)
I don't know, I script production provisioning anyway. Dev provisioning is free, I just change the hostname to the VM.
Re:If you love automation, why is your development environme... by 23david on Wednesday May 08, 2013 @03:35PM (#5676347)
Have you ever tested restoring from your daily snapshots? :-) Seems like a good setup, but to be rigorous about it you should probably also schedule a full restore from backup every once in a while to ensure that your backups are actually working correctly.
Re:If you love automation, why is your development environme... by qwerta on Wednesday May 15, 2013 @07:24AM (#5711234)
Re:If you love automation, why is your development environme... by fideloper on Wednesday May 08, 2013 @09:48AM (#5674080)
I think an important point in this post was more about not trying to setup a dev environment in your base Mac install (or similar). Use Virtual Machines.
Re:If you love automation, why is your development environme... by qwerta on Wednesday May 08, 2013 @09:54AM (#5674108)
In that case I just find it better to wipe MacOS and replace it with Linux.
Re:If you love automation, why is your development environme... by gtaylor on Wednesday May 08, 2013 @10:47AM (#5674395)
It's not always a good solution for your entire team. I run Linux on my desktop, but have found that the touchpad drivers (even the experimental ones) just really suck on Linux+Macbook Pro to the point where it's either external mouse (not always possible) or decreased productivity.

I have a feeling this is going to devolve into a "well, just use vim and a tiling WM or X other thing", but the point is that just replacing Mac OS with Linux isn't always going to be good for your whole team.

Re:If you love automation, why is your development environme... by beatgammit on Wednesday May 08, 2013 @11:55AM (#5674929)
When you're targeting Linux, it's easier in the long-run to just use Linux. The base system isn't the same between the two because Mac OS X uses BSD versions of important things like SED, grep, etc. There are subtle differences that most Mac OS X users I've met don't know and can lead to weird problems like "why doesn't X work; it works fine on my mac!!".

If everyone's on Linux, the dev and productions systems are more similar, so less scripting issues can arise. I personally use Arch, other coworkers use Mint or Ubuntu, and only one developer uses Mac OS X (others switched because of above problems; he couldn't switch because of EFI problems). Even devs new to Linux (from Windows) love Mint, and all is well and good in the world. Servers run Debian or Ubuntu, so I test my changes in a VM because Arch has noticeably newer software in the repos, but that's because I can't stand Debian as a desktop system (package manager too slow).

Also, the Mac OS X user uses his Mac like a Linux box. He only ever touches his trackpad to use non-keyboard friendly apps (uses Vimium for Chromium, tmux/vim for terminal/editing, etc). Our devs not familiar with the keyboard generally use Sublime on Linux, which is a fantastic editor as GUI editors go.

The trackpad drivers aren't that bad, but may require some configuration in the xorg conf (I got multitouch working, but disabled it because I find it annoying).

We don't standardize on a single dev platform because each developer is different. The developer understands that using Linux is going to be easier in the long-run, but he/she must understand that his/her choice of OS must not negatively impact productivity. We've had a few developers try starting on Windows, but we'd refuse to support any dev environment besides Ubuntu Linux, and when they ran into problems, they switched to Mint/Ubuntu.

I've never seen a developer be more productive on Mac OS X than Linux. In fact, those gesture usually end up slowing him/her down from what should be easy using the keyboard (and all that switching from trackpad to keyboard is not productive).

Re:If you love automation, why is your development environme... by hosh on Wednesday May 08, 2013 @01:25PM (#5675541)
There are advantages to using VMs even if you've installed Linux as the base OS on Mac hardware.

The VMs provide isolation for testing and developing the server components. (I'm assuming you are developing server code). Through synced folders, you can still use your favorite $EDITOR on the host machine -- vim, emacs, sublime text, whatever. Onboarding is faster, and you can manage multiple node setups.

Further, you have the additional advantage of being able to replicate staging or production systems on your local box. This reduces time spent round-tripping to a staging server.

This lets you standardize the server code without requiring all developers to standardize on editors/ide/etc.

Personally, I am more productive on OSX than on Linux. But that's because my actual dev environment is tmux+vim. I let OSX and Mac hardware handle the stuff that it does much better than Linux: being able to talk to anyone, anywhere, with anything. (Networking) Being able to reliably suspend and wake.

Re:If you love automation, why is your development environme... by gtaylor on Thursday May 09, 2013 @12:27PM (#5681284)
> I've never seen a developer be more productive on Mac OS X than Linux.

Completely anecdotal and not at all useful in the context of this discussion. I've seen some of the top minds in the Python community using Mac OS with extraordinary productivity, as well as some of my fellow developers at Pathwright. I myself run Linux, but think it's foolish to suggest that I'm automatically more productive on it just by virtue of it being Linux.

I feel like you're missing part of the point, though. Even between different Linux distros (or versions of Linux distros) there exist differences in the packages. Some of these differences can lead to unexpected breakages. If you've got a smaller team, one or two guys are going to end up fixing everyone's disparate environments as things break unexpectedly (or you need to bump a package version or install something new).

The Vagrant (or VM) setup in general lets everyone use their preferred OS/Distro, while having the same. exact. environment to run the product you're working on. It also cuts down on support time, and your dev environment will not be just "kind of close" across your team, i'll be "really close".

Re:If you love automation, why is your development environme... by kaolinite on Wednesday May 08, 2013 @12:06PM (#5674988)
As someone who uses both OSX and Linux, I am more productive on Mac. Seriously though, get over your grudges - use what makes you happiest.
Re:If you love automation, why is your development environme... by w1ntermute on Wednesday May 08, 2013 @11:00AM (#5674519)
If productivity is key, get a ThinkPad, install Linux on it (they're very Linux-friendly), and learn to use the TrackPoint exclusively. Watching people use MacBooks, even with all those fancy multitouch gestures, is like watching a slow-motion movie. And they are always amazed how quickly I can do stuff on my ThinkPad.
Re:If you love automation, why is your development environme... by platz on Wednesday May 08, 2013 @11:18AM (#5674666)
TrackPoint is amazing; I hesitate to switch from ThinkPad's because of it.
Re:If you love automation, why is your development environme... by zmjones on Wednesday May 08, 2013 @11:45AM (#5674870)
How is the battery life?
Re:If you love automation, why is your development environme... by beatgammit on Wednesday May 08, 2013 @11:57AM (#5674943)
Why do you need battery life for development? Most of the time you'd probably be in the office anyway.

Even so, ThinkPads have pretty good battery life, and on some models the CD drive can be replace with an extra battery. I've heard of some that can go nearly two working days before recharging.

Re:If you love automation, why is your development environme... by zmjones on Wednesday May 08, 2013 @01:03PM (#5675380)
I don't work at the office most of the time. I know thinkpads have good battery life generally, but I know there have been some battery life issues with linux in the past.
Re:If you love automation, why is your development environme... by lsiebert on Wednesday May 08, 2013 @12:54PM (#5675305)
Thinkpads have great battery life built in, or you can get extended batteries, or slice batteries. You can even stick a battery in the drive bay.

You can also easily turn off ports you aren't using, at least in linux.

Re:If you love automation, why is your development environme... by sensae on Wednesday May 08, 2013 @01:51PM (#5675702)
I run ArchLinux on a ThinkPad X120e. I get 3-4 hours of battery life out of a 57Wh battery.
Re:If you love automation, why is your development environme... by Retric on Wednesday May 08, 2013 @09:56AM (#5674114)
The problem with VM's is each developer often customizes the, quite a bit. It does make adding someone new faster but unless you have rapid turnover I don't think it's worth the overhead.
Re:If you love automation, why is your development environme... by hosh on Wednesday May 08, 2013 @05:27PM (#5677070)
That's why you manage the VMs with a configuration convergence tool such as Chef or Puppet. At that point, the VM doesn't matter. I tend to treat mine's as throw-aways, and have Chef rebuild the specific VM for the specific project. This lets me experiment with things and then reset it back to a known, good state.