News for hackers. Stuff that matters.
Re:We need both engineers and artists in programming by GeneralMaximus on Monday May 11, 2009 @09:11AM (#603402)
> People willing to trade the hard scientific measurements such as memory footprint and runtime speed for something so ephemeral as programmer happiness.

I'm sorry, but I just can't take this seriously. Runtime speed and memory footprint are not important anymore?

How will you justify to your customers why the software you just delivered takes several hours to perform simple operations? I'm sure they don't care about programmer happiness one single bit.

(I don't have anything against the guy who wrote this. I'm glad he found something he loves doing.)

Re:We need both engineers and artists in programming by davidw on Monday May 11, 2009 @09:32AM (#603440)
No, what he's saying is that there is a tradeoff involved, and that for many things, it's better to optimize for programmer time/productivity, rather than for machine time. This has been true for 50 some odd years:

http://journal.dedasys.com/2008/12/04/the-economics-of-progr...

Clearly, that's not true in all cases, and some code has to be fast. However, it's often best to avoid premature optimization - write the code, explore the problem domain, and then speed up the bits that need it.

Re:We need both engineers and artists in programming by marcusbooster on Monday May 11, 2009 @11:05AM (#603581)
I think we've reached the point where it shouldn't take "several hours to perform simple operations" on any modern compiler/platform. Instead, it shouldn't take several hours of a programmers time to develop simple operations.

I'd agree with the conclusion of this post, "Hardware is cheap, programmers are expensive": http://www.codinghorror.com/blog/archives/001198.html