News for hackers. Stuff that matters.
Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @08:15AM (#2780516)
I have mixed feelings that the best hardware yields better productivity.

I worked with a Macbook Pro, top of the line, with 2 x 24 inch monitors attached, with an ergonomic keyboard and wireless mouse and all that crap.

Now I work with a $500 ASUS that doesn't even lit my keyboard, with Ubuntu Linux installed and I'm using it directly (no external monitors or keyboard) since I'm on the move a lot.

As far as my productivity is concerned, I still get things done at the same pace. Hardware is not my bottleneck.

Of course, this has more to do with my other preferences. I like keeping my toolchain as light as possible. I don't use bloated IDEs, even when working with languages that require an IDE, such as Java. I don't do heavy processing often and when I do, I prefer offloading that work on AWS. I am also proficient with manipulating virtual desktops.

As far as startups go, I think that spending money on expensive hardware is not frugal spending. If you're my boss, I would rather prefer a bonus than the latest and shiniest crap -- if I want shiny crap, I can buy it myself while respecting my own priorities.

Re:Why doesn't every company buy developers the best hardware? by icebraining on Tuesday July 19, 2011 @08:29AM (#2780553)
My meager single-core 1.6GHz laptop has been fine for development, until the time I had to use Eclipse instead of Vim. Why, oh why, does it freeze while I'm just writing code!
Re:Why doesn't every company buy developers the best hardware? by Kliment on Tuesday July 19, 2011 @09:32AM (#2780786)
Eclipse shows you build errors by compiling your code in the background as you type. I believe you can disable this, or make it happen less frequently. This is the cost of red wavy underlines for compile errors. I don't remember the exact setting, as I haven't used Eclipse in years, but it's in there.
Re:Why doesn't every company buy developers the best hardware? by icebraining on Tuesday July 19, 2011 @09:43AM (#2780845)
But the Right Thing™ would be for Eclipse to lower the priority for such checks, so that they wouldn't conflict with the interface. I often have processes using all my available CPU time, but since they run at a 'niceness' value of 19, they don't affect the interactive tasks.
Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @09:59AM (#2780905)
It's easier said than done -- whatever Eclipse is doing in the background, it also has to update the interface to reflect the latest results, which means synchronization with the UI thread.

Also, a big project is hard to optimize, especially when threads are involved; so whatever shortcuts you take to make it work at first does come back to hunt you in a big way and you can't fix it easily.

For example people are telling me that Eclipse should run fine, but on my laptop it freezes a lot, even for small projects; while IntelliJ IDEA works flawlessly. So I'm not sure what the problem is, but it does something on my box that it shouldn't -- and throwing more money on hardware (instead of searching for a better alternative) just seems like the wrong approach to me.

Re:Why doesn't every company buy developers the best hardware? by burgerbrain on Tuesday July 19, 2011 @11:34AM (#2781335)
I am under the impression that async UI updating is a rather solved problem. I'd wager Eclipse has even done it since.. probably forever. No, I suspect the real issue is that it doesn't 'renice' it's compilation processes correctly or sufficiently.
Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @12:28PM (#2781620)
Not necessarily -- if you're pushing thousands of update events in a short time, those events will also trigger a waterfall of other events triggered by UI components and so the effect gets multiplied; the end result being that it doesn't matter if the operations themselves are async as the UI will get sluggish.

Another problem is that some operations are blocking in nature. Consider the case when an intellisense dialog is triggered (after typing a dot or pressing Ctrl-Space) -- to give you intellisense, Eclipse has to compile your code, make guesses about your intent in case the code has errors (since intellisense also has to function in case of simple errors, otherwise it is useless) and then present you with a dialog with options available for completion. This is not something that can be done async.

Of course, this opinion was just some random guess. I have no idea why Eclipse has the tendency to freeze the UI on my machine.

Re:Why doesn't every company buy developers the best hardware? by kgthegreat on Tuesday July 19, 2011 @01:02PM (#2781819)
Disable Build Auto in under Projects
Re:Why doesn't every company buy developers the best hardware? by gmartres on Tuesday July 19, 2011 @07:08PM (#2783523)
Why do you need Eclipse?
Re:Why doesn't every company buy developers the best hardware? by icebraining on Tuesday July 19, 2011 @08:59PM (#2783827)
The project (an internal tool) had a dependency on an Eclipse plugin and platform.
Re:Why doesn't every company buy developers the best hardware? by cks on Tuesday July 19, 2011 @09:16AM (#2780704)
For me, long compilation times puts me out of "the zone". If compilation takes too long I'll start reading e-mails or web browsing. When compilation is done my mind is elsewhere and I have to get into the problem solving "zone" again.
Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @09:42AM (#2780837)
This is very true; that's why I hate the Scala compiler and when working with Java I take special care to have a lean and mean compilation strategy.

For example with Java I use manually written Rakefiles (I prefer it over Ant since I have more control), I make sure it doesn't compile unless files have actually changed and in case the project is getting big I start separating functionality in multiple projects, having multiple JARs as a result.

Then, I'm using Emacs and in Emacs I can start a build whenever I'm hitting "Save" on a file. And in case of compilation errors, Emacs even highlights the errors for me.

You have to work on it a little and you lose time on the actual build process, but you can achieve a lean and mean setup (unless the compiler really sucks).

Of course, this is the advantage of an IDE - it takes care of annoying details for you; but then you have to put up with all the bloat that brings. And for humongous projects, your IDE will choke anyway, even if you have the latest state-of-the-art hardware; try loading the Firefox codebase in Eclipse CDT or in Visual Studio sometimes.

Re:Why doesn't every company buy developers the best hardware? by Terretta on Tuesday July 19, 2011 @11:30AM (#2781316)
In the 'old days', compile time was a chance to print out your code on fanfold paper and do a top down thoughtful code review, refreshing the map of the whole project in your mind.

It's quite rare these days for developers to literally see their whole program's code at once, and I think we're the worse for it.

Re:Why doesn't every company buy developers the best hardware? by dpark on Tuesday July 19, 2011 @12:18PM (#2781563)
In the 'old days', you must have been writing small programs. Printing a 1K-line program on paper might give you a nice perspective on your code. Printing a 10K-line program on paper is a waste of paper. Printing a 100K-line program on paper is ridiculous. Beyond that it just gets worse.
Re:Why doesn't every company buy developers the best hardware? by Terretta on Tuesday July 19, 2011 @12:54PM (#2781771)
> In the 'old days', you must have been writing small programs.

On the contrary, 10,000 lines is still only 150 pages at 66 lines per page, and fanfold paper flips through easily.

I've read through several projects that took at least three reams of fanfold paper. I'm not saying that was fun. Fortunately one didn't generally have to read through the whole project, only the module one was working on.

Re:Why doesn't every company buy developers the best hardware? by dpark on Tuesday July 19, 2011 @01:24PM (#2781966)
I don't think it's useful to attempt to hold 150 pages of code in my head. Even with a long compile time, it's not possible to do more than just barely skim that much code.

I have printed code and reviewed it before. Sometimes it's useful for small programs or classes. I don't think it's useful to waste 150 (or more) pages to print an entire large program, though.

Re:Why doesn't every company buy developers the best hardware? by Terretta on Tuesday July 19, 2011 @02:27PM (#2782360)
> I don't think it's useful to attempt to hold 150 pages of code in my head

Not sure it was about holding the actual code in one's head so much as the structure, flow, or shall we say, "plot".

The Chronicles of Thomas Covenant runs 4948 pages, Song of Ice and Fire is 4195 pages so far, and even LotR is 2144 pages.

This is one of the reasons I think there's a high correlation between great developers and developers who love history -- leveraging the ability to envision and hold a complex sequence of interlocking details in mind.

Re:Why doesn't every company buy developers the best hardware? by dpark on Tuesday July 19, 2011 @03:04PM (#2782546)
I feel like you're really reaching for a comparison here. You're not reading LotR in the 10 minutes it takes your code to compile. You're not even skimming it. The fact that your code is shorter than LotR isn't really meaningful. You also aren't reading 150 pages of code while your code compiles, and if all you want is to review the high-level flow, skimming the code is going to miss a lot.

I just can't see the value in printing 150 pages of code to barely skim it. Especially since those 150 pages will be increasingly out of date as time goes on. It's just such a waste of paper.

I'm not sure where you get your "great developers" and "developers who love history" link, either. Liking history has nothing to do with coding. Nor does it have anything to do with reading fantasy novels. And none of the history buffs I know are even coders. This is such a random tangent.

Re:Why doesn't every company buy developers the best hardware? by Terretta on Tuesday July 19, 2011 @03:56PM (#2782773)
> "I'm not sure where you get your "great developers" and "developers who love history" link, either."

I provided credentials above. I've been managing hundreds of developers over the past decade and working as an independent developer for a decade before that. (And as a hobbyist developer the decade before that.)

> "Liking history has nothing to do with coding."

My experience hiring and managing hundreds of devs indicates the exact opposite. You may have found differently, but I will continue to focus on hiring people who find learning a rich tapestry of interconnected context fascinating, and preferring to hire those with history (or linguistics or other complex humanities) degrees with formal CS electives over those with pure CS degrees.

Re:Why doesn't every company buy developers the best hardware? by dpark on Tuesday July 19, 2011 @04:57PM (#2783041)
Sorry, I should have been more clear: Your personal anecdotes are not sufficient to establish any meaningful connection between these two. Moreover, this is entirely tangential and has nothing to do with what we were discussing.
Re:Why doesn't every company buy developers the best hardware? by Terretta on Tuesday July 19, 2011 @07:49PM (#2783622)
> "Your personal anecdotes are not sufficient to establish any meaningful connection between these two."

“Now, I don't want to get off on a rant here ...”

By your definition, most science is "personal anecdotes" if building knowledge through systematic observation and study of hundreds of test cases is merely "personal anecdotes". (See "empirical research"[1].)

By contrast, you wrote "Liking history has nothing to do with coding" but you supplied nothing whatsoever to substantiate that statement, just as you supplied no basis for the statement that working closely with hundreds of developers is not sufficient to establish a connection. Ok, I've managed hundreds, and we've collaborated with thousands. How many developers would be enough to establish any meaningful connection?

You challenged "I'm not sure where you get your link" and I provided the basis for that link: observation of several hundred developers I have hired and employed. That's a reasonable number considering many studies use pools of just a couple dozen test subjects.

Throughout this thread, you have countered remarks I've based on experience, with your own unsubstantiated assertions, sometimes insulting in nature. For example, you wrote "In the 'old days', you must have been writing small programs" when the opposite was true.

Just because you "can't see the value" in a printed code review back in the 80's, or haven't noticed a link between coders with an appreciation for history and an exceptional ability to architect software systems, that doesn't obviate the need to provide at least as much foundation for your arguments as I've provided, particularly if you're trying to call me out for lack of basis.

You said this is "entirely tangential and has nothing to do with what we're discussing", yet this concept of holding the complex in mind is precisely what I opened with, and the theme I've stayed with.

In my experience – which I've scoped so readers can decide for themselves if it's relevant – reading well, taking time to contemplate and be thoughtful, remembering and understanding complexly woven tapestries of information (whether multi-volume literature or world history or computer code), and being able to read long code (or threads) and form a structure of it in one's mind, are all skills signaling good developers.

In my experience, a love of reading, stories, and history in particular, signals a desire for learning, a sense of proportion and place, and a respect for 'the shoulders of giants' likely to help a good developer become great.

“... of course, that's just my opinion. I could be wrong.”

1. http://en.wikipedia.org/wiki/Empirical_research

Re:Why doesn't every company buy developers the best hardware? by dpark on Tuesday July 19, 2011 @08:40PM (#2783762)
I have serious doubts about the quality of your "systematic observation and study of hundreds of test cases". I don't believe at all that you've been systematically tracking which of your programmers are history buffs and how it correlates to performance. I think you're a history buff and so you assume that it must correlate meaningfully, just as programmers who are into music, or art, or whatever else do.

No number of developers is enough to turn offhand observation into meaningful correlation. That would require measuring and tracking. It would require more than your gut feeling and confirmation bias. I frankly find it worrisome that you actively choose history majors over CS majors for development work. That says nothing to me except that you have a personal bias.

I stand by my statement that you must be writing small programs if you're willing to print them in entirety on paper. You can find that insulting if you want (it wasn't intended to be), but it's a fact. 10K lines is not a large program in modern terms (though I say it's too large to waste the paper on). It's definitely not large when your team involves multiple developers.

As for code reviews in the 80s, the value is in the review. Whether it's printed on paper or not isn't really very meaningful. It can be nice to have a paper copy sometimes, but it's just that, nice. It's not really a substantive change.

And yes, this history argument is extremely tangential. You did not start with that. You started by saying that you used to spend compile times reviewing the printed code. That has nothing to do with being a history buff. Someone could love doing paper code reviews and hate reading about history. And any link that might exist was certainly not established before you transitioned into talking about history buffs being good architects.

Re:Why doesn't every company buy developers the best hardware? by Terretta on Tuesday July 19, 2011 @09:24PM (#2783884)
> I have serious doubts about the quality of your "systematic observation and study of hundreds of test cases".

You still haven't provided your basis for positions, and you're still littering your responses with assumptions or accusations.

> I don't believe at all that you've been systematically tracking which of your programmers are history buffs and how it correlates to performance.

You are mistaken. When, out of hundreds of hires, a handful match the criteria, it's easy to look back at data collected at hiring time, and find out if there are correlations (not causations).

> I think you're a history buff and so you assume that it must correlate meaningfully, just as programmers who are into music, or art, or whatever else do.

Wrong. History isn't a primary interest. I enjoy a variety of things more. I believe most are unrelated to ability to architect software.

> No number of developers is enough to turn offhand observation into meaningful correlation. That would require measuring and tracking. It would require more than your gut feeling and confirmation bias.

See above. Your assumption was mistaken.

> I frankly find it worrisome that you actively choose history majors over CS majors for development work. That says nothing to me except that you have a personal bias.

Prefering to hire a History major with a minor in CS over a pure CS major typically results in better rounded individuals more capable of software architecture, dealing with clients, and collaborating with peers. Unfortunately, out of hundreds of hires, again, only a handful have fit that bill. But none of those who did fit that bill, had to be let go.

This was data collected at interview time, and in fact, on the first such individuals, I was as skeptical as you. Looking back at the collected hiring data about outperformers revealed this correlation. Since then, I've confirmed this curious correlation with several peers.

> I stand by my statement that you must be writing small programs if you're willing to print them in entirety on paper.

Again, your assume that I was printing the large programs. I was not. I was invovled with software developed and used by scientific research organizations, hospitals, and universities. They would hand me a box of fan-fold paper (once even on a hand truck), and say, "Here's the code." I found learning the overall picture faster reading through the stack than scrolling the code on a CRT, particularly thanks to the ability to use a highlighter and Post-Its.

Today, when confronted with a similar task, I prefer an iPad and a good reader with markup tools.

> As for code reviews in the 80s, the value is in the review. Whether it's printed on paper or not isn't really very meaningful. It can be nice to have a paper copy sometimes, but it's just that, nice. It's not really a substantive change.

Given today's technology, mostly agreed. However, research suggests tangible artifacts cement concepts more firmly in our organic brains than digital exposure alone.

> And yes, this history argument is extremely tangential. You did not start with that. You started by saying that you used to spend compile times reviewing the printed code. That has nothing to do with being a history buff. Someone could love doing paper code reviews and hate reading about history. And any link that might exist was certainly not established before you transitioned into talking about history buffs being good architects.

You're right, I didn't bring up history first, I brought up the concept of understanding "a map of the whole". To me, that equates closely with a long multifaceted narrative. You brought up the inability to hold a few pages of code in one's head, and I countered with literature and history. Both code and history are something like the Bayeux Tapestry, where the local is most useful when understood in context of the whole. Come to think of it, the word for our oldest long historical texts, and for what you do reviewing code on a the screen, are the same: scroll.

My ravioli's done baking. Enjoyed the discussion. Cheers.

Re:Why doesn't every company buy developers the best hardware? by dpark on Wednesday July 20, 2011 @12:09AM (#2784262)
To be fair, you haven't provided any legitimate basis for your claims about the link between history buffs and software architects. I'm just saying that your claims are unfounded, and so I'm not making any claims that demand support. Your claim that interest in history is correlated closely with ability to architect software is not obvious prima facie, so it demands support to be believable.

I also don't think your handful is a very large sample size, regardless of what correlations you think you see. Honestly, I can't imagine how you're even attempting to gathering this info. Are you just randomly asking people if they've read 1776 during the interview?

But no, hiring "hundreds of developers" is still not the same as actually measuring. I do not believe that you have files that track how history-oriented your developers are (make them take a survey?) vs how productive they are, so that you can find a proper correlation. A proper study of this might yield a strong correlation (though I doubt it), but it would require a lot more than casual observation during your hiring.

I did assume that you were the one printing the programs, because that's how I read your reply. In the 'old days', compile time was a chance to print out your code on fanfold paper ...". If that was a misunderstanding, then I guess it changes the situation. Sure, if someone's already handed you a stack of printed code, why not look through it while compiling?

Hope you enjoyed your ravioli. Cheers.

Re:Why doesn't every company buy developers the best hardware? by gaius on Tuesday July 19, 2011 @09:14AM (#2780695)
I think about what the Old Masters programmed with just a single 80x25 green-screen terminal, and I weep for programmers today.
Re:Why doesn't every company buy developers the best hardware? by onemoreact on Tuesday July 19, 2011 @09:36AM (#2780803)
The expectations have increased over time. Batch processing banking transactions on a Manframe is a lot easer than writting a bannking website today.
Re:Why doesn't every company buy developers the best hardware? by kraemate on Tuesday July 19, 2011 @10:22AM (#2781006)
Not sure if being sarcastic .. Expectations might have increased , quality hasnt.
Re:Why doesn't every company buy developers the best hardware? by onemoreact on Tuesday July 19, 2011 @11:50AM (#2781411)
Quality and Scope are always at odds. Comparing a MUD to an MMORPG you might find programers producing similar amounts of bugs, but individual productivity has clearly increased.
Re:Why doesn't every company buy developers the best hardware? by kraemate on Tuesday July 19, 2011 @12:04PM (#2781485)
If you define individual productivity as the amount of misuse of hardware resources , then yes. In all other cases, no.

A few pretentious programmers wanting fast hardware to play with is one thing, but demanding it and proclaiming that programmer productivity has increased and thus all programmers deserve the best possible hardware is laughable at best.

Re:Why doesn't every company buy developers the best hardware? by onemoreact on Tuesday July 19, 2011 @02:08PM (#2782250)
Feel free to limit yourself to green screen terminal, but good luck building a GUI.

Anyway, fixating on HW like it has meaning outside of the software that runs is a common misconception, and assuming there is any reason to buy a PC with less than 200$ of ram is simply premature optimization. Today that works out to 16GB, in the past that may have been less than 16KB, but that does not mean 16KB was enough just that it was a point of diminishing returns.

PS: Assuming that the same assumptions will always apply even as HW gets 1000 times as fast is ridiculous. I know someone that prevented 1 million in computing hardware from being purchased due to a few weeks work. Today doing those same optimizations would be a waste of time because computing power has literally increased by that much.

Re:Why doesn't every company buy developers the best hardware? by mtogo on Tuesday July 19, 2011 @01:19PM (#2781938)
Should we build buildings with primitive tools that we used hundreds or thousands of years ago? I mean, builders back then built things just fine, we're so spoiled with our power tools and motor vehicles.
Re:Why doesn't every company buy developers the best hardware? by gaius on Tuesday July 19, 2011 @05:23PM (#2783142)
What they built lasted until now, that's how we know about it. How much modern stuff would last even a hundred years, let alone a thousand?
Re:Why doesn't every company buy developers the best hardware? by icebraining on Tuesday July 19, 2011 @09:27PM (#2783893)
Exactly what has lasted a thousand years without maintenance? I live in a country with very old constructions (Portugal) and all have had regular (heavy) restoration works across the years.
Re:Why doesn't every company buy developers the best hardware? by mb21 on Tuesday July 19, 2011 @04:33PM (#2782943)
I disagree. I think the overall quality of software built by software professionals has increased over time. It's the natural maturation of an industry (although I believe we are far from mature).
Re:Why doesn't every company buy developers the best hardware? by ams6110 on Tuesday July 19, 2011 @09:21AM (#2780732)
And often connected over a 300 baud dial up.
Re:Why doesn't every company buy developers the best hardware? by SkyMarshal on Tuesday July 19, 2011 @10:48AM (#2781127)
I offload to AWS too for personal stuff, but is there a way for a company or organization to manage a team of developers spinning up new instances for testing/compilation/etc.? The costs of that could be very variable, depending on the instance type and nature and frequency of work it's used for.
Re:Why doesn't every company buy developers the best hardware? by regularfry on Tuesday July 19, 2011 @06:29PM (#2783422)
We have a single LTSP server for the office which everybody works on. It's a 12-core, 44GB server with about 1TB of platters in various configurations attached. I think it cost around $8000 all in.

We do a lot of VM spinning, and it's a fantastic way to do that sort of work, plus managing a single server is much less overhead than managing 6 workstations.

Re:Why doesn't every company buy developers the best hardware? by mise on Tuesday July 19, 2011 @09:55AM (#2780891)
So I shouldn't buy a new MacBook Air for the fun of it? I guess the answer is no for PHP programming :)
Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @10:50AM (#2781135)
That wasn't my point -- do buy a MacBook Air just for the fun of it, if you have the money.

Whatever makes you feel better if you have the cash, plus for MacBook Air the portability gained is a great bonus and you may need it.

I was arguing about this notion that companies should buy the latest and most expensive hardware as that supposedly leads to better productivity, but I have my doubts about that. Better hardware does give better productivity, but it depends a lot on what you do with said hardware -- if developing PHP-stuff, no, you don't need a 20-core processor with 50 GB of RAM. You don't even need a MacBook -- any crappy laptop will do.

It's also debatable if you need big dual monitors and an office that looks like the cockpit of a plane. Yes it's cool. No, it won't help with your ADHD problems.

Re:Why doesn't every company buy developers the best hardware? by mise on Tuesday July 19, 2011 @11:54AM (#2781425)
Good points. Regarding the dual monitors, I find being able to move quickly between workspaces in Linux/OSX to be a good alternative (I use three workspaces for programming).
Re:Why doesn't every company buy developers the best hardware? by goldmab on Tuesday July 19, 2011 @09:16AM (#2780703)
I feel the same way. I have a Dell Inspiron that cost me something like $500 two years ago, and I have no problem doing Python development on it with vim. If I had a compile step I might feel differently.
Re:Why doesn't every company buy developers the best hardware? by Game_Ender on Tuesday July 19, 2011 @08:53AM (#2780624)
What language(s) do you work in?
Re:Why doesn't every company buy developers the best hardware? by swah on Tuesday July 19, 2011 @08:17AM (#2780517)
How much memory do you have?
Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @08:18AM (#2780520)
3 GB
Re:Why doesn't every company buy developers the best hardware? by shareme on Tuesday July 19, 2011 @10:24AM (#2781018)
you going to get irate at the next point..

I use Eclipse IDE on vmware-Ubuntu on a winVista 32 bit computer with not claims of bloated IDe slowing me down..it snot the IDE but the operator..more often times than not its improper eclipse.ini config that produces such bias rather than knowledge

Should not a java developer know how to use VM settings to set up their IDE? Its about like doing J2ee but not knowing how to do the VM setting son the server..is it not?

--rant off-

Re:Why doesn't every company buy developers the best hardware? by bad_user on Tuesday July 19, 2011 @10:55AM (#2781159)
My point about bloated IDEs was to highlight my specific setup and preferences, which may not be specific to your setup.

I also think that proper configuration should be preferred over hardware-investments. Heck, I lived in a time when optimizing Config.sys and Autoexec.bat was required for playing games.

I do get annoyed by arguments that take a small part of what I said and comment on it out of context. Don't take this the wrong way, but your rant is not warranted -- if Eclipse floats your boat then I have no problem with that.