The Happy Secret To Better Work

We believe that we should work to be happy, but could that be backwards?

Conventional wisdom holds that if we work hard, we will be more successful, and if we are more successful, we will be happy.  Yet, sadly, this no longer seems to be the case for many people, does it? 

When  we achieve success, whether it’s a new job, a promotion, or losing weight, we are happy – for a while.  But when the newness wears off, we find ourselves back in the same state of dissatisfaction that we were before, so we set our sights on a new success that’s finally going to make us happy.  And the cycle keeps repeating.

Recent research in the field of Positive Psychology has shown that it actually works the other way round: happiness helps make us more successful.  The dust jacket for The Happiness Advantage says:

“When we are positive, our brains become more engaged, creative, motivated, energetic, resilient, and productive at work. This discovery has been repeatedly borne out by rigorous research in psychology and neuroscience, management studies, and the bottom lines of organizations around the globe.”

A Software Developer's Life

    These are animated images making us smile by reflecting the friendly faces that remain for developers when all kinds of things happen during their working hours.  

When something that was working on Friday, did not work on Monday

Developing without specifications is like

Uploading something to the production environment

Asking someone for resources is sometimes 

Finding solution to the problem without searching on Google

Closing the IDE without saving it

Fixing bugs late in the evening

When boss reports the module one has been working on will never be used

When the regular expressions returns what's expected

When one shows the boss the bug that one has just fixed

When one updates a database script and realizes that one has deleted the entire database

When one uploads a code without testing and it works as expected

When marketing folks show to the developers what they have sold

Applying CSS for the first time to a web page

When system admin grants one the root access

When a colleague proposes coffee break in full swing

When one goes on leave while the others in office are still trying to fix all issues

When one realizes there's gonna be an extra pay if project ends before the deadline

The fellow with whom one intends to develop

When the client tries to click on the model

When the bug goes unnoticed

When the customer wants changes two days prior to the climb to production

When the demo's unwound without any bugs

When the code finally runs

When the project manager enters the work room

When one's asked about his code being used everywhere

         Which one is your favorite out of the above. Also, if you are a developer and have had any such similar experience go ahead and share it with us. 

The best of National Geographic's Pics