Time to work

Article spread by permission of the author. The original is here .

I know two options for organizing the start of work at an IT firm and I had the opportunity to work with both options.

1. Coming to work at a specific time. Akin to the Soviet: at 8.00, everyone should be at work otherwise fine or even dismissal. They all leave at 17.00
2. Free arrival by any time. There may be a lot of variations when you have to work 8 hours a day or 40 hours a week or no one looks at all if only the work is done.

I worked for 7 years in a company where I had to come every day at 9.30 and leave not earlier than 6.30 pm, and now already half a year in a company where everyone comes and goes when he wants.
And now I'm ready to compare options.

The first option is usually justified by the fact that since at work one has to interact a lot, everyone should be at work at the same time. And then suddenly you will need a programmer A, but he is gone and the work has risen. Also, the first option allegedly disciplines people and adjusts to work. It is also quite simple for managers and other directors, since track employee time becomes very simple.
')
Cons of the first option :

• Coming to a specific time does not allow the employee to properly manage their free time. Maybe I want to do something before 4 am and then sleep a little longer? But no, I have to go to work, and which of me is an employee, if I slept for 3 hours? And if 2 days for 3 hours?
• Tracking "spent" time in IT is absolutely useless. For IT specialists, time is not converted directly into a product. The “mythical man-month” was written a long time ago, and far from all have read it. <Li />
  The work should be organized so that the absence of programmer A does not stop the whole process. Otherwise, no ward rules will help in case of force majeure. And forcing people to come at the same time is just a masking of real problems with the workflow.
  This option just annoys many people. And sometimes it causes a search for a new job.