News for hackers. Stuff that matters.
Re:Why doesn't every company buy developers the best hardware? by vacri on Tuesday July 19, 2011 @09:19AM (#2780718)
What constitutes 'best hardware'?

I have a friend in high finance whose desktop is a (dual?) quad core with 12GB ram which he regularly maxes out. I have a colleague that writes firmware on windows XP, which with his various drivers and Eclipse problems causes a BSOD about once a fortnight. I keep offering him to get a new computer, cards, whatever, and he refuses because of the cost to him in terms of getting his environment set up 'just right' again - he's quite picky (at my previous workplace, a digital circuit designer on six figures didn't want to move from his PIII to a Core 2 for the same reason).

Another colleague runs a quad core on an SSD and complains that his CAD program runs slow... but when we run it through its paces, it doesn't seem to hit any bottlenecks bar the initial load (which isn't his complaint); it just 'feels' slow.

as with all things computery, the answer is: "it depends"

Re:Why doesn't every company buy developers the best hardware? by djipko on Tuesday July 19, 2011 @11:18AM (#2781272)
>I have a colleague that writes firmware on windows XP, which with his various drivers and Eclipse problems causes a BSOD about once a fortnight. I keep offering him to get a new computer, cards, whatever, and he refuses because of the cost to him in terms of getting his environment set up 'just right' again - he's quite picky (at my previous workplace, a digital circuit designer on six figures didn't want to move from his PIII to a Core 2 for the same reason).

I've seen this before (and was guilty of this kind of thinking a few times) and I believe this is simply misguded. No matter how good of an "old-school" developer someone is, she needs to keep her tools fresh. To me this is no different than having a very manual build or deployment process (maybe not as bad but still).

I believe when it comes to HW + toolset for development, you simply must consider:

-Computers break - you need to be able to set up a new one in a matter of hours (or 10s of minutes). Maybe it does not need to be this drastic everywhere, but if your computer breaks and it takes you a few working days to get it just right - something is wrong - you need to automate it or reconsider the tools (which may not be always possible especially in embedded/hardware design world). If you get this right - upgrading will not be (such) a problem.

-You need to keep up with the tools - maybe more than you need to keep up with the libraries. With this I don't mean only the newest versions, but to constantly be on the lookout for the better alternatives - blogs, forums etc. there is simply no excuse for not doing this if you are a developer other than laziness. This will help you get rid of some stuff on your machine you don't actually need because you may end up with better alternatives. I am a firm believer in getting rid of clutter in your life.

Not all devs in all companies can follow these, of course, due to policies, the nature of work, "legacy stuff" and whatnot, but it helps a lot if you can, and point 2 means you are learning - so you are not bored.

Re:Why doesn't every company buy developers the best hardware? by miahi on Tuesday July 19, 2011 @01:59PM (#2782183)
I still use Win 2k3 on my work laptop. I'm using this OS since RC2, and I'm way more productive on that old OS than on W7. I tried customizing a W7 install to look and feel just like that and I failed to get the same feeling. I use W7 at home, it's very nice for entertainment, but I just can't get into 'the mood' with it.

For the other applications, I went for the 'portable' version of everything I need. This way I can move from one machine to another without spending days setting up everything - I just copy the 'tools' directory and I'm ready.

Re:Why doesn't every company buy developers the best hardware? by simplezeal on Tuesday July 19, 2011 @05:12PM (#2783093)
You should ask him to look into disk2vhd tool. Allows you to make VHD off a current set up which he can run on new machine as VM until he is comfortable with setting new machine per his requirements.