5 ms·

> - It makes other people resentful of the fact they have to work longer hours, or change their schedules, to keep up with features or testing. That leads to mo

> - It makes other people resentful of the fact they have to work longer hours, or change their schedules, to keep up with features or testing. That leads to more staff churn. It shouldnt do though, your team should be able to work any number of hours and still be productive because things like illness, pregnancy, deaths, holidays occur and they are not always expected or planned. > - It's harder to have discussions about the work being done when someone is working outside of office hours, which leads to things being done as one person sees fit, or needing to be reworked often. That annoys other people on the team. Depends on the role the person is doing, a good team will be able to cater for those who do more hours, just view that person as like two people working then you can see your team is incapable of working with two people performing a task/job. > Other people on the team who choose not to work more than their contracted hours would be very annoyed if they saw hours as a factor in compensation, leading to more staff churn. Seems like a rehash of point 1 and that shouldnt matter. >- In a small business that charges for time in days, someone working 16 hours a day is essentially giving the customer work for free. If you charge for 2 days work, and tell the client you're doing 2 days work, but only work 1 day, that's dancing around the edges of potential fraud. A client could very reasonably argue that if you did the work in 1 day they should only pay for 1 day... Then you have a contract issue which is not handling your charges properly. Flip this around, what if you got super busy and had to do 16hrs a day to complete the job more quickly to get onto another project/source of income, would you still work 8hrs because you contract charges are wrong? > I would much rather have a good team of people working well together than have one hero doing most of the work. I sense you despise individualism which might explain why so many people go work for themselves.

onion2k 5y ago
Seems like a rehash of point 1 and that shouldnt matter. I'll clarify then. Point 1 is that people get annoyed having to work with someone who puts in more time because it makes their work harder. Point 3 is that if people see that someone got a raise or a promotion because they put more hours in, then they will think they won't get a raise or a promotion unless they put more hours in. They will see working longer hours as the barrier to advancement, and if they don't want to do that they'll leave. I sense you despise individualism which might explain why so many people go work for themselves. Saying I "despise individualism" is a bit melodramatic. I've run teams for the last 20 years or so and I've enough experience to understand that a good, well-motivated team of devs who communicate well and collaborate on a common goal is far more effective in the long term than a team who have a lone dev who's happy to grind out code in the middle of the night.
- Terry_Roll 5y ago
  I see where you are coming from which is you want a team, which is understandable but that doesnt work for the individual whose happy grinding out code in the middle of night aka the lone wolves, but then would they be working in a team in the first place?
  - onion2k 5y ago
    would they be working in a team in the first place? If you're a dev who works alone, with no other devs, no product person, no QA, no support, and no users to collaborate with then you probably can just hack on your code for however long you want without bothering anyone.

onion2k 5y ago

Seems like a rehash of point 1 and that shouldnt matter. I'll clarify then. Point 1 is that people get annoyed having to work with someone who puts in more time because it makes their work harder. Point 3 is that if people see that someone got a raise or a promotion because they put more hours in, then they will think they won't get a raise or a promotion unless they put more hours in. They will see working longer hours as the barrier to advancement, and if they don't want to do that they'll leave. I sense you despise individualism which might explain why so many people go work for themselves. Saying I "despise individualism" is a bit melodramatic. I've run teams for the last 20 years or so and I've enough experience to understand that a good, well-motivated team of devs who communicate well and collaborate on a common goal is far more effective in the long term than a team who have a lone dev who's happy to grind out code in the middle of the night.

Terry_Roll 5y ago
I see where you are coming from which is you want a team, which is understandable but that doesnt work for the individual whose happy grinding out code in the middle of night aka the lone wolves, but then would they be working in a team in the first place?
- onion2k 5y ago
  would they be working in a team in the first place? If you're a dev who works alone, with no other devs, no product person, no QA, no support, and no users to collaborate with then you probably can just hack on your code for however long you want without bothering anyone.