News for hackers. Stuff that matters.
Re:What I Learned from Working 32 Hours a Week by seanalltogether on Sunday January 06, 2019 @09:38AM (#18838511)
I've often felt that a 5 day work week is about availability, not raw productivity. I could easily compress all of my weeks work into 30 hours or less, but that's not what my managers and clients value. What they value is the fact that I'm making progress on my tasks, and that my reachability is not preventing anyone else (people above me or below me) from making progress on their tasks
Re:What I Learned from Working 32 Hours a Week by YayamiOmate on Sunday January 06, 2019 @10:20AM (#18838728)
That's what i notced with my friend in the managerial position. He can spend most of the time in Work From Home mode, has really good pay grade, and can't rest. He's looks like he's on a wrist band leash getting mails every 2-3 minutes and needs to somehow react on 10%.

He doesnt do much other than be available 12-16h 6-7days a week. It's taking more toll than one would expect.

Re:What I Learned from Working 32 Hours a Week by adetrest on Sunday January 06, 2019 @11:07AM (#18838963)
I could never understand why would someone accept these jobs. What's so great about becoming a manager and work 60h/week? How's that better than 40 a week as a subordinate and letting someone else worry about all the office drama?
Re:What I Learned from Working 32 Hours a Week by IMTDb on Sunday January 06, 2019 @12:30PM (#18839385)
It's just a different set of skills and you create value/feel rewarded in a different manner. It's not better or worse, it's just different and appeals to different kind of people. Take some other example from video games:

- Why would anyone pick a healer in an MMO group ? What's so great about becoming a healer ? How's that better than playing a DPS, actually contributing to killing the boss and letting someone else worry about your health bar ?

- What is fun about plying support in DOTA ? I mean the fun is being the carry and killing everyone on the other team to win games ? How can anyone willingly waste his gold to buy visibility wards, that is really not fun at all.

The healer/support/manager (="helper") position appeals to people who like to focus less on the pure "productive" task at hand. They like to focus on getting a full picture of everything that is happening, anticipating potential issues, fixing them, and allowing the DPS/carry/engineer (="producers") to be in the best possible position so they can perform their job. This can be fun for some people even if you don't see it that way. This often is really not an easy task. This often is critical for the success of the team.

And just like there are good and bad "producers" there are good and bad "helpers". The skillset is different, the measure of value creation is different, and the fun is different.

Re:What I Learned from Working 32 Hours a Week by shimms on Sunday January 06, 2019 @03:02PM (#18840263)
What a fantastic analogy, and aligns almost 100% with why I like management and leadership.

I've often struggled to articulate the reasons I enjoy these positions over a "producers" role. This will help - thank you.

Re:What I Learned from Working 32 Hours a Week by wushupork on Sunday January 06, 2019 @01:01PM (#18839568)
Great analogy. I'm going to use that. I'm currently the "healer" in my "party"
Re:What I Learned from Working 32 Hours a Week by coding123 on Sunday January 06, 2019 @04:44PM (#18840923)
Also healers get placed in the dungeon ASAP - high priority because there are so few. I play a tank, and feel similar status effects.

I want to know the analogy of healers that rage quit (they do so more than DPSs or Tanks) with the entire manager/subordinate thing ;)

Re:What I Learned from Working 32 Hours a Week by james_s_tayler on Sunday January 06, 2019 @07:58PM (#18841897)
Easy. 50% of devs promoted to management go back to dev within 12 months (or so I keep hearing).
Re:What I Learned from Working 32 Hours a Week by adetrest on Sunday January 06, 2019 @01:16PM (#18839654)
Thank you, that helps me understand.
Re:What I Learned from Working 32 Hours a Week by el_cid on Sunday January 06, 2019 @04:49PM (#18840946)
That's a fantastic analogy!
Re:What I Learned from Working 32 Hours a Week by bradleyjg on Sunday January 06, 2019 @01:17PM (#18839658)
Let's say things are humming along swimmingly in your career. You find yourself in a very decent position in a company that has a nice IC ladder.

A decade later, you are an expert in the technologies that company uses, are paid well, and have good working conditions. But a recession comes, the company has a couple of bad years, and is taken over by a private equity firm. They decide you are too expensive and you're laid off.

You have 15 years experience as an IC, are a master of your craft, and no one wants to hire you. Principal engineers are promoted from within rather than hire from without. You are willing to start lower down the totem poll at a new place, but hiring managers believe that you'll leave at the first chance, or be disgruntled at the pay/seniority cut, or are just plain intimated by you. Realistically you are looking at a couple of decades of contracting. That's not the worst thing in the world, there are some upsides, but it's not the pure IC work you had been hoping for--it means decades of hustling.

Now look at the other career path. 6-7 years as an IC, 2-3 years as a engineering lead, 4-5 years as a engineering manager. If you get laid off at that point, besides all the engineering manager positions you can go for, you can also position yourself as a engineering VP / CTO of a smaller company. No one is overqualified for that, and the CEO that does the hiring isn't going to be intimated.

I'm not saying that you need to decide that reduced career risk (and probably extra money) are worth moving to the leadership track from the less stressful IC track, but isn't some incomprehensible choice.

Re:What I Learned from Working 32 Hours a Week by adetrest on Sunday January 06, 2019 @01:31PM (#18839729)
> You have 15 years experience as an IC

I really hope that by the time I get there and get laid off in a recession or restructuring, I'll be retiring. I love software, but not enough to do it for longer than I have to and for someone else.

Re:What I Learned from Working 32 Hours a Week by bradleyjg on Sunday January 06, 2019 @01:49PM (#18839835)
If extreme early retirement appeals to you, that's great. But given that this discussion started with "I could never understand ..." you can see that EER isn't for everyone, right?
Re:What I Learned from Working 32 Hours a Week by tfigment on Sunday January 06, 2019 @11:35AM (#18839081)
Cannot speak for all but usually its money. Many companies cap technical tracks pretty fast while management is uncapped. Next as as you go further in your career then management as a nearly universally considered a valid next step. For me, my manager was fired and rather than having to deal with hiring my boss (for second time), I took the role even though I knew I would dislike the politics/drama.
Re:What I Learned from Working 32 Hours a Week by natalyarostova on Sunday January 06, 2019 @01:09PM (#18839618)
I used to never want to be a manager. Now I'd rather be a manager than have someone incompetent and new tell me what to do. I think this is a common trope.
Re:What I Learned from Working 32 Hours a Week by useful on Sunday January 06, 2019 @02:00PM (#18839915)
For me it was protecting my people from bullshit drama. Making it so everyone could be effective and fulfilled in their job is a real thing. Most mid and junior level employees think it's bullshit, I did when I was young, but so much happens because people don't know what they want or someone doesn't have budget that is solved by asking people to work late, be on call, or work on weekends because no one said no.
Re:What I Learned from Working 32 Hours a Week by bryanrasmussen on Sunday January 06, 2019 @11:28AM (#18839052)
I'm guessing it is something to do with money in most cases.
Re:What I Learned from Working 32 Hours a Week by adetrest on Sunday January 06, 2019 @01:15PM (#18839648)
1.5x the pay for double the hours isn't a trade-up though.
Re:What I Learned from Working 32 Hours a Week by sokoloff on Sunday January 06, 2019 @02:39PM (#18840116)
If you're paid 100 units [after-tax] and your expenses are 80 units, you're left with a (higher than average) savings rate of 20% or 20 units of currency.

If you double your hours, raise your pay to 150 units and inflate your lifestyle by 25% (from 80 units to 100 units), you are now making 150, spending 100 (with more luxury), and saving 50 units (250% of what you were saving before).

That might be considered a trade-up (and is more or less the path I chose).

Re:What I Learned from Working 32 Hours a Week by bryanrasmussen on Sunday January 06, 2019 @03:25PM (#18840439)
and probably a portion of that luxury is stuff like cleaners and other labor saving services which means that a lot of time that was spent on non remunerative work is now spent on the work.
Re:What I Learned from Working 32 Hours a Week by shanghaiaway on Sunday January 06, 2019 @09:24PM (#18842254)
Tell him that there is no need to reply outside of the 9-5 schedule
Re:What I Learned from Working 32 Hours a Week by ggurgone on Sunday January 06, 2019 @10:24AM (#18838742)
This is a valid point, managers and clients value availability and that's mainly the reason why they want you full time.

In fact IMHO many prefer availability to productivity. Being available 40-50h a week is rather tiring though and it can affect productivity.

For example I found that I perform better on a 32h/week. The availability problem can be solved by having the team cover the full week (different shifts with overlapping days).

Re:What I Learned from Working 32 Hours a Week by guitarbill on Sunday January 06, 2019 @11:59AM (#18839224)
I think "the reason why they want you full time" is usually because they can (very few people push back) and/or they are in roles where more time put in equals more work done. For example, as a manager doing 1:1 is still tiring, but if you aren't paying 100% attention, that doesn't cost money unlike bugs in code.

Almost nobody can do more than 3 hours of heavy concentration/flow work regularly. Add another two or three hours for meetings, answering emails, triaging bugs, etc. and you get ~30h per week. When I'm in a position to do so, I tell my team that I'd rather have 3 hours of great work than 6 or 8 hours of mediocre work full of mistakes.

Still, it's an uphill battle culturally. And sometimes even developers don't like it, since they can't hide a lack of output behind hours in the office. I think this is a positive, because as a team lead you notice issues quicker, e.g. if someone is having a rough week. But it's also a good way to "unmask" people who e.g. embellished their skill level during the hiring process and maybe aren't a great fit for the role. That way, you can get them the training they need, or find them a different role.

Re:What I Learned from Working 32 Hours a Week by ggurgone on Sunday January 06, 2019 @12:34PM (#18839412)
> they are in roles where more time put in equals more work done

This is partially true if:

1) you only hire young folks 2) you don't care about long term health of your team

Based on this philosophy I could work 90h/week and get even more done i.e. there is always work to be done but IMHO this way of working is unhealthy and not sustainable.

Personally for me it takes more time than the average to recharge so having a shorter working week helps with recharging and do well next week and be productive. And by that I mean being equally productive to a "full time".

> if you aren't paying 100% attention, that doesn't cost money

I'd argue it can cost you money, in different ways.

Re:What I Learned from Working 32 Hours a Week by guitarbill on Sunday January 06, 2019 @01:56PM (#18839883)
I'm saying managers or clients aren't always technical, and for some of these non-technical roles, time is correlated to amount of work done, so they assume technical work is also like that.
Re:What I Learned from Working 32 Hours a Week by nraynaud on Sunday January 06, 2019 @02:52PM (#18840194)
that's an interesting twist of thing. What about making it explicit, like: "I can answer the company chat quickly, but I'm painting a mountain with my friend Bob right now".

I guess it can only go so far because some social time with family and friends have to be focused.

Re:What I Learned from Working 32 Hours a Week by MiddleEndian on Sunday January 06, 2019 @10:17AM (#18838710)
This is why working remotely is fantastic for work life balance. I can do my personal tasks, travel, visit my family, etc. and still be available.
Re:What I Learned from Working 32 Hours a Week by amelius on Sunday January 06, 2019 @10:40AM (#18838802)
How are you available when you are traveling and visiting your family?
Re:What I Learned from Working 32 Hours a Week by popotamonga on Sunday January 06, 2019 @10:41AM (#18838813)
Take the computer with you. Once in a while you have to pop it out. Rarely.
Re:What I Learned from Working 32 Hours a Week by jrochkind1 on Sunday January 06, 2019 @01:02PM (#18839582)
> Once in a while you have to pop it out. Rarely.

I think "working from home" means something different to different people...

Re:What I Learned from Working 32 Hours a Week by sl1ck731 on Sunday January 06, 2019 @03:15PM (#18840351)
Yeah, it can go either way. I tend to spend more time "working" than I would in the office because I get more invested in things or am just more comfortable. If I went into the office ever I would 100% just shut off at 5, and if I was asked for significantly more I would tell them to shove it.

Some of my coworkers view it differently though and it becomes difficult to collaborate because they are running around doing other things during core hours. It is kind of an internal battle because I don't want the privilege taken from me.

Re:What I Learned from Working 32 Hours a Week by MiddleEndian on Sunday January 06, 2019 @11:10AM (#18838977)
Family: Laptop, internet at family member's home, work in the day.

"Vacation" travel: Haven't done this myself (outside visiting family) but have had colleagues who did it without issue. Available and worked in the day, did vacation things in the evening presumably.

Re:What I Learned from Working 32 Hours a Week by tylermac1 on Sunday January 06, 2019 @11:56AM (#18839201)
I've done vacation travel before. Worked out well as we were able to take a longer trip and relax a bit more (traveling with two kids under 2 can be stressful). I only ended up taking 3 days vacation on a two week trip.
Re:What I Learned from Working 32 Hours a Week by MiddleEndian on Monday January 07, 2019 @12:34PM (#18847495)
Sounds like a sensible course of action. Hopefully we see remote work become more of a standard than an exception.
Re:What I Learned from Working 32 Hours a Week by dyeje on Sunday January 06, 2019 @10:15AM (#18838700)
Doesn't that problem disappear if everybody switches to the same shortened schedule?
Re:What I Learned from Working 32 Hours a Week by pasbesoin on Sunday January 06, 2019 @03:05PM (#18840274)
I've held a number of "exempt" positions (salary, no overtime pay) where the workload is typically high but there are the occasional slow periods or an abnormal personal schedule demand.

When they want you to work extra hours, there's no argument. There's the project and the deadline.

Come a slow day or two, though, or the need to take an hour or three for a personal task (see the doctor, for example), and there's no automatic, corresponding flexibility from them.

Oh, your manager may grant you the time, but it's always at their discretion and a "favor" in return for your "good behavior."

Gee, thanks. :-/

By the way, the positions are "exempt", but there's no hour-by-hour management of associates that requires constant attention. The whole definition of "exempt" is skewed to fix labor costs rather than provide (and pay, at a higher fixed level) for real "management of employees". Hell, often I'm not even directly interfacing with anyone who is non-exempt.

Butts in seats. In my mind, it goes along with the "open space" paradigm. It's not actually about being "efficient"; it's about appearances, and control.

Like the one petty tyrant manager who wouldn't let us upgrade woefully outdated and overly expensive process, because he might lose some headcount. His status and "security" were, in his mind -- and perhaps even correctly -- tied to that headcount.

And... I suppose low cube walls helped to "show it off."

P.S. I actually got along pretty well, including with my management. Perhaps too easy-going.

As I've had time to reflect back upon all this, my resentment has grown and hardened. A LOT of wasted time and energy.

If/when you start feeling this way, look around not just at the ostensible work you have to complete, but at the system and environment in which you are expected to complete it.

Which are the real problems?

Re:What I Learned from Working 32 Hours a Week by test1235 on Sunday January 06, 2019 @03:14PM (#18840349)
you might want to give the developer hegemony[1] a read - the author mentions this specifically: the output of a developer is hard to quantify, so now instead of being paid to build things (as might a traditional labourer), you're instead paid for your time, during which the company can assign you any work.

[1]https://daedtech.com/book/

Re:What I Learned from Working 32 Hours a Week by drdeadringer on Sunday January 06, 2019 @05:40PM (#18841202)
> is about availability

That's what I've found especially with my current job.

I can sit for a whole long time doing Nothing. I mean literally Nothing. I could tap out to see a 2.5h movie, come back, and nobody would have noticed.

But "I'm available". Oh but of course, I'll press this button for you. Let me refer you to the "subject matter expert". And no, there's nothing explicitly for me to actually do.

I can't wait for this contract to be over.

Re:What I Learned from Working 32 Hours a Week by lettergram on Sunday January 06, 2019 @10:02AM (#18838629)
Never thought about that, but availability is probably closer to what employers are looking for.

One thing my colleagues always value that I’m willing to respond at any time. It means most people come to me with their problems and my value to the business has increased (removing blockers from others).

Re:What I Learned from Working 32 Hours a Week by teekert on Sunday January 06, 2019 @02:33PM (#18840076)
Wow, you really put in words what I have unconsciously felt for a long time. This is very true in my job as well. Btw, 32 hours is almost the norm in my country but you have the same issues ;)
Re:What I Learned from Working 32 Hours a Week by village-idiot on Sunday January 06, 2019 @05:33PM (#18841174)
The problem is that the actual limited resource for workers is not time or effort, but attention. If you're available at work, you're spending that resource.
Re:What I Learned from Working 32 Hours a Week by wojcikstefan on Sunday January 06, 2019 @10:13AM (#18838690)
This is a good point. If you're a go-to expert in some category at your workplace, your availability and responsiveness might be too valuable to give up.
Re:What I Learned from Working 32 Hours a Week by ggurgone on Sunday January 06, 2019 @10:38AM (#18838799)
you might want to avoid having "go-to" experts at work because when they leave you might be screwed
Re:What I Learned from Working 32 Hours a Week by wojcikstefan on Sunday January 06, 2019 @11:47AM (#18839137)
Yep, definitely agree. Increasing the bus factor is always a good idea.