News for hackers. Stuff that matters.
Re:The GOOG-MSFT Exodus: Working at Google vs. Working at Mi... by evilneanderthal on Sunday June 29, 2008 @06:27PM (#231532)
If you go by what the on-board shuttle group [1] is doing for NASA, more process is the key to a better functioning organization.

But then, that's how software should be written when there's lives on the line, which doesn't exactly describe Google.

Still, something to aspire to.

[1] http://www.fastcompany.com/node/28121/print

Re:The GOOG-MSFT Exodus: Working at Google vs. Working at Mi... by cliff on Sunday June 29, 2008 @07:15PM (#231547)
Sure, but there are plenty of downsides to this.

I've always been fascinated by and impressed with NASA's software methodologies, but they are neither cheap nor fast.

I'm not sure it's something to aspire to as much as one extreme on a continuum of code quality vs. code cost.

I would suggest that it would not be in Google's nor in most companies' interest to do anything like this. Where a company falls on this line depends on their organization's size, purpose, and business model.

Re:The GOOG-MSFT Exodus: Working at Google vs. Working at Mi... by evilneanderthal on Sunday June 29, 2008 @11:17PM (#231671)
What I was aiming at was the notion that creating maximally stable software that does exactly what it's designed to do is something to aspire to.

Just my opinion, obviously. You could be right that the above is not in most companies' interest.