Mark DiGiovanni

Sponsors

The Lounge

Wicked Cool Jobs

News

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
Shorter hours in software

It seems that shorter work days are the new trend in the software industry.  I think EA helped bring this to the forefront, but companies may not be all to blame.

A tough-guy culture among coders also seems to have been a factor. Last year, the International Game Developers Association cited this as a reason for horrible working conditions in the computer game world.

"Developers are sometimes just as much to blame for submitting themselves to extreme working conditions, adopting a macho bravado in hopes of 'proving' themselves worthy for the industry," the professional group's board said in a statement.

Does working overtime produce more work?

Research indicates that long hours don't translate into heaps of extra work. Consultant DeMarco has studied productivity data and concluded that workers putting in 44 hours per week generate the same amount of work as those who put in 36 or 37 hours.

"There's nothing to be gained from the extra hours," he said. DeMarco argues that there are limits to how much people can churn out without adequate breaks, and companies with cultures of long days tend not to run meetings in a disciplined fashion.

Read on here.

—Mark


Posted Tue, Feb 22 2005 10:08 AM by Mark DiGiovanni

[Advertisement]

Comments

Darrell wrote re: Shorter hours in software
on Tue, Feb 22 2005 9:34 AM
The problem is in what is considered work? The 36 or 37 hour developer may be doing the same amount of work, but is not improving him/herself at all. The 44 hour worker may be doing some personal improvement on company time, and in the long run will be a much better employee.

Of course the 37-hour worker may be improving at home, and the 44-hour worker could just be slow, too. :)
Devlicio.us