Developers on Flexi hours

[SauRoNZA]

9-6 or 6-3, with lunch.

Oh you meant core hours. I'm with you now.

 

[Pho3nix]

Rubbish.

Do more in less hours, that will get you noticed. People who hang around trying to look like they are working are surfing the net.

I have been lucky, I'm in support so my hours are varied and they have been relaxed about when I'm in the office as long as I'm available.
Its starting to change a bit as more people have joined our office and they wan't to be as informal as I am. Before we were just a satellite office with 2 -3 guys.
The head office has always been more strict but they get to have flexi time as well. They just have to be in 9 -3

And when you finish your work, you sit idle because you've done all your sprint work?

 

[Mike Hoxbig]

You are speaking of efficiency. I am speaking of going the extra mile...

Go the extra mile doing what? There's a finite amount of work available. 'Going the extra mile' and taking on more work points to a staff shortage - the only reason it would impress your boss is because it shows them that you're willing to be their slave. They can get away with saving on staff costs while offloading additional work onto those who are 'willing to go the extra mile'.

People with this mentality need to realise that they're part of the problem, not the solution. One should get recognition for their productivity and quality of work, not the volume of work that they take on. It unfairly disadvantages people who are actually productive and have lives outside of work...

 

[LLoydizle]

I can come in between 6 and 10 and work 8 hours (or 7 if I don't wanna take lunch). But I'll gladly do overtime when I am behind or need to be around.

 

[Syzygy78]

Go the extra mile doing what? There's a finite amount of work available. 'Going the extra mile' and taking on more work points to a staff shortage - the only reason it would impress your boss is because it shows them that you're willing to be their slave. They can get away with saving on staff costs while offloading additional work onto those who are 'willing to go the extra mile'.

People with this mentality need to realise that they're part of the problem, not the solution. One should get recognition for their productivity and quality of work, not the volume of work that they take on. It unfairly disadvantages people who are actually productive and have lives outside of work...

Going the extra mile can mean so many things, not just investing more time. This could mean refactoring code that everyone else avoided, but you stepped up and took initiative. Instead of just sitting at the next presentation, why not actually stand up and engage with the client? These are but small examples of what going the extra mile means when not constrained with your definition of it. Yes, perhaps you do all of these things, but many people do not. There is also nothing wrong with arriving 15 minutes earlier to work to sort out pesky admin that a lot of programmers are so very bad at.

No, I believe it is your mentality that is problematic. So lets agree to disagree since you are so biased against going the extra mile.

 

[DominionZA]

I work an average of 12 hours a day. Purely because I love to code.

Company scores because of the extra hours, and in return I get very flexible work hours and good bucks. It's a win win when you love what you do and can't help doing extra. On top of the day job, I also own a system that I work on almost daily.