How Important Is Programmer Punctuality?

Question

I found the article entitled Evidence Based Scheduling interesting, where Joel Spolsky himself states that programmers "don't really like to make schedules".

Might there be a correlation between not liking to make schedules and not liking to keep one?

For example, I am working on becoming less habitually tardy, but I hate having a schedule, and so I'm wondering how much the schedule matters, as opposed to one's attitude towards executing it.

UPDATE: I was originally curious about tardiness, but that question was too personal and arguably hard to tie to the programmer lifestyle. I believe that it is fairly common for programmers to be given flex time, especially if they are expected to be available for middle of the night coding fixes. I have also seen this management attitude with other creative folks such as graphic artists, even though some people gripe that they are not available to be pestered during all of the 'normal' business hours. I agree that chronotype could is potentially a factor for many in their desire to keep odd hours, but I also agree that it's a pragmatic necessity to deal with one's obligations and the boss' expectations.

Answer 1

If you are having difficulty being punctual for work, that's something that you, yourself have to deal with. Most people in the world need to be on time for their jobs, and most of those people manage without any difficulty.

Being a programmer does not make you "unpunctual," nor does creativity or any other personality trait; if you are constantly late for things, then you have simply failed to effectively manage your schedule. This is not a personality anomaly.

Answer 2

I am punctual to all my commitments. I don't see showing up at work as one of those, it is just showing up at work. I'm usually close to on time, it doesn't matter where I work, so I don't stress about it.

People have "out-sheeped the sheep, because we've dispensed with the sheep dog. We police each other." Our behavior stems from how we fear what others will think of us, and what they will say if we are different.

I say bah to that. Be yourself, do what works for you. Most programmers are narcissists, and I am no exception.

As far as giving yourself your own attitude adjustment, I say that's harder to do than giving yourself a haircut. Try changing your scenery. Go to the bar and get the crap kicked out of you, as long as that's different from your usual routine.

Sorry this seems like a non-answer. Just my thoughts to a not too specific question.

Answer 3

Your aptitude for being punctual really seems linked to just personal habits and personality.

I used to hate the morning, couldn't get up early, couldn't function well, loved staying up late and working into the wee hours of morning...but that wouldn't cut it with my current job.

So I had to change, I worry less about what profession I am in and more about what I need to do to be successful and keep moving up/forward with my career and towards my goals, this is the motivation I use to keep punctual. I have also established with myself that 30 minutes early is on time, and any time after that I'm stressed out from feeling "late".

If you make it important enough to be to work on time, like real consequences are waiting for you if you ARE late (with all the layoffs right now, I'd be scared to death to be habitually late), then chances are, you will be on time.

Just my opinion, good to hear you've jump-started your desire and career, I hope things work out well for you!

Answer 4

It really depends on the work environment.

I worked at a vfx shop and they didn't care when the developers (or artists) showed up as long as you were productive and put in your time. Some guys would show up at 7:00 am and leave at 4:00. Others would show up at noon and work into the evening.

Other jobs were in a more traditional office (like a financial services company) and punctuality was more important. In theory, it shouldn't have mattered if the programmers showed up at noon if they were doing their work, but in practice it looked bad. If the executive whose reports you're working on comes by your desk with a problem at 10:30 and you haven't made it into work, there's going to be a problem.

As well, it was annoying for the other people in the office whose job did require them to work normal hours to see developers in the IT department come and go as they please.

I guess the short answer is: if you can't fit into the culture at your workplace, your choices are basically to (1) adapt (2) find a new job or (3) be miserable.

Answer 5

Being punctual is a sign of respect for the people you work with. Being late for a meeting implies that you think you are more important than they are and do not need to make the effort to be punctual.

Its all about perception. It does not matter why you are late, only that you are late.

Answer 6

I've got a similar problem, in that I hate sitting in morning traffic, or evening traffic. Luckily, my boss was amenable to a solution-- basically, that I work 8 hours a day, no matter which 8 hours they are.

We aren't factory workers, who can just show up and expect to perform. Now, I'm not disparaging factory workers, and in fact, I envy the fact that they can have very specific timelines and delivarables. The guys at our work have to make so many machines a day, and there's very clear performance metrics for them in terms of both quality and quantity. We don't have that luxury, and so have to define 'success' in a different way. As a result of that, 'hours on the job' is no longer a particularly useful metric for determining the success of a programmer. Other metrics, such as customer satisfaction with the product (always a tricky target to define) and functions implemented that make money (also tricky) start to take center stage.

So the actual, particular hours worked isn't probably that big of a deal, just so long as you (and your team) overlap with others in the company so that the solutions you produce are relevant.

Answer 7

Maybe this issue is not so much about being punctual as about being a chronotype that does not fit well with common working hours.

Answer 8

I think programmers not liking schedules has more to do with management/customers not liking requirements. e.g. I'd give you a better estimate if I had any idea what it is you really want me to build.

Answer 9

Gbrandt has it right, 100%

Answer 10

A good solution to have a level of flexibility while keeping it productive is to let employees come in at work between, say, 7:30AM (leave at 4:30PM) and 9:00AM (leave at 6:00PM).

This way you have everyone at work between 9:00AM and 4:30PM, which is necessary if your development teams are focused on team work and you want to get the flow going, plus you're not being too rigid towards employees as far as schedules go.

Answer 11

The more anal a company is about face time the less likely they are to be able to hire or retain the really top level of programmers. When you come down to it, its the quality of code that matters, not that someone punched in a minute 'late'.

I was the first programmer in what is now a six year old company with 7 developers, 2 testers, and several interns, artists, and other folks.

Being retired military I of course am programmed to show up at a time certain (9am for me), and it worries me if I'm even a minute late.

On the other hand we've since hired several superstar level developers, none of whom can be counted to show up before 10am, if they show up at all. And forget being able to start a meeting on time.

These guys bother me a bit with their un-punuctality. On the other hand they can solve really tough technical problems and can generate lots of quality code quickly. You can take their estimated completion dates to the bank.

Maybe somebody else is in the business of building their fragile ego by bullying employees, but we're in the business of delivering quality code. And quality code comes from talented developers who are treated as the valuable professionals that they are, not clock punching beaten down serfs.