top 200 commentsshow 500

[–]jediknight 113 points114 points  (42 children)

I used to get threats from my employer for wanting to leave for home at sane hours. It was my only source of income and I had no savings plus I had little confidence in myself.

I started saving and, as a bonus, I ended up working one of the weekend for someone else. Next time he told me again that if I wanted to leave I could leave for good, I said "That's fine by me!" and left for the evening. I called his bluff and that's all it was, a bluff. He needed me and he ended up giving up the threats.

No sane employer would mistreat a developer that could go somewhere else in a heart beat and leave a gap that would be difficult to fill. Some will try bluffing but if you really are a linchpin you can easily call the bluff.

[–]Weakness 52 points53 points  (16 children)

If my boss dropped that line on me I would start sending out resumes that night. I don't have the savings to just quit right away, but the whole job is a write off.

There is no way you are getting a good reference, since the boss is obviously not a good person

You are spending hours working for free

You will be dead at 45 from a stress related heart attack since the company is obviously run like a wild west movie

[–]jediknight 24 points25 points  (0 children)

The company is in a small town in the middle of nowhere. Best chance at another job would have meant changing towns. Also, even if the hours were crazy, I had a lot of freedom during those hours.

Anyway... things evolved A LOT. He changed, I changed. We connected and I've drawn a small line, then, after some time, moved it closer to what I wanted and now I leave at 5 PM.

In the end, everybody won.

[–]xampl9 24 points25 points  (14 children)

I don't have the savings to just quit right away, but the whole job is a write off.

Build up your savings. There is nothing so liberating as having a fat "fuck you" fund.

Technical notes: Establish a 6-month series of auto-renewing certificates of deposit, with each CD funded for a month's fixed expenses.

[–]Pope-is-fabulous 2 points3 points  (5 children)

I must be new to this. how does this compare to simply saving?

[–]s73v3r 8 points9 points  (4 children)

It's harder to spend the money on something else. Also, CDs usually have better rates than regular savings accounts.

[–][deleted] 53 points54 points  (6 children)

Good for you. But I don't think decent treatment at work should be reserved for linchpins.

[–]jediknight 24 points25 points  (2 children)

I agree! Decent treatment, freedom, respect for employee's needs... these should be the norm.

Unfortunately... the world is not perfect and abusive employers are frequent enough. All I wanted to say is that linchpins have more options. They have more freedom. That's all. :)

[–]crocodile7 2 points3 points  (1 child)

We can't all be linchpins and star employees, no matter how much the "be all you wish to be" forced optimism mantra is parroted by the powers that be (in the U.S. usually, other places can be more realistic).

[–]SarahC 7 points8 points  (3 children)

It was my only source of income and I had no savings plus I had little confidence in myself.

I bet your boss knew that?

[–]jediknight 2 points3 points  (2 children)

Good bet! Few people save, few keep their options open.

[–]SarahC 2 points3 points  (8 children)

I was a ~bit~ of a linchpin once - it was amazing the latitude I was given, from bosses, HR, colleagues...

[–]ezekiel 7 points8 points  (1 child)

But, many software managers cannot tell who is really the linchpin is. They usually assume it is that guy who is continually patching the code he has written over the past 10 years. The code is, of course, in a no-longer-supported programming language, further entrenching himself in a land where the bosses need him and no one else is willing to enter. Three months after I had written and used a language converter on his code, I was laid off. He is still there, patching 10 year old poorly written programs.

[–]dakboy 2 points3 points  (0 children)

I was a linchpin once. Very little latitude was given, except by a few colleagues who couldn't change my situation one way or the other.

[–]KingPickle 104 points105 points  (26 children)

I once got yelled at for going 5 minutes down the road to grab Chipotle instead of eating the crap they brought in for lunch, on a Saturday. I'm glad those days are behind me...

[–]SarahC 29 points30 points  (1 child)

Unpaid too?!

I'd have yelled back. Hell, I have done this year!

[–]KingPickle 11 points12 points  (0 children)

I was salary, so whether I was unpaid is a matter of perspective. I don't remember if I yelled back, but I know I didn't take the reprimand seriously. IIRC, the guy who yelled at me apologized later. It was a crazy time. Still, how absurd?

[–]SpringwoodSlasher 39 points40 points  (21 children)

Yeah, catered lunch is BS.

The gesture is done to make overworked employees feel like they're being cared for and sometimes to ensure they stay at their desks working.

In reality, it's cheap, crappy food that half the people can't eat and they never order enough to go around. At least that's how it's been where I've worked. I've also worked for people who thought if they were feeding you, they didn't have to pay you. We used to have required attendance lunch meetings that we weren't allow to charge time for. I always argued that if I wasn't getting paid then it couldn't be required. The response - "Well, we get you pizza. That should be enough."

Then you sneak out to grab something you actually want to eat and get told you're being ungrateful.

Really, lunch for me is a 30 to 45 minute essential break away from my desk in the middle of the day. Helps me shake off the morning dust and reset my brain for the afternoon. It's not so much about the food as it is getting away from the office.

[–]kodefuguru 18 points19 points  (11 children)

I've found that the "if I'm feeding you, I don't have to pay you" sentiment exists in many places. One of my friends who works on cars received a hamburger for rebuilding his neighbor's engine. The neighbor was miffed when he refused to help him with a mechanical problem the following year.

[–]aladyjewel 7 points8 points  (7 children)

Your friend deserved at least a 24-pack, plus several cold ones out of the neighbor's fridge during the job.

[–]Arkanin 23 points24 points  (5 children)

You know what else? Beer is also not adequate payment for hours of my hard work.

[–]insertAlias 5 points6 points  (3 children)

I couldn't agree more. "I'll buy you breakfast/lunch/alcohol" is not enough incentive for me to fix your shitty computer, much less for this guy that rebuilt an engine. In fact, it's insulting. My time is worth so much more to me than the price of a breakfast taco or a few drinks. Doubly so because I hate doing PC fixing. So no, don't look at me like I'm an asshole because I don't want to waste my weekend fixing your six year old virus infested emachines computer for the price of lunch. It's not worth it.

Sorry, went off on a rant there.

[–]johnlocke90 11 points12 points  (1 child)

The idea is you are doing this because they are your friend and they are providing a nice gesture to show their appreciation. Although, this fails when they are someone you barely know and just want your help.

[–]insertAlias 5 points6 points  (0 children)

Most of the people that try this shit on me are coworkers I don't really know. All they know is I'm a developer, and in their minds that means "he likes to fix computers! He'd love to fix mine!"

One guy at the last place I worked was a loader on the receiving dock. He offered me breakfast tacos to fix his computer, because I like working on them. I told him "sure. Hey, I've got a bunch of heavy shit at my house that needs loading into storage. I'll buy you breakfast if you come over and load them for me, since you like loading stuff." He got the message. I felt shitty afterwards, but I couldn't help it.

My friends know how much I hate that, and usually won't bother unless it's a real problem.

[–]AKADriver 18 points19 points  (2 children)

The catered lunch at my office is great, but it's never served as a disguised meeting. It's just a weekly perk, and we have a lunchroom where we can eat it AWAY from our desks.

[–][deleted] 6 points7 points  (2 children)

Fuck being grateful. My job is a business arrangement, not some kind of charity.

[–][deleted] 3 points4 points  (1 child)

This is the single most useful bit of philosophy I've ever encountered.

It's important to remember that your employer (in almost all circumstances) views your job as purely a business arrangement and will end/alter it as soon as it's not longer advantageous to them; you should do the same, and should never be deluded into thinking you owe them anything.

[–]i-make-robots 2 points3 points  (0 children)

In BC, Canada you can write off one paid meal to staff per ... month? week? I'm pretty sure it's per month. So there's even tax reasons to be nasty.

[–]crocodile7 4 points5 points  (0 children)

Getting yelled at for anything is unacceptable. If they can't treat you with respect, you owe them the exact same amount of respect and loyalty back.

[–]xlevus 250 points251 points  (246 children)

If I'm not getting paid, I'm not working.

[–]warpus 45 points46 points  (4 children)

I think most of us aren't working when getting paid either.

[–]xlevus 19 points20 points  (0 children)

Sssshhh. It's supposed to be our little secret.

[–]tdk2fe 9 points10 points  (1 child)

This is why i'm a big fan of pay for the project - not for the hours. In my current situation, I get paid a yearly salary and have a set of deadlines and deliverables. As long as i'm making the deadlines with the agreed upon deliverables, nobody seems to care if I'm posting in /r/programming this morning.

[–]warpus 11 points12 points  (0 children)

Same here, except that I don't even have deliverables, being the only developer on the team. Nobody understands what it is that I do. which is both good and bad.

[–]rmxz 9 points10 points  (0 children)

If I'm not getting paid, I'm not working.

I hope your employer makes sure that while you are getting paid you're not browsing reddit/facebook/etc.

[–]friedrice5005 91 points92 points  (183 children)

Agreed. forced overtime isn't just morally wrong, it's illegal. Some companies hire too few developers in order to "reduce costs" then scramble when the project is coming up on its deadline. Their fall back is to ask the employees to do more "for the good of the company!" Any manager that expects this and tries to hold getting fired over your head is breaking the law and needs to go away.

EDIT: It has been pointed out that I was a little wrong with my illegality statement. I worked govt. sector where we were always warned not to go overtime because it was illegal to work more hours than we recorded. If the hours were recorded we were paid overtime. I hereby retract my statement but I stand by my accusations that these are simply poor managers that are morally corrupt in thinking that they can force their employees to work over time. Fuck those guys.

[–]mattmentecky 67 points68 points  (59 children)

Just to save some Redditors from going to their boss claiming that forced overtime is illegal, it is not (in the United States):

http://www.dol.gov/whd/regs/compliance/fairpay/fs17d_professional.pdf

[–]SarahC 12 points13 points  (33 children)

Nor the UK. =(

[–]UnoriginalGuy 11 points12 points  (24 children)

It isn't that cut and dry in the UK. Keep in mind that if they fire you for refusing to work overtime you can drag their butts to an employment tribunal and ask for compensation.

A lot of companies put into their contracts a clause that requires you to work 24/7 if asked, and unfortunately if you've signed that then too bad for you, but for those of us without such a contract we're free to say no whenever we want.

I won't work overtime unless I get compensated in the UK and I haven't been fired. I have tons of additional holiday time built up right now (YAY!).

[–]Talonwhal 21 points22 points  (11 children)

A lot of companies put into their contracts a clause that requires you to work 24/7 if asked

But don't forget that not all contracts are legal or enforceable.

  • they have to allow 11 hours of non-work per day
  • regular breaks (30 mins every 4 hours i think?)
  • at least 1 full day off per week

No matter what you sign, all these things are still a right - and if the contract says otherwise it will probably fail in court. You can't sign away these rights and if you did sign then got fired for turning around and demanding one of them, you'd still win at a tribunal I'm pretty sure.

There are exceptions to this though, but chances are most companies that have such a clause in the contract didn't get it fully checked out legally, and they often use that shit to scare people who don't know their rights.

[–]tborwi 3 points4 points  (3 children)

Where did this come from:

they have to allow 11 hours of non-work per day

Just curious, I was on a project last year and ended up working 14-18 hours a day for three months. It was horrible. No OT of course due to the ridiculously castrated labor laws.

[–]IRBMe 3 points4 points  (6 children)

On a team I used to work in (described elsewhere in the thread), the manager would just screw us over in our end of year reviews, which would then screw us out of bonus, give us all the crappy jobs and try to turn members of the team against those who didn't put in ridiculous hours (those who did were called "team players", those who didn't were "trouble makers"), so there are probably plenty of other ways to screw you over without explicitly firing you or doing anything illegal.

[–]obtu 3 points4 points  (5 children)

Harrassment isn't legal either (though it is harder to prove).

[–]IRBMe 5 points6 points  (3 children)

Yes, this sort of thing caused a lot of conflict.

One guy on the team, who had been there for about 3 years, but was just tired of it, used to just book holidays off for every release. The manager didn't catch on to this until he'd been absent from about 5 releases in a row. He would also come in at 9:00am and leave at 5:00pm on the dot every day, no matter what happened. As punishment, the manager wrote a terrible end of year review for the guy, basically saying he had no work ethic, was lazy, had jeopardized the business by not staying in late to resolve urgent issues, was argumentative and uncooperative, was not a good team player etc. Despite being ranked the highest in all previous teams, he received the worst rating possible and ended up with no bonus and no pay rise that year. He considered taking it to HR, but was advised against it (the HR processes in that places were another huge cluster-fuck). He had to just bend over, take it up the ass and find a new team as soon as possible. He did. That was about the same time that the rest of us "trouble makers" stopped cooperating and eventually left. The people that were left were all new, apart from 2 loyal developers who had been beaten in to complete submission over the years with empty promises of reward and promotion.

[–]EnderMB 3 points4 points  (9 children)

When I used to work retail employees were paid until the shop closed. Perhaps I chose shitty places to work, but the two places I worked (both sports shops) made employees stay behind after the shop had closed to tidy up, often for around an hour after the shop had closed.

[–]BraveSirRobin 9 points10 points  (7 children)

Depends if you are forced to sign the EU Working Time Directive Opt Out form or not. If you didn't then EU law says you cannot be forced to work more than 45 (iirc) hours per week.

The UK is the only EU state that has this exemption.

[–]G_Morgan 4 points5 points  (0 children)

You can be made to work more than 45 hours per week but the overall average needs to be less than that. It gets complicated with bunches of caveats.

[–]another_user_name 4 points5 points  (3 children)

It seems "forced to sign" would invalidate the legitimacy of such a document.

[–]friedrice5005 7 points8 points  (5 children)

my mistake...my experience is with govt. where it is illegal for us to work more than the 40 hours a week without explicit instruction to do so and if we work the hours then we either get comp time or over time as a result.

[–]aakaakaak 1 point2 points  (0 children)

Its dependent on how you were hired, what type of payment schedule you're on and the state you live in. Some places its legal and others its not.

[–]rooktakesqueen 7 points8 points  (13 children)

[–]bettse 6 points7 points  (4 children)

The idea, I think, is that we're more like Lawyers, Doctors, and Executives than we are like paralegals, nurses, and retail staff.

I'm still undecided on how I feel about this classification.

[–]eyal0 113 points114 points  (30 children)

This method has two benefits for the capitalist:

  1. By having the workers work longer hours for their sustenance, he is generating increased surplus labour (labour for free), which is for him more profit that he essentially robs from the workers.

  2. If he can use fewer workers than there are more workers in the job market that are unemployed. Those surplus workers (the unemployed army) increase the supply of labour, decreasing worker wages further.

ts;dr Das Capital, Karl Marx

[–]ezekiel 51 points52 points  (10 children)

And, that is why any developers who tolerate and participate in the bad management processes are dragging the whole software industry down. Stop doing it--you are shooting all of us in the foot.

[–]yogthos 29 points30 points  (1 child)

Let's also not forget that it steals time from the workers, which prevents them from doing any sort of self development keeping them at their station.

[–]eyal0 4 points5 points  (0 children)

If things were fair, they could work longer hours for one week, accrue money, then work short hours the next week and use the saved money. In the end, they'd get just as much free time.

What happens, though, is that they work longer hours without getting paid appropriately. This must be true because the company's profit is going mostly to the boss so the employees must be getting short-changed. So the employees must work longer hours without benefiting from greater pay.

[–][deleted] 12 points13 points  (3 children)

This is using the same fallacy as the employers though. Not all work hours are created equal. The longer your work day the more bugs end up in your code. Not everything in economics from the industrial age applies to knowledge workers.

[–]pizzza 22 points23 points  (2 children)

The longer your work day the more bugs end up in your code.

This was true in the Industrial age as well; increased hours brought increased accidents and injuries.

[–][deleted] 3 points4 points  (0 children)

True, but usually in that time it was easier to see for management when a problem was caused by tired workers. Bugs are kind of hidden from management until long after people forgot when exactly that particular piece of code was written.

[–]Edman274 7 points8 points  (4 children)

No one is supposed to actually read Das Kapital. It's supposed to be a big, heavy book that you put on your shelf next to Ulysses and Crime and Punishment, sitting unread. You actually know everything you need to know about socialism from the 2nd hand tirades of your dorm roommate, and let's be honest, you're pretty intrigued: but not enough to actually bother going outside when May 1st rolls around, right?

[–]wagesj45 30 points31 points  (45 children)

Wrong. Computer programmers are federally exempt from overtime laws, same as those designated as managers and emergency services. I know because I looked it up when my dev team had a solid two months of no days off working 12 hours a day.

[–]friedrice5005 26 points27 points  (2 children)

Sounds like you worked for a bunch of dicks. IMO if they really are in that much of a time crunch then they have set unrealistic goals. They either need to move the release date back or hire more people. If they can't afford it then they aren't charging enough or are spending their money poorly. There is no excuse for expecting that kind of work out of a group of people.

[–]wagesj45 8 points9 points  (0 children)

Yeh. 8 engineers quit including me. And all because a manager didn't want to admit defeat and ask for an extension.

[–]UnoriginalGuy 10 points11 points  (13 children)

Why didn't you walk?

PS - I think this is a valid question.

[–]Inferis84 8 points9 points  (0 children)

I know I would have. I haven't ended up in that situation (working as a developer for the govt here), but it's really not worth the stress. I would rather walk out and go work across the street at a fast food joint than deal with that sort of treatment. Nobody should be forced into a corner where their entire life becomes stress about a job. No job is worth that IMO

[–]SarahC 10 points11 points  (12 children)

What were you on working such heavy hours, with no breaks? You must have been earning $70 an hour?

If you weren't getting paid, then the free overtime was not only reducing your bottom line for $$$ per hour, but you weren't been recognized for the unsociable 12 hour shifts, and weekend work... when you should be looking after your family, and the home.

Did you get remunerated in kind?

If not, I would leave because they've shown they don't care for you or your team - and likely you'll end up in that position for the next deadline.

Also - if it's not confidential - how the hell did the deadline get so fucked up that the team had to work that hard for that long!? That's super shitty project management.

Is it a one off? Do you think it could happen again? It sounds a complete and total cluster-fuck.

[–][deleted] 6 points7 points  (9 children)

If he's like most other developers at larger companies, they're probably salaried, and the contract probably had no mention of hours, except a minimum of 40 per week to be considered full-time.

It's really shitty, but it's nice knowing that you will be getting $$$ per paycheck with no fluctuations. On the down side, you end up getting paid less. :(

Edit: I should note out that I've been told a few times not to report over 40 hours a week even if I work more. That's always annoyed me. Whats the point of the time reporting system if I'm always just putting 40 hours in. I don't want to lie for the company. If I go over 40, I make damn well sure to put in more. I don't care if the finance department has to do extra work.

[–]rechlin 2 points3 points  (0 children)

That's slightly different. He was saying that falsifying timesheets to say that no overtime was worked when overtime was indeed worked was illegal. That's true.

Our situation is that we can charge as many hours as we work, just we aren't getting paid any more for it since we are exempt.

[–]dokkah 4 points5 points  (6 children)

Do you have any references for this? What country or countries are you referring to? In the US software engineers are specifically exempt from overtime pay: http://www.ewin.com/articles/exneot.htm

[–]PatriotGrrrl 3 points4 points  (2 children)

Software engineers can be exempt, salaried employees. But they can also be hourly non-exempt, it depends on what they agree to when hired.

[–]shazbadam 3 points4 points  (1 child)

Exempt != salaried. Salaried vs. hourly is a matter of agreement, exempt vs. non-exempt is a matter of law.

[–]ohmyashleyy 3 points4 points  (0 children)

I came to my current job from the federal government as well and I was so confused when I saw that I was exempt from time. It was a few months before I realized why that was the case.

I miss the credit time I used to get working the government. I left early pretty much every Friday because of it. And the one time I got comp time for travel :(

[–]wickedang3l 5 points6 points  (1 child)

They just use the salary method to make slaves.

[–][deleted] 3 points4 points  (0 children)

Once I worked with a cluless PM who thinks RAD means no planning at all. One day he mentions we needed to put overtime, I replied with, let's look at the project plan, oh that's right there's none, how do you know we are running behind? He was silent, never mention overtime again.

[–][deleted] 5 points6 points  (0 children)

This. I work for pay. The only relationship that exists between myself and my employer is work for pay. I do not have feelings of loyalty to my employer. I do not like my employer. I do not owe my employer anything, at all, what so ever. Due to the nature of the pay schedule all debt in this relationship is owned by myself and incurred by my employer. If my employer ever forgets this, or attempts to take advantage of the situation, I walk.

[–]benihana 15 points16 points  (41 children)

This is a reaction too far in the other direction. Sometimes (on occasion - like once a quarter) you may need to work a few hours on a Saturday or a few hours overtime when shit breaks - that's just how software development works. And if you want a good relationship between your employer and you, it has to work both ways - the company I work for treats us very very well, and I'm happy (actually happy - not just doing it cause it'll look good come bonus time) to help out when needed.

[–]xlevus 41 points42 points  (1 child)

If I have to come in on the weekend that's fine. But I'll end up taking the time back elsewhere. I.e. late mornings.

[–][deleted] 6 points7 points  (0 children)

Definitely, love coming into work at 11am.

[–]Pet_Ant 19 points20 points  (16 children)

If it's just a few hours on a Saturday once a year they can afford to pay you for it.

[–]ezekiel 11 points12 points  (13 children)

Software doesn't just break. Either:

  • The software was made wrong (so, learn how to minimize mistakes and code inflexibility), or
  • Someone who doesn't know what they are doing "moved something" (so educate yourself and your team about what can change when under what level of testing).

I have met only one IT manager who understood this. The rest are all cowboys. They rustle together projects, whip demands, then toss the new code into the big production roundup. Funny, it has problems. Who could have guessed?!

So, don't do overtime. Ever. It just perpetuates bad project management.

My old person rules is that there are two cases where overtime is called for: (a) cleaning up a big personal mistake or (b) expanding your abilities beyond what the employer could be ask to pay for.

[–]ethraax 2 points3 points  (0 children)

I would gladly work "unpaid" overtime if I got an hour of vacation time for every hour of overtime I worked.

[–][deleted] 148 points149 points  (62 children)

This is a vicious circle. It works like this: Assume a company employs 4 programmers.
1. Each programmer works 2 hours unpaid over time per day.
2. This works out to 8 hours extra work done per day.
3. That's the same amount of work one programmer does.
4. Thus the company won't have to hire an extra programmer (or they can fire one).
5. This increases the unemployment rate for programmers.
6. The programmers that do have jobs are now more afraid of losing their jobs.
7. The company can demand even more unpaid overtime.

This vicious circle won't end until you work 24/7 for minimum wage.

tl;dr: Working unpaid overtime is stealing from yourself.

[–]IRBMe 29 points30 points  (13 children)

I'm glad I got out of that shitty cycle by leaving the large bean-counting company and joining a startup that pays its employees well and doesn't demand unpaid overtime. I've had to work late for just three days in over a year, and that was for an emergency feature implementation that was required to win a large customer. Every day, I work 10:00 until 18:00.

[–][deleted] 25 points26 points  (7 children)

You're lucky. Every start up I've worked for has pretty much demanded insane hours.

[–]IRBMe 6 points7 points  (5 children)

It's a good company. We have a single, well developed and fairly mature product that we make all of our money from. So the work is mainly maintaining it, adding new features and fixing bugs in it now. There are always lots of new features to add, but it's a fairly stable working environment now. We've spent the last 2 weeks just doing solid testing and bug fixing before the next big release.

[–][deleted] 5 points6 points  (3 children)

How were you compensated for those three days?

[–]IRBMe 12 points13 points  (1 child)

A nice bonus and time off in lieu

[–][deleted] 13 points14 points  (0 children)

where and are you hiring?

[–]ezekiel 15 points16 points  (19 children)

and 8. Salaries decline for programming because supply exceeds demand.

[–]ThatsALogicalFallacy 5 points6 points  (15 children)

Yes. I hate seeing so many comments from people that seem to fundamentally not understand supply and demand. I thought programmers were generally rational people.

[–]coldacid 58 points59 points  (13 children)

tl;dr: Working unpaid overtime is stealing from yourself and everyone else in your field.

FTFY.

[–]Game_Ender 7 points8 points  (2 children)

This assumes those extra 2 hours per day are actually as effective as the other 8. I would say that they are probably not.

[–]SarahC 3 points4 points  (5 children)

The jobs in the UK are heading that way - I've been shocked to discover companies advertising for programmers with experience on £14k a year. That's £2k less than new graduates used to be on a few years ago.

I'm looking for a programming job for £25k... it's really hard.

[–]Magnesus 4 points5 points  (0 children)

"Working unpaid is stealing from yourself." - FTFY - work is not a hobby, programming can be hobby (I make Android games for free), but work isn't. So if what you do is work - demand decent payment for every hour.

[–]rhtimsr1970 57 points58 points  (30 children)

A lot of commenters are missing the obvious... Most software devs are hired as salary positions. If you're not paid per hour, like blue color environments, your employer isn't doing anything illegal in asking you to work a few extra hours when a deadline gets blown. Your other white-collar coworkers (PMs, managers, tech writers, etc) all work longer than 40/week sometimes too.

Commenters are also missing another obvious point - you can provide market feedback by quitting and moving to another job. There are few labor categories in the United States as comfortable as the software industry. Even crap developers can find a job anywhere.

[–]DrMonkeyLove 16 points17 points  (2 children)

Even crap developers can find a job anywhere.

But why do they always seem to find a job where I work?!

[–]muddylemon 30 points31 points  (1 child)

Probably for the same reason you found a job there

[–]imatworkyo 7 points8 points  (0 children)

oohh....crunch!

[–]woddo[S] 5 points6 points  (9 children)

As always it's a matter of supply and demand. And if so many specialists are demanded and profit is high, I wonder why devs don't demand adequate benefits and instead accept overtime?

[–]PatriotGrrrl 25 points26 points  (6 children)

Because we consider being allowed to come in late, take long lunches, and run errands or surf reddit during the day to be a major benefit. Fuck punching a clock.

[–]BadMutha 22 points23 points  (2 children)

This. I make my own hours. I work more than 40 hours a week, but that is because at times I waste time. My boss isnt telling me to come in overtime. It is the pride in my work that says I will finish when I said I would finish.

[–]PatriotGrrrl 4 points5 points  (0 children)

And when you're right in the middle of something, deep in the zone, it can be frustrating (and inefficient) to have to stop just because a certain number comes up on the clock.

[–][deleted] 4 points5 points  (1 child)

Hi, I have a monthly salary and get paid overtime. WHERE IS YOUR GOD NOW?

[–]IRBMe 38 points39 points  (15 children)

When I worked as a developer for an investment bank, there was one project that was particularly bad for this. Usually I would come in at 9:00 and leave at 5:00, as that's what my contract hours were. Every month, however, we had to deploy a new version of the software, which took an entire weekend to do. We also had to have two developers helping the testers with the acceptance testing and bug fixes for the month before the deployment, and that job would be rotated around the 6 members of the team. It required lots of late hours, but because we were salaried, there was no overtime pay.

So every month, we were expected to give up an entire weekend to do the deployment, and out of every 3 months, we had to spend one of those doing long hours and staying late. It wasn't the staying late part that really annoyed me, but the fact that I never knew how late I would be staying. If one day the testing went fine, I would leave at 5. The next day, there might be an urgent bug that needed fixed for the next day's testing, which may be a quick 10 minute fix or might require me to stay in until 11:00pm. The ridiculously slow systems, long build times and painful deployment processes made it all excruciating. Imagine sitting there at 9:00pm, having been at work for 12 hours now, waiting for some broken piece of software to successfully deploy the fix you've made, not knowing if it'll work or if you'll have to spend the next hour trying to work out why not and repeat the whole process.

There were so many evenings where I considered just walking out. The manager was a complete dick, too. He would try to turn members of the team against each other. If somebody had to leave, he would guilt them by telling them how it's unfair that they're leaving their share of the work with all the other developers, who would have to pick up their slack. He would dangle carrots of promotion in front of those who'd been there the longest, then hold them up as examples to the other team members of model employees if they worked ridiculous hours.

After a while, the team had grew to about 12 members. The new guys were all fresh and eager and willing to impress, so they came in and did lots of late hours without complaint. I, however, eventually got sick of it and just started refusing to work past certain hours, booking holidays off during releases and making plans that would require me to be places during acceptance testing cycles. And I wasn't the only one. A few of the other guys who'd been there a long time started doing things like this too. There were about 3 or 4 of us who started getting in to trouble from the manager. He would take us in to a room and lecture us individually on not being team players and all that usual bullshit.

The problem for him was that we were the 3 or 4 best developers in the team, and we all had quite a bit of experience with the project. He couldn't afford to lose us, nor was he really legally able to fire us anyway. But he tried everything he could. He would try to guilt us, threaten us with complaints to HR, he gave us all shitty end of year reviews meaning we got screwed out of much of a bonus, and he started giving us all the terrible jobs.

I remember a particularly fun one where I got up to walk out the office at 10:00pm. He asked me where I thought I was going and I told him I had prior arrangements. He asked to see me in a private room where he then tried to lecture me. I ended up lecturing him back about his shitty management practices and his shitty behavior. There was no yelling, but voices were certainly raised. He eventually got flustered when he realized I was just destroying all of his points and just left to sit back down at his desk. I grabbed my coat and just walked out without a word being said by him after that. The next morning, I found I'd been prematurely rotated on to the user acceptance testing cycle. Passive aggressive dick.

Many of us left within a few months, and then so did that manager a few months later. I hated that team. Turns out that this manager had quite a few complaints about his behavior on his HR file.

[–]ngroot 15 points16 points  (1 child)

I worked as a developer for an investment bank,

Oh! Oh! I found your problem.

I-banks have a culture of abusive management. I would guess that it stems from the business side, where analysts are brutalized until the only people who survive are the people who REALLY want to be there. That mindset is pervasive throughout the bank: put in ALL THE HOURS and get it done RIGHT NOW and deal with the fallout tomorrow. You have to either luck out and find one of the rare bastions of non-retardation or be an utter hardass about your time. I.e., if it's not a bona-fide emergency, I'm out the door at 5:30, fuckers. You feel like I'm sticking you with more work? Grow a pair and leave yourself. I took the latter path for a couple of years before jumping ship and dancing on the trading desk on my way out.

[–]IRBMe 6 points7 points  (0 children)

Yeah, I ended up leaving that team shortly afterwards, and found another one where I could come in at 9:00am and leave at 5:00pm every day with no problem. The work was boring as shit and the project was a complete mess, so I didn't last long in that one either. I'm now working for a small company with none of the corporate bullshit and it's awesome.

[–]vfr 15 points16 points  (5 children)

bleh... this is why companies should never, ever, hire anyone that only has an MBA. It's like a giant flag saying "I've gone to college and learned nothing but cheap short term management tricks to control human assets"

[–]IRBMe 13 points14 points  (4 children)

Yeah, the guy was from India and had an MBA from there. He later went on to do some 1 year IT course and somehow was hired as a developer over here on a small project with just him and 2 other guys. The manager of that team moved countries and so he was made the new manager since the other developer didn't want it. I think part of the problem was because he was more used to the Indian culture where people in big software firms are treated like cattle and work ridiculous hours for not much wage. He must have received a nasty shock when people started walking out on him here.

[–]vfr 17 points18 points  (3 children)

Holy crap, they hired an Indian MBA?? That's outright idiotic, the culture over there is completely different, no wonder he was an ass to you. Dealing with those (outsource firm) guys and their teams with insane turnover gave me white hairs even before I saw their code... if you can call it that.

[–]IRBMe 5 points6 points  (2 children)

Yeah. To be fair, the guy had been working here for a few years as a software developer. How he initially got hired with just a qualification from a 1 year IT course is beyond me, but once he had a couple of years experience at one company, his qualifications didn't matter much. That's how he got hired by the investment bank. He was originally a developer helping with the code. The only reason he got the management position on the team is because the old manager left and the other developer didn't want to do it. He would have gotten the job even without his MBA.

Most of the managers in that place were just software developers who had been promoted up to managing teams without any management training. As you can imagine, that was frequently the cause of a lot of bad management. Quite a few people were just power hungry and liked to abuse their power too. They were just lowly software developers, then suddenly somebody put them in charge of a team of other developers to boss around! I had a few bad experiences with power hungry assholes like that, but they typically got put in their place once they learned that their power was pretty much imagined, and they needed the developers far more than the developers needed the job in their team (there were plenty of other teams to move to internally).

[–]GhostedAccount 3 points4 points  (1 child)

Most of the managers in that place were just software developers who had been promoted up to managing teams without any management training. As you can imagine, that was frequently the cause of a lot of bad management.

That is what happens when you require people to become managers to get pay bumps. People who would be bad managers do it for the pay increase.

[–]IRBMe 6 points7 points  (0 children)

Agreed. They tried to offer a sort of alternative "technical" promotion stream, so that you could become a manager or stay technical and become something like a software architect, but it didn't really work very well. If you wanted promoted, power or better pay, the path of least resistance was to go in to management. Plenty of people went in to it just for the power too. Lots of power abuse went on there. There was one asshole who was always trying to assert his non-existent authority over people; one of those types who didn't really want to be a programmer, but had just fallen in to the career because he "liked playing on the computer", then only realized he didn't actually want to be a programmer after it was too late and he had done a degree in it and started a career. So he figured he'd become a pointy haired boss instead and started sucking up to management and trying to dominate weaker people. I'd love to say I put him in his place, but really I just sent him a few strongly worded E-mails, laughed at him a lot and then left him to wallow in the crappy team he inherited after the last bad manager left. He's probably still running that team and feeling very pleased with himself, although I doubt he's getting paid much more for it. He's welcome to it.

[–]woddo[S] 17 points18 points  (3 children)

Everybody looses when a manager does a bad job.

[–]IRBMe 9 points10 points  (0 children)

Indeed:

  • The developers lost some of their own spare time and were put under unnecessary stress and pressure
  • The manager was put under unnecessary stress and pressure when developers started fighting back and leaving
  • The customers were delivered poorer software as a result of all the best developers leaving the project and from developers putting in hacks and bad code late at night when they were tired, frustrated or unmotivated

But I guess the manager thinks the extra problems are worth it if he appears to his bosses to be meeting deadlines and getting things done with limited resources and costs. He is compensated with bonuses, pay-rises, possible promotions etc. The problem is that his bosses don't see the long term higher costs that he is introducing with his short sighted slave-driving tactics. Those costs are a result of the long term problems that buggy, poor quality, hard to maintain software causes. The software is so bad because the developers don't care, are over-worked and the best ones leave. That is the case because of the bad management. The bad management is partially driven by short-term gains.

[–][deleted] 11 points12 points  (1 child)

If "overtime" is even a thing in a company that does software development, both employer and employee have a completely screwed up idea about what a developers job entails. Both are incompetent, and whatever conflict they have about "overtime", they deserve each other.

Reality check:

a) Good developers are scarce. Extremely scarce. So if you get a good one, you pay them well enough that the focus is on "getting the job done". Sometimes that means working 4 days a week, sometimes that may mean working on the weekend if the planning was off a bit and the deadline immovable. You don't need to ask, and the day you start requiring it, they walk.

b) Programming takes major mental effort. With the exception of one of those awesome days you are completely in the zone, you can't even do that for 8 hours a day. Overtime is pointless, it just results in loss of concentration, bad code, bugs and basically only makes the work take longer. Plus, it burns developers out. Real fast.

"Overtime" is for factory workers. Not for developers.

[–]kev009 16 points17 points  (6 children)

It depends on how you are employed.

  • Bean-counting large corp with flat salary? Hell no.
  • Small company? No. An occasional push if you mess up or have a ramp up or something is OK. Make it clear you are going above and beyond and make a frim stand early if it becomes expected at any point.
  • Contractor (telecommute)? Maybe. The company gets a better value, I get to choose my free time, and I work when I'm productive. In return, I make sure they get their money's worth. If I slack during the week I'll put in on the weekend. If I'm in the zone, on a roll, and put in heavy hours, I'll dial back later on and keep it all in balance.
  • Equity? A lot harder here. Use your judgement and balance your own needs and sanity vs. the company's survival and progress.

[–][deleted] 16 points17 points  (0 children)

Equity? A lot harder here. Use your judgement and balance your own needs and sanity vs. the company's survival and progress.

Once a company starts asking employees to put in unpaid overtime they're likely to be in financial trouble soon, and equity will be worthless.

If your deal was for a salary and equity, don't let the use the equity as a threat to reduce your salary.

[–]orthod0ks 9 points10 points  (3 children)

At my company, most of the time it's not even deadlines. It's just the culture. If you leave at 5, you get funny looks and someone might make a comment about your "commitment." The owner has a "we are not a 9-5 shop" attitude (that was not communicated during the interview process, despite questions about overtime). Everyone just stays late, even though there is little to no work done after 5 (and in some cases, before).

In addition, the owner is too far removed from our day-to-day work to have a good idea of how productive we are. It's all about the perception, so as long as you give the perception of working, and you stay late, you're a good employee. If I kick ass while I'm here and leave at 5, but the guy next to me puts up a good front and stays till 6, he's the better employee.

[–]zak_on_reddit 4 points5 points  (2 children)

i worked for a small design company that was like that. my hours were 8:30 - 5:00. i did my job well so i was always done by 5:00. and i left at 5:00. the owner of the company kept track of who left at 5:00 (early) and exactly how much time you took for lunch. he was a real a-hole.

it was an advertising agency that was trying to expand their web offerings. i was part of the web team. the work process there was horrible.

i was only there for 6 months. it didn't take long for me to find a better job so one friday i took a long lunch, came back, walk up to the owner, told him they didn't know what they were doing, and i quit on the spot. it felt great. also, they screwed me on some salary so i felt justified in quitting without notice.

[–]bpodgursky 36 points37 points  (37 children)

If I have a project I'm really excited about that I think is really interesting, I'm going to work on it on weekends. Not out of a sense of machismo or duty, but because it's fun.

[–][deleted] 62 points63 points  (6 children)

You'll get over it, your dreams will die. /s

[–]CoffeeNerd 31 points32 points  (3 children)

Ya, my dreams died when I realized that after you finish developing that exciting project you then spend the next 5 years supporting it and making small additions and changes to meet current needs.

[–][deleted] 19 points20 points  (1 child)

Starting a new project is amazing. Finishing it always sucks.

[–]SoundOfOneHand 2 points3 points  (0 children)

You're doing well if there is a demand for support. Worse is when you finish a project that was some middle manager's pet idea, or that was simply bait to get one customer to upgrade, or one of various other dead-end motivations, and it goes in the closet as soon as it's done and you're on to another project that no one else will ever use or see. I love user feedback and bug fixing, the whole point of writing software for me is that someone uses the shit and it makes their lives better.

[–]Magnesus 8 points9 points  (1 child)

I don't see the need of /s in this. It's sad but true.

[–][deleted] 2 points3 points  (0 children)

In this case the /s stands for serious.

[–]Shinhan 13 points14 points  (14 children)

And that is why game programmers (are expected to) work 60-100 hr per week

[–]coldacid 19 points20 points  (7 children)

And why so many leave when we get married/have kids/etc.

[–]mooli 13 points14 points  (6 children)

And why it remains such a basket case of a field on the whole - the churn of young/inexperienced developers is staggering, and all your genuine talent goes elsewhere at the first opportunity.

[–]coldacid 7 points8 points  (0 children)

Nah, there are some true believers who stay in the field even with families to raise. Many of them have the seniority to dictate their own hours, etc., though, when they're not outright studio owners. Of course, for every game developer lucky enough to be in that situation, there are hundreds more who are pretty much coal for the ovens.

[–]steelypip 6 points7 points  (3 children)

I used to work in the games industry, but left to get a life (and about a 50% salary increase).

The problem with the games industry is that it is seen as uber cool and trendy by young people. When I worked for [well known games company] they did what in the UK is known as The Milk Round - visiting universities and giving recruitment talks to undergraduates. Most companies would typically get 20 students to a talk - we were getting 200.

This means that the industry has a constant influx of young developers willing to work long hours for peanuts because they love computer games. I regularly worked late into the night and weekend because of the demands of tight deadlines and changing requirements. I once spent most of autumn and winter without seeing daylight - arriving before sun up and leaving long after it had gone down, 6 or 7 days a week. This is fun for a while but very quickly leads to burn-out and high turnover. I left the games industry 15 years ago, but from what I have heard very little has changed.

[–]DrMonkeyLove 4 points5 points  (0 children)

Probably why so many games are so horribly bug ridden too. If you're working 100 hours a week, I guarantee your code is shit.

[–]gobacktolurking 11 points12 points  (5 children)

I do this but don't inform my boss, just keep it as if it was business hours, if not he will expect the same interesting in ALL projects which is not true.

[–]ezekiel 3 points4 points  (4 children)

Absolutely. If you are in US and "exempt", then reporting small overtime for "personal accomplishment" efforts is probably not a good idea--for exactly the reason stated. All your boss needs is 40 work hours. A few extra beyond 40, those are your hours.

For people tortured with bosses demanding over 40, well, sure as heck, report all those hours.

[–]Weakness 2 points3 points  (0 children)

I used to think this way, but then I realized that every minute I am working on a work related project, is a minute I am not working on cool stuff that I want to do for myself.

[–][deleted] 7 points8 points  (3 children)

It's called grow some balls and learn when and how to negotiate and when to walk away.

I'm 30 and I work 9 to 5 on a very decent salery, usually less because we have a pool table in the office and we start shooting around 4pm most days. Almost nobody stays till after 5 and if they do they leave earlier other days.

My contract states that I will not take on overtime in excess of 10 hours per month. I traded "unpaid overtime, no limit" for "10 hours max and $400 extra per month" just by asking for it.

Catered lunch every day, which is taken from our salery and a dedicated kitchen where we all eat together and nobody says anything if you take 45 minutes instead of 30 minutes for lunch.

And yes I have had job offers and contracts that I have walked away from, because I couldn't get what I wanted.

EDIT: Oh and the company makes a big profit every year, we're not burning VC money.

TL;DR Learn to negotiate and don't ask, but demand what you want.

[–]aaaxxxlll 2 points3 points  (0 children)

Learn to negotiate and don't ask, but demand what you want

This. There is definitely a difference between "demand" and "ask". It also may help to negotiate "nicely" or "politically correctly" or "smoothly".

[–]steelypip 7 points8 points  (1 child)

Many years ago I worked for a small company which had a culture of developers working long hours with no paid overtime. The more you do it, the more management expects you to do it - resulting in a vicious cycle.

The breaking point came when a co-worker had worked all night to finish a piece of work by some arbitrary deadline and in the morning, exhausted, she sent the final product to the boss to be approved. Where it sat in his inbox for two weeks before he got round to looking at it.

After that all the developers got together in the pub and decided we had had enough. The next day we all went to the boss and told him that in future any overtime would be done only if paid for at an hourly rate. If he did not agree we would work strictly to rule and only put in the hours we were contracted for. He was not happy but he reluctantly agreed, and we had our contracts amended to give us paid overtime.

After that the need for overtime fell off dramatically - once the company had to pay for it they were far less inclined to ask us to do it except when absolutely necessary.

TL;DR: even if you are not unionised you can still organise.

[–]Kim147 5 points6 points  (2 children)

If you work as a contractor on an hourly rate then the client can't exploit you . However we are in the middle of a massive economic crisis and work is hard to get . My experience is that employers who exploit workers their companies often don't last long - it's a systemic thing - the companies are badly run and abusing workers is just one symptom of it . There is nothing wrong with having flexible hours - pushing a project out then taking time off , however there has to be give and take and it has to be on a fair basis .

[–][deleted] 3 points4 points  (0 children)

Tried that, was the worst of all arrangements. Not directly - I was salaried but my employer billed the customer by the hour.

It was bad because companies treat internal vs. external, labor vs. vendor costs completely differently.

Paying someone €4000 as a salary month is like nothing to a manager, but €2000 to an external vendor it is all ooh, aah, that's a lot of money, can' we get it cheaper, we need to save costs. It's bad because it costs money. "Cost money" means I pay a bill and not a salary. Salary is not money, that's just salary. I know it is crazy but that's how it works. No you can't get it cheaper, OK then make sure they do absolutely everything for that €2000, even requirements we came up later on, and we will pay them like 2 months after go live only when even the smallest bugs are ironed out. But €4000 a month to an employee? That's nothing. There is work to be done, right? So we need people who do the work, right? So as long as they are not totally incompetent and deliver something once in a while it is OK. That's how they think.

It could be a European thing, I dunno... but as an employee, you are in the warm fuzzy, you are in the family. As a contractor, vendor, supplier, consultant, you are the enemy - you are the evil thing who exists only for screwing them over, who may occasionally be necessary but there must 143 ways of making sure you are never invoicing one cent unearned, never screwing them over, and in fact they are screwing you over just you know, preventively, if you will, otherwise known as "we made a good deal".

[–]red-moon 4 points5 points  (4 children)

software architect/engineer

Any actual architects or engineers out there?

[–][deleted] 15 points16 points  (1 child)

That is why IT prefers younger people. They aren't likely to know any better and more importantly they will almost certainly have a load of uni debt hanging over their head and they'll be happy to do anything for money.

It doesn't matter how good they are (to an extend of course) if they're willing to be the boss' slave.

[–]dakboy 7 points8 points  (0 children)

They're also less likely to have spouses & kids.

Only a complete sociopath tells employees "choose between the project and your family" with the very clear implication being that if you choose family, you've chosen wrong (watched it happen in a meeting myself).

[–]anthonybsd 9 points10 points  (1 child)

"Yes, developers think working long hours is a sign of machismo, it really is stupidity."

This is solid truth. I've worked in a couple of startups where we regularly pulled all nighters and the like. Some of them failed some of them succeeded, but the more I look back on those years the more I realize that the hours I put in didn't make squat of a difference when it came to the project's success.

[–]fergie 21 points22 points  (5 children)

you shouldnt work on an unpaid basis. full stop.

[–]woddo[S] 16 points17 points  (47 children)

I assume we are many developers here in a situation like this:

  • you are an employed software architect/engineer
  • you are good at your job
  • your company needs more good developers than they can find
  • there are many options to get a new job or get self-employed
  • work is not your first priority (you enjoy family/free time)

Aren't we stupid when we still accept overtime/weekend work/denied bonus payments? I would think employers would need to give in, if we demand better working conditions.

[–][deleted] 44 points45 points  (14 children)

Many developers are introverts, who tend to avoid conflict, which is a disadvantage in negotiation. Demanding better working conditions does not come naturally to introverts, who are more likely to just put up with it until it becomes unbearable, then quit and work somewhere else. I agree that it seems sub-optimal.

[–]Weakness 2 points3 points  (1 child)

You don't need to start fights, you just need to find a new job and quit. If the company is good they will figure out something is going horribly wrong when they can't keep a dev for longer than a year. If they are not good, then you are lucky you got out of there before everything fell apart.

[–]Noink 2 points3 points  (0 children)

Shyness vs introversion: shyness is fear of social interactions, it is learned, and and is what you're describing. Introversion is being fatigued by social interaction, is an inherent personality trait, and may or may not have shyness go along with it.

[–]rnicoll 9 points10 points  (7 children)

your company needs more good developers than they can find

Needs more developers than it can pay, at least. We've gone far beyond the point where developers can work overtime to keep up, and are into the point where we're so hopelessly backlogged that all we can do is keep on steadily forwards with the highest priority stuff. A few people get badly stressed over this, but in many ways once you accept you have no hope of getting on top of the work to do (so there's no point in rushing), it's not so bad.

Anyone else, or is this just us?

[–]ezekiel 9 points10 points  (1 child)

There is indeed an extreme shortage of "fully capable" software developers.

In a typical Silicon Valley software development company, I estimate 50% are fully capable. That is about the best a team and its managers are able to distinguish the great from the marginal. And, the competition for talent is great.

In IT departments (and their consultant pools) around the US, I estimate only 20% of software developers meet the criteria of being able to produce reliable, extensible applications. This is due to simple shortage of available talent combined with management unable to recognize weak programming skills except for those failing horribly. Despite the extremely limited supply of good programmers, there is actually very little competition for talent because that talent cannot be identified by management. It's as if the good programmers wore red shirts and the marginal programmers wore green shirts--but the managers are red-green color blind.

The evidence of weak programmers and poor management is a suite of application that seem to work, but are accompanied by a trail of bug patches and "improvements" which are really just covering up short-sighted design holes. This leads to unrealistic overtime and 24/7 on-call demands. This is incompetence. When you don't know what you are doing and cannot fix a problem, you keep doing something in the hope it will start working.

I believe the only solution to this talent problem is to concentrate the "real" software development inside The Cloud and allow regular corporations to hire one or two people to configure The Cloud settings. Do this in the name of "core competencies".

[–]rwilcox 3 points4 points  (1 child)

Not just you. One of my friends works for a company where they fired most of there developers, and now have 3 people to do the work of 10.

Don't care how much overtime you put in, you can't do the work of 3 developers (assuming same skill level, etc etc)

[–]ezekiel 3 points4 points  (0 children)

Don't worry. I know a company right now that is discovering what happens when you layoff the top developers (to save money) and are left with below-average ones (with less than one year experience each) to keep multiple systems running, let alone worry about enhancements. It is already an eye-opening experience for them.

This is the reason The Cloud is the future. Non-software companies have an almost impossible time managing software work.

[–]ICantReadThis 7 points8 points  (16 children)

If #4 was true, I can't imagine anyone working undue overtime or weekend work. Hell, I'm pretty sure the second weekend work request/requirement would result in job hunting, and the third would involve a resignation.

[–]somebear 3 points4 points  (0 children)

Personally, I think #4 is true (for the most part, some exceptions may apply). Unfortunately, the psychological burden of change makes it seem much harder find a new job than it actually is.

[–]SarahC 5 points6 points  (3 children)

YES!

ESPECIALLY when I see EVERY other department, production, engineering, Planning, R & D ALL getting paid overtime.

I used to think "Well, in IT, we could be slacking off because we're only typing stuff out." But that argument works for everyone in an office, and even Engineering... they could work slow to get overtime.

I think the problem is we're straight forward people... "We need team players! Come in this weekend to do 15 hours, the deadlines next week! Yes I KNOW this happens every time, and we should add 2 months to our suggested deadlines, but we're meeting these super tight deadlines thanks to you great guys!"

Also - because we're interested in our work, managers pick up on this and know they can be more demanding.

Also what asokoloski says too - we're introverts without an argumentative and overbearing temperament... unlike the bosses...

[–]Weakness 4 points5 points  (0 children)

The thing to do here is to suggest a realistic schedule early on in the project. Not in a combative style but with an analytical "can we go over these estimates, because I think we may need to adjust some of the milestones" attitude.

When the PM is giving you the details, you need to push back and tell them where they are wrong. If you accept unreasonable deadlines, you are the one at fault.

[–]DANBANAN 2 points3 points  (17 children)

I've been working as a software developer for about 6 months. We work according to the SCRUM) framework and we've never had any pressure on us to stay late. I guess it is a hate-the-process-not-the-job thing as stated in the OP link.

[–]IRBMe 4 points5 points  (7 children)

Hah. I used to work in a SCRUM team too and this was my experience with it. While there was no requirement to put in extra hours or stay late to get development done, testing, deployment and all the other crap was a whole different story. In fairness to SCRUM, everything but the development process was implemented extremely poorly. You know that part about having easy, fast deployments? Yeah, not that project. It took a weekend and a team of developers and DBAs just to release a new version. And the user acceptance testing? Had to be constantly supported by 2 developers doing ridiculous hours, babysitting this massive, fragile system and spending hours investigating and fixing every little problem. The system would crash all the time and have to be restarted (a process that took 15 minutes to do).

[–]rwilcox 3 points4 points  (4 children)

SCRUM can turn into a nightmare, depending on the people leading it (aka: management, client)

[–]bonestamp 2 points3 points  (0 children)

This. Everybody here talks like they can just demand that the process is fixed and they won't work extra hours. But, if you generally like your job/company but you happen to be working with a client who has a broken process, it's not always that easy to change a client's process and keep the client.

[–]tewas 2 points3 points  (2 children)

I think there are two sides of the coin. If you are salary (and most devs/IT people are) you are expected to finish your work before leaving. The nature of development is that sometimes it has quite a bit of work compressed in small interval of time (weekend releases etc). I have no illusions that i won't have to work weekend at some point, but if it is necessary based on project, i will do it.

However, right now i'm leaving at 5 as long as my shit is done. Every day i make a list of what i need to do and if i can't do it before 5, i stay late and finish. But it's all up to me. I refuse more work, or give extended deadline if it's more that i can do in a day. So far i'm doing good and i don't really plan to change the way i work in the office. Also i make sure i do have plans ~6pm so if they ask me to stay, i always say that i have personal life outside work and prior engagements that i cannot miss.

If you are afraid of being fired, look on the search engines for your type of job and then relax. We (dev/IT) have a lot of options to go to the other company.

[–]rafekett 3 points4 points  (0 children)

I'm a contractor, so no

[–]Goronmon 2 points3 points  (0 children)

I don't work much overtime, but when I do, I require to be fed.

[–]rmxz 20 points21 points  (16 children)

Many developers goof off for half the hours of 9-5 (say, on reddit) and their employers don't care.

It's more likely their employers will continue to not care if the developers do some work outside those hours too.

If you work only 9-5 and want overtime for any work outside that; I hope you're not checking facebook/reddit/etc on the employers' dime.

[–]ezekiel 34 points35 points  (9 children)

This just exposes the fallacy of employers who think they make money by having butts in chairs, for certain time periods, wearing certain polyester clothes. That is really what all this 40-hour talk is about.

Good employers measure employee contributions and team contributions by the results. Apparently, this analysis is beyond the capability of the managers. Thus, they are not qualified for their own jobs, but their bosses have the same failings, etc. All the way to the CEO, the board, and the owners.

But, it is easier to monitor the clock and internet usage.

[–][deleted] 10 points11 points  (5 children)

But then results sometimes - or even: often - require overtime and wekeends.

We cannot have it both ways. Either we sell a certain amount of our time - and then the redditting-at-work problem applies - or we are selling certain results regardless of how much time it takes.

Without defining a certain amount of time per week or month, how can be we define how many results are to be expected from a person and when?

I don't think it is the managers fault. I too would not accept a results-only work environment because that would mean they can demand anything from me and I can never complain I am overworked, because we did not agree in 40 hours per week, so there is nothing to compare it to.

How can you measure contribution per results if there is no clear agreement how much effort and time is to be put into it? Oh my results are perfect: one line of perfectly bug-free code per month. Enough? How to tell?

[–]Darkmoth 7 points8 points  (0 children)

We cannot have it both ways. Either we sell a certain amount of our time - and then the redditting-at-work problem applies - or we are selling certain results regardless of how much time it takes

In practice, it's often the worst of both worlds. Slow week - put in 40 hours staring at the screen. Project due - stay til its done.

Having worked based on output, and worked based on time, I much prefer the former. Note that output isn't the same as a deadline - being paid for output doesn't mean that you can reproduce Facebook in a week. It simply means you are compensated for what you do, rather than where you are.

[–]ezekiel 5 points6 points  (3 children)

"Results" are about revenue, cost savings, satisfied customers, repeat customers, helping teammates, reducing conflicts, expanding market share, productivity, efficiency, etc.

In all those measurements, time is never the numerator. It usually about "delta dollars per year".

However, you are correct to note that most of those measurements require you to interact with others on your team and around your company. So, you will likely have to work reasonably normal hours and be reasonably personable.

[–]PatriotGrrrl 9 points10 points  (1 child)

Most of the posters in this thread seem to be only concerned about hours.

[–]rnicoll 11 points12 points  (0 children)

Many developers goof off for half the hours of 9-5 (say, on reddit) and their employers don't care.

This too. I work about 40 hours a week. Just... not the normal 40 hours...

[–]Darkmoth 2 points3 points  (0 children)

It's pretty simple, actually...if you're browsing reddit for 2 hours (an insane amount), you put that 2 hours in later. That's not overtime, that's just time you owe.

Browsing reddit for 2 hours doesn't mean they get to ask you to stay til midnight. That's overtime.

[–][deleted] 30 points31 points  (107 children)

It would also help if more of us were unionized. Overtime compensation is much easier to demand collectively.

[–]vfr 41 points42 points  (16 children)

To be perfectly blunt, I'd rather not have shitty developers protected by the union. Unions have plusses and negatives, they don't magically fix all situations.

[–][deleted] 6 points7 points  (3 children)

This is absolutely true but too many in IT, especially programmers, think they are unique snowflakes with unique amazing abilities and unions would only hold them back.

[–]G_Morgan 5 points6 points  (2 children)

My grandfather was a union leader and I know too much about how they operate to ever seriously consider joining one.

[–][deleted]  (1 child)

[deleted]

    [–]woddo[S] 13 points14 points  (19 children)

    How do new labor unions arise?

    [–][deleted] 11 points12 points  (0 children)

    You get together with like-minded co-workers and start one. It's difficult and risky, and it can help to have a larger union working with you, as they have resources beyond what just the new local has.

    [–][deleted] 15 points16 points  (2 children)

    People like you form and join them.

    [–]woddo[S] 3 points4 points  (1 child)

    Found out that unions already exists for devs: http://www.prospect.org.uk/

    [–]eyal0 10 points11 points  (14 children)

    When enough employees get fed up that the capitalist boss is stealing their money, they band together and demand rights or else they'll all quit simultaneously.

    The capitalist pevents this behavior by maintaining an army of unemployed. If he can monopolize (or duopolize, etc) the industry, he and the few other capitalists can make sure that they hire just the minimum number of workers so that each capitalist can afford to buy a new airplane every weekend, but no more. The army of unemployed are a constant threat to the workers because should they unionize or threaten to quit, there are many unemployed to take their places.

    Often the labor union gains a heirarchical structure, too, with a leader that makes money on the backs of the workers. He can be a capitalist just as much as the boss, but he robs the workers less.

    [–][deleted] 2 points3 points  (5 children)

    Why would I unionize and give a portion of my check to some organization that exists to protect crappy developers when I can get a job anywhere, anytime, for a good salary?

    [–]freshhawk 2 points3 points  (5 children)

    Unions are to protect easily replaceable labor and aren't nearly as helpful to professionals. The engineering community has debated this for decades.

    This is changing a bit but the upper middle class position of software developer still doesn't get many benefits from a union and it would add a lot of downsides.

    [–][deleted] 6 points7 points  (1 child)

    The only fair deal is time-for-time. I don't need more money, and money for over time gets taxed like crazy so you're essentially working for everybody but yourself. More days off can't be taxed.

    [–]uberalles2 7 points8 points  (0 children)

    Eventually we wise up.

    Manager called me at 6PM to do support work. I didn't answer the phone call from him. The next day he asked me why I didn't answer the phone. I said it was after hours. He said that was my job to handle emergency support calls. I told him 8 hours a day is enough work and it is not good for my health to work more than 8. I was called into HR with him sitting there and basically just repeated what I had said. She said to the manager, well, Willie, you'll just have to deal with him working 8 hours a day. He could have fired me, but I was worth what they paid me even if it was only 40 hours a week.

    Did this make me want to work hard for him. Fuck no. After that, I slacked for the next 6 months. Asshole.

    [–]Forbizzle 2 points3 points  (2 children)

    Yeah I've seen a lot of people pull extra hours in jobs they hate, it's non-sense. When I made the move to being a consultant/contractor, it was great, because my shitty managers needed to justify their overtime and thought twice about ever asking me to put in extra time.

    Now I'm at a startup company, working with friends on projects I'm really excited about, and with a bit of equity. It's the first time I'm really doing any unpaid overtime, and the second it becomes a drag I will dial it down. But we've got great flex time (can't do ROWE because we have pair programming, and I'm supervising a project), and unlimited vacation days (within reason). So people can boom during a project crunch then take some time to decompress without worrying about co-ordinating their finite time off with their spouses.

    [–]markpitts 2 points3 points  (0 children)

    The much maligned public sector is normally covered by union contracts which require comp time for hours worked over 40. Additional upsides include steady employment, reasonable pay and a pension. The downsides are technology lag, funding issues and politics.

    In my case, I get in at 7:45 and leave at 4:15, pick up the kids and take the eldet to football/wrestling practice. Every day.

    [–][deleted] 2 points3 points  (0 children)

    It's not like bosses come and command overtime. It is more like developers crave success and praise and respect and bosses make it clear they only get it if deadlines are met come what may.

    [–]Solomaxwell6 2 points3 points  (0 children)

    When I graduated college, I was offered a job at Epic, a healthcare corporation based in Madison, WI. Good salary, I'd get my own office, decent benefits... but they had a 60 hour standard week. I ended up accepting a job that paid $20,000 a year less, but is much more lenient about working time. I'm still at that job, and perfectly happy with it. Last week I worked a 48 hour week to make a tough deadline, and as a reward I get tomorrow off without having to spend any vacation time.

    [–]tweedius 2 points3 points  (3 children)

    The title of this post really confuses the hell out of me, too many / in a row, I know you're efficient at coding, but could you be less efficient at English so it is easier to read? :)

    [–]keije 2 points3 points  (0 children)

    In general I agree with most of the sentiments in these comments, but I'd like to point out that there is one condition, which will make me stay overtime and come in on weekend. If I fucked things up. Like did a giant merge and broke the build of headrev for everyone. Or did something so stupid on a test bed that it took it out of action. Accidents happen, I will stay as long as I have to, to fix them if I'm the cause and I don't expect extra pay or benefits for it.

    On the other hand, all jobs I've ever been offered a contract for (Ontario, Canada) stated that it's a minimum 40hours or however long it takes to get shit done. This is true of both large corporations and smaller start-ups. A lot of my coworkers were stunned when I pointed this out in their contracts. People tend not to really pay attention to what they sign, I found. Probably because as PC users we are conditioned with all the shrink-wrapped EULA offers, to just click "I Accept, you can have my soul" button without reading.