Live data from Hacker News

The "Spanish Theory" of software project management

dodgycoder.net

21–30 of 53 posts

Re: The "Spanish Theory" of software project management

#21
post #16
post #12

Earlier quoted context omitted.

Except the only relation between the Spanish Flu and Spain was that Spanish newspapers were the firsts writing about it, as they weren't as censored as the ones published in countries fighting WWI.

They nap in the afternoon, they publish uncensored news .. is there anything those Spaniards are good for?

And you forgot about food and weather ;)

Re: The "Spanish Theory" of software project management

#22

I was a bignpropknent of OT for non managers since they have less control. The danger with paying managers OT is every hour they do "make work" causes the organization to spend 10 more so you don't want to invent that. OT policies encourage managers to properly staff from the start.

Your concern applies only any creative professional work where time input and work output are not clearly correlated, not just management, though.

Re: The "Spanish Theory" of software project management

#23

This meme about how unfair it is that programmers work unpaid overtime is starting to drive me nuts. I've been in big stodgy software company where everyone worked exactly 8 hours, and the whole company filed out the door at 5pm as if a factory whistle had blown. I've also worked at a smallish software company where the norm was at least 10 or 11 hours a day, and half the programmers came in on Saturdays and Sundays…

It appears that your comment has been taken the wrong way... I think what you're saying is this:

* It's more fun (for you) to work with people who like to program and ship software than it is to work with people who just program to pay their bills and would rather be anywhere else than at work.

When employees care about solving problems, they put in extra hours sometimes. Managers have the problem of making sure that team members don't burn themselves out. At these companies you see things like as much time off as you want, work what hours you want, work where you want. There's no need to make people work.

When employees don't care, they spend lots of time in the office getting coffee, checking email, IM chatting, surfing the web, having endless meetings arguing about whether or not source control is a good idea, etc. The managers there have the problem of getting the staff to do any real work at all.

For an employee who wants to work at one kind of company, it's very frustrating to work at the other kind.

Re: The "Spanish Theory" of software project management

#24
post #19

Earlier quoted context omitted.

But the OP is speaking to all software developers, and I'm offering an alternative viewpoint. > no one should be whining about unpaid overtime Do I think that I and other programmers should be paid for overtime? Yes, of course I do. I would gladly accept payment. My point is that this complaint about unpaid programmer time is becoming a recurring theme, as if it's a huge and terrible problem. What's next: programmers…

What's wrong with forming a union?

One thing wrong is that programming is not homogeneous work, and unionization works better when different employees' work are completely substitutible. Otherwise you end up in a "market for lemons" race to the bottom in work quality situation.

Re: The "Spanish Theory" of software project management

#25
post #24
post #19

Earlier quoted context omitted.

What's wrong with forming a union?

One thing wrong is that programming is not homogeneous work, and unionization works better when different employees' work are completely substitutible. Otherwise you end up in a "market for lemons" race to the bottom in work quality situation.

I'm curious...I haven't thought about this much at all and I've no experience in it, but your assertion doesn't seem obvious to me. Can you back it up with examples?

Re: The "Spanish Theory" of software project management

#26
post #23

This meme about how unfair it is that programmers work unpaid overtime is starting to drive me nuts. I've been in big stodgy software company where everyone worked exactly 8 hours, and the whole company filed out the door at 5pm as if a factory whistle had blown. I've also worked at a smallish software company where the norm was at least 10 or 11 hours a day, and half the programmers came in on Saturdays and Sundays…

It appears that your comment has been taken the wrong way... I think what you're saying is this: * It's more fun (for you) to work with people who like to program and ship software than it is to work with people who just program to pay their bills and would rather be anywhere else than at work. When employees care about solving problems, they put in extra hours sometimes. Managers have the problem of making sure that…

This describes the kind of place I want to work. Employees want to be there for crazy hours because it's such a fun environment, and employers push back to prevent burnout.

Re: The "Spanish Theory" of software project management

#27
post #17

Earlier quoted context omitted.

And also I agree to work overtime near deadlines because my employer lets me super flexible work time when there's not much work. So it's a tradeoff. Of course, if your employer doesn't compensate with something, you're getting screwed. But that's true for developers, waiters, clerks, everybody, it's not something specific of our kind.

Based on the comments and complains I heard and read online (in other words: it's only my wild theory) what it seems specific of programmers is the willingness to comply, without trying to negotiate. Maybie it's because the ideal is passionate effort instead of detached profesionalism, or maybie it's because programmers are just a 'quiet bunch'.

It's also the lack of unionization.

Re: The "Spanish Theory" of software project management

#28
post #23

This meme about how unfair it is that programmers work unpaid overtime is starting to drive me nuts. I've been in big stodgy software company where everyone worked exactly 8 hours, and the whole company filed out the door at 5pm as if a factory whistle had blown. I've also worked at a smallish software company where the norm was at least 10 or 11 hours a day, and half the programmers came in on Saturdays and Sundays…

It appears that your comment has been taken the wrong way... I think what you're saying is this: * It's more fun (for you) to work with people who like to program and ship software than it is to work with people who just program to pay their bills and would rather be anywhere else than at work. When employees care about solving problems, they put in extra hours sometimes. Managers have the problem of making sure that…

Many really good people who love to program, though, don't necessarily love to spend 100% of their time programming one thing. Lots of strong, motivated programmers work on open-source projects and other side projects in addition to their day job, and try to avoid companies where excessive crunch-time would make that impossible.

Re: The "Spanish Theory" of software project management

#29
post #24
post #19

Earlier quoted context omitted.

What's wrong with forming a union?

One thing wrong is that programming is not homogeneous work, and unionization works better when different employees' work are completely substitutible. Otherwise you end up in a "market for lemons" race to the bottom in work quality situation.

There are a number of uniform-ish things that I wouldn't mind an advocacy group handling. For example, I think as an industry we could get better terms in employment agreements, e.g. less onerous noncompetes, claims to own out-of-work IP, and no-contact rules, if employers had to negotiate with a union over those things, instead of every individual employee having to fight an uphill battle to strike out lines in the agreement.

Although an alternative, seen in California, is to bargain at the really collective level and deal with it through legislation that outlaws some kinds of terms entirely.

Re: The "Spanish Theory" of software project management

#30
post #19

Earlier quoted context omitted.

But the OP is speaking to all software developers, and I'm offering an alternative viewpoint. > no one should be whining about unpaid overtime Do I think that I and other programmers should be paid for overtime? Yes, of course I do. I would gladly accept payment. My point is that this complaint about unpaid programmer time is becoming a recurring theme, as if it's a huge and terrible problem. What's next: programmers…

What's wrong with forming a union?

[Warning: This question may seem like a troll... I'm just trying to provoke a little more thinking about the pros and cons of unions as they apply to programming.]

Would a union allow it's members to contribute to open source projects? Especially those used in commercial products?

Post reply on HN