I never consciously thought about sleep until I started working. During the days I was growing up, I had never felt sleep deprived ever. I also slept early, well into the mornings and there were too less of distractions to keep me out of bed.

Things started to change as screen time started to conquer the lives. My grandfather used to call the TV as the idiot box, even though there was only 2 hours of watchable programs every day. He said that this makes people lazy consumers and not able to do anything productive. He said that entertainment should only be used like medicine not like food.

The screen addiction was very evident even without smart phones, I have played snake game for hours together on the old Nokia phones often postponing sleep. It is very hard to limit screen time, often those endless titbits we read/watch is not of so much use and the games we play does not relax us but bait us into playing more.

If I look back, many of my bad days were due to having a bad sleep the previous night. Sleeplessness increases the fatigue, turns it into a chronic cycle of yawning, lethargy and sleepiness. Often this impairs judgement because a sound body is a higher priority in hierarchy of one’s needs.

How to sleep well, it is very hard to find a rhythm that works for a person as each person is unique. The ones which has always worked for me very well are; social media off at least an hour before bed, reading a light book to switch off the buzz in the head, keeping the room cool, a cozy bed, dim lights from an hour before bed, enough physical activity during the day to make me tired but not fatigued. This setting worked like clock work for me for years. I used to go to bed same time everyday and wake up at the same time every day.

If I succumb to the temptations of sleeping late for a few days, then things go out of gear which takes a few weeks to get back into rhythm. For me a good night always meant a good day next day.

Someone I met last year mentioned that the reason the 737Max planes went down was because it was coded by developers from a country where there was no aviation engineering experience. This person also went on to say “What else can you expect from people who are paid less than 9$ an hour wage”.

What is evident from this person’s thought is, irrespective of all the experience in aviation, expensive engineers, highly paid directors this crash was a result of a developer who coded as per the specification given not because of the carelessness of the others, in spite of airline industry being one of the hallmarks of safety standards.

Why this kind of thought irritates me is that a lot of people equate cost to quality. If something is not expensive, it is of poor quality. Expensive flights like concorde ran into losses, nobody eats at michelin star restaurants every day even though they are the best in the business.

It is very much possible to reduce cost without cutting quality, recent example I could think of is SpaceX that too in space technologies which is “Rocket science”. If something has failed, it is not necessary that the component of poor quality always costs the lowest.

Many software developers are in favour of a kind of laziness, the laziness to think, design and test clearly. Instead they are very active in creating pages and pages of code, endlessly run the application in debug mode doing a treasure hunt for bugs and spend countless hours fixing bugs and regressing many others.

Steven Wright, a standup comedian says, “Hard work pays off in the future. Laziness pays off now”. That is very true for the brain, for subconscious part of ourselves, any new thing is an irritant. Brain will find a way of rewarding itself with chemicals when it is able to gratify very quickly, thereby rewarding more and more lazy behaviours.

It is super easy to nudge someone to be lazy than the other way. That is the reason a person may skip gym for a whole week but will find it tough to go to it for a week. This is the point where software development mangers do a double whammy by saying “I want the output fast, I don’t care about quality” thereby disrupting the delicate balance the developer had between quality and speed.

As a result, the developer ends up adding a new flag, changing all the methods from the controller to the repository to take that flag and finish off the work in a record time. The developer may also get rewarded with the developer of the month award. Other developers get the idea, they eye for more awards and recognitions.

The worst thing to teach a teenager is to borrow money and buy to fulfil their immediate needs. The teenager will never be able to grow out of that nasty habit. The same applies to programmers, if you tell them early in their career that they can compromise on quality to achieve speed, they are not only going to ruin themselves but also take their team down along with them.

Quality work is like investing in compound interest, you can only realise over time but in unimaginable levels. In one of our teams, we had a strict adherence to quality routines. The manager had only one yardstick to measure, it was no of stories delivered. The speed of the team went up to 8 times in the 12th week when measured against the first two weeks. We had to ramp the team down to keep up with the flow of the requirements.

For many, laziness pays off now but makes them and others around bankrupt in the longer run