Why you should not work extra hours

There are pros and cons in working extra hours or over time regularly, here is an attempt to list them all. Some are well known, some are taken from my experience, if you know other reasons just comment and I’ll include them in the list.
 
 
 
 
 
 
 
 

CONS:

You are going to introduce bugs 

bVkZi3B

Human concentration does not last for long time, and it decreases drastically if your brain doesn’t rest properly.
We are already introducing bugs when we are extremely focused and well rested in the morning, so it’s easy to imagine the disaster that can happen at 10PM.
8 hours of mental work a day is more than enough for your brain.

Your changes cannot be promptly reviewed 

enhanced-buzz-30149-1390858215-15Code reviews is an extremely powerful tool that is widely used by team in order to control code quality. It works perfectly when reviews are done immediately and you can talk face to face with your team members. It works well when it’s done using tools like Gerrit, Reviewboard and so on. It works bad if every morning there are tons of lines of code to review because of nightly or extra hours commits.

Stories team estimation goes wild

92767.strip
One of the most painful part of any agile team is the stories estimation (less in Kanban, more in Scrum). It is painful, stressful, long and it is tiring for all the participants. Estimations are based on stories complexity and time. The time is the 8 hours per 5 days a week. Now, all this estimation gets distorted and so useless when team members regularly work extra hours. Team will get frustrated.

You can create tension between team members

 
anigif_enhanced-buzz-21029-1384455707-19
One thing I noticed in teams where some members work over time, is the presence of hostilities and tension. Why is that? People that follow regular work hours can be worried about their career being compromised because they do not stay longer in the office. People who work late can see the others as non involved/interested enough on the job. Solution? simple, stick on regular hours.

You create wrong expectations

bossw
Everyone knows, you give a hand and they want your arm. You work regularly over time and your manager will start soon to expect and to count on you to stay late.

You lose a great part of your life

missgirls
Yep.

PROS:

giphy
 

Related Whitepaper:

Software Architecture

This guide will introduce you to the world of Software Architecture!

This 162 page guide will cover topics within the field of software architecture including: software architecture as a solution balancing the concerns of different stakeholders, quality assurance, methods to describe and evaluate architectures, the influence of architecture on reuse, and the life cycle of a system and its architecture. This guide concludes with a comparison between the professions of software architect and software engineer.

Get it Now!  

2 Responses to "Why you should not work extra hours"

  1. Manuel says:

    Completely agree!

  2. Riccardo says:

    Good post, but you’re forgetting one important thing: if you’re paid, say, 100 for 40 hours in a week, that’s 2.5 per hour. If you work 50 hours in that week, that’s 2 per hour. Basically you’re underselling your work; that’s bad for everyone in the long run, not only for you.

Leave a Reply


× 9 = eighty one



Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use | Privacy Policy
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.

Sign up for our Newsletter

20,709 insiders are already enjoying weekly updates and complimentary whitepapers! Join them now to gain exclusive access to the latest news in the Java world, as well as insights about Android, Scala, Groovy and other related technologies.

As an extra bonus, by joining you will get our brand new e-books, published by Java Code Geeks and their JCG partners for your reading pleasure! Enter your info and stay on top of things,

  • Fresh trends
  • Cases and examples
  • Research and insights
  • Two complimentary e-books