My last company tried very hard to make me "on call" without any extra compensation.
I think it's very important to separate your work life from your home life so you have time to switch off and decompress. Never give your personal phone number(s) or email address to bosses at work - carry a separate work phone if you must, and turn it off or leave it at the office. Also don't check your work email from home, ever.
BYOD (Bring Your Own Device) where work pay you a pittance to use your personal cell as a work phone is a joke. There is no universe where it's good for you.
If you set this expectation from the very beginning, it will be much easier than trying to change to this down the road.
> My last company tried very hard to make me "on call" without any extra compensation.
I had a company try the same shit (on top of even more shit). Took a job, the pay was... not terrible. However they oddly took the time to stress that as a programmer I am exempt for overtime. After a while I was put as the "on-call" guy for deployments and crashes. I thought it was just during work hours, since we had dedicated sysadmins at the company, but it was in fact nights and weekends. The fact that they hid that during the interview and waited a couple months in when any other job offers I would have had dried up can only be a calculated move on their part. When they asked me if it was going to be a problem, I told them yes, I quit. If you're going to try to take whole weeks of my free-time for the company you sure as shit better compensate me for it. I'm not going to spend my weekends sitting around the house when I could be out hiking, kayaking, or fishing and spending time with my friends. Especially not when you go out of your way to stress you don't owe me anything additional, and especially not when it's done in such a conniving manner.
We did this for a couple years and it worked out well. So well, that some people would take the "on-call" phone in exchange for your cash (the co. paid out in Visa gift cards) since there was really only a small chance that there would be a support call anyway.
Once Finance decided they weren't too happy with how the IRS might view that, the payments were canceled. And since the devs weren't dumb enough to work for free, support was scaled back to office hours only.
Hmm... I wonder why they thought the IRS would have a problem with that. I used to work for a large tech company that, at the end of each quarter, would count the number of weeks you were on call, multiply that by $X, and then pay that to you as a bonus. It would get reported on your W2 and have taxes withheld, just like any other bonus.
That was the problem. Apparently, in order to cut down on paperwork, someone had just bought a bunch of $x gift cards and they were handed out to the people on support each week. As a one-time thing, it probably wouldn't have been a problem, but as an ongoing perk, it needed to be taxed like a bonus.
This is, basically, 100% of sysadmin/operations jobs. It's just SOP.
I recommend a structure where you get paid for on-call -- even if it's just a token amount, it makes you feel less bad about having someone cover a week for you, and sometimes people are actually happy to do so.. rather than feeling like they're doing you a "favor".
While I've had plenty of sleepless nights over the past decade, everywhere I've worked has respected me and my time. Maybe I've just had good bosses, but "show up to work whenever you want" is doubly true when you're on-call and may have been fighting issues at night.
Similarly, my bosses have always had my personal cell phone number. It's paid for by work, and it's not a scam. I can count the number of times I've been called on vacation on one freaking hand. I volunteer to provide my international phone number when I'm overseas and pick up a local SIM, and in exchange, my boss NEVER CALLS ME.
I'm always wary of folks who are so guarded and defensive ("never hand out your home phone number", etc)
I treat my superiors and coworkers with respect, and they do the same for me. If I ever found myself taken advantage of, I'd put a stop to it, or I'd quit. It has never come to that, because I work for reasonable people.
> This is, basically, 100% of sysadmin/operations jobs
Oh sure, but I was by no means sysadmin, and "on-call" wasn't anywhere near my job description or on any list of expected behavior.
> It's paid for by work, and it's not a scam. I can count the number of times I've been called on vacation on one freaking hand.
Your situation and mine are obviously polar opposites, so it makes sense you think it's find and I think it's BS. I would get called repeatedly between 11pm and 5am, often on Saturdays and Sundays. Our company WAS the cell phone carrier, and they'd only kick in $10/mo (taxable) to have you use your own cell phone for work, 24x7
Being officially on-call at the company meant you had to be no more than 30minutes from the office, carry a pager etc. etc. They expected me to take a "promotion" that was way more responsibility, way more accountability, and officially on-call for no pay raise or any adjustment to compensation.
After lots of discussions around the topic, I quit.
If you're not being paid for on call, quitting is the only message that will get through to the employer. At least among physicans, that I know of, call is written into the contract on a per-day basis, and it generally pays well.
I did that for years, oncall with no compensation. I did it because I was trying hard to build a resume, and in fact stuck out a lot of pretty difficult job situation for years to do so. It has and hasn't paid off, but I would never take another job with a pager again, paid or unpaid.
I'll flip burgers before I do it, no one would pay me enough. Mine was going off 2-3 times a night, about 3-4 days/nights a week. I was then given no comp time either, and expected in the office at 8:30AM.
Karma seems to have come my way though, because now I have management that completely respects me and my time. It's just a shame it requires some windfall from a good manager to be treated with some sense of humanity.
My recommendation though to anyone is never accept a job with a pager involved. Doesn't matter about the details or how desperate you are to build a resume.
If they won't pay for a global "follow the sun" support model, they have no business running an operation that requires 24/7 support and you don't want to be there.
Much fun is had when you're at TheNextBigUnicornWePromise!.com and they only can afford a tiny ops team but need 100% uptime and 24/7 coverage with three people!
The problem with the Devops market is that good people get snatched up for north of 200k - so having a staff competent enough for larger scale is going to put a dent in any startups payroll budget with potential to lose the guys to apple fb etc easily.
I think we might see a re-fragmentation back toward outsourced ops services :-)
Wrt: byod- what I want is complete number mobility.
And the ability to have multiple numbers on the device.
I should have a phone in this era that allows me to have calls inbound on the employer number show up as work - and have any personal number calls be differentiated easily.
In the same manner as I have three email boxes in the damn mail app - which are easily deleted or locked once I leave a company, why can't I bolt additional phone numbers onto the phone during the time I'm employed there!?!?
I have a Lenovo phone with dual sims that I bought from China.
I'm currently switching over carriers, and it's useful to be able to have my old SIM in for people and companies that haven't managed to get my new number.
So yes, the option does exist, just not in the American market. It seems to be somewhat unique to the Asian market from what I've seen.
It does mean that you're limited to the phones that have dual sim slots though, which tend to be less powerful than flagship phones.
Yikes. Being on call is fine but it really ought to a) be spelled out in advance and b) be rotated among several people so you don't end up wasting more than a weekend a month, tops.
Of course, I know people who theoretically are on sane on-call schedules but as it turns out, because of irresponsible co-workers that shirk their on-call duties they ended up being called as a last resort...
I was just thinking to myself yesterday how sometimes it would be nice to have one of those jobs where when you are away from work, there is no work to be done. Like working in a factory or something, where there is literally nothing I can do during the off hours other than relax.
This through crossed my mind because I had just finished two weeks of vacation where I literally did nothing related to work, and it was really relaxing.
So the take away is that in order to avoid burnout you need to mindfully develop the skill of 'stopping work'. While that is easy when you work on a factory line and you can't bring the tools home, and its really really hard when your job consists mostly about thinking about how to solve a problem.
I found early on that since I really enjoy programming I couldn't "stop" instead I had to shift to one of my projects so that it would be more enjoyable for me. That works a bit but not as much as sitting on the deck of a mountain cabin with no Internet connectivity does :-).
But the bottom line is figure out a way to "not work", whether it is by reading, exercising, or doing some hobby, so that you don't let the stress of work overwhelm you.
>sitting on the deck of a mountain cabin with no Internet connectivity
As someone who often struggles to 'turn off' after work, this is my favorite way to disconnect. I try to make it out fairly regularly to camp deep in the backcountry–there's no better relief from work stress than sitting by a campfire in the forest, a full day's hike from the car, parked an hour's drive past the last trace of cell service.
The feeling of freedom is intoxicating–the feeling that there is literally no way that some work 'emergency' could crop up and demand my attention. It's something I used to get on airplanes, but with the increasing availability of in-flight wifi it's not quite so peaceful.
Since I live in a city where my ISP has a bunch of "public for customers" wi-fi hotspots (Vancouver), I've considered dropping my cell-phone plan and just using a VoIP provider for calls/texts. You can find the wi-fi hotspots near most places you might need Internet (e.g. when shopping), but they don't extend into public spaces like parks, and you can't use them when moving in a car/bus/train (or even when walking at a reasonable clip.) It seems like it'd separate life into connected and disconnected spaces, rather than forcing a constant decision (that's "on you") to disconnect—and I quite like the sound of that.
I sometimes feel like part of the problem is that we look at this too black and white, for example we never say to avoid death we should eat less sugar which is true but the more immediate thing that should come to mind should be less critical things like bad teeth or getting fat, which are in their own right very important. I think by constantly just saying we're at risk of burnout makes the problem appear easy to fix, namely just avoid burnout (take a vacation, etc., in the case of excess sugar just don't die, that's what I think a lot of donut lovers are thinking) whereas if the problem was many-fold then it'd be hard to trivialize it and therefore being on call just two days a week not being a big deal all of a sudden becomes a big deal.
Been working from home for the past 3 years and I've managed to pull this off with sports. It's unbelievable how tired I feel every evening when I "stop", go play football for 2 hours (somehow the feeling is just in my head, physically I'm pretty energized) and when I get back I'm actually in the mood for working again, feeling even better than in the mornings.
Sports in general are really effective against stress, it's hard to think of something else at all when engaged in the exercise. Make that a hobby and it's a long term recipe for a great career.
I've heard a number of people suggest that taking a break for physical exercise really helps. I also found that when I started taking the train to/from work the "break" of being on the train helped trigger the habit of switching out of work "mode".
Given my typical new year's resolution I'll have to try the physical activity trick as well :-)
Classified / sensitive work is often like that. I had a job like that in the Army several decades ago... if I took my work home with me, it would have been a prison sentence if they found out. Note that I'm not talking crazy James Bond cloak and dagger Hollywood stuff, there's a whole world out there of lists of sensitive serial numbered objects and their current locations.
Some production work is like that. You don't have a "real" production network unless the SCADA is air gap firewalled from the rest of the universe for safety reasons, and if its safety critical some of your coworkers will be onsite 24x7 so you can relax when you're offsite.
I did an internship in a place like that (nothing leaves your office, security clears the building at 5.30), it was the most relaxing summer I had in college I think.
I've also thought about that a lot. I had a friend at a previous employer who considered starting a food truck business instead of doing software development.
This seems to be a cultural issue, around me in the Netherlands, most people I know slam their laptop shut between 17 and 18h and open it again between 8 and 9h, in between they are offline. A boss that would try to reach you in that time would be frowned upon. I think that we have a (more) hierarchy despising culture than most countries, that helps probably.
My company recently forced Vodafone Mobile device Management upon us, since that happened many people also stopped syncing their own smartphones (what a horrible app on Android). But I am in R&D where I guess deadlines are less strict...? Even during my PhD the lab would be mostly empty at 18:00 though I guess the people that were still working were the ones ending op at MIT.
I guess there is a reason we don't have a booming start-up culture here :)
I lived in northern France and have thought about the differences between here (the US) and Europe a lot. I think it's as much just kind of "bad luck" that the startup scene isn't there. The US really sucks a lot of lifeblood out of many other nations, partially because it was "first" with many of the entrepreneurial spirited ways of doing things here.
Would the Netherlands (one of my favorite places in the world) have a booming startup culture with changes in laws and cultural norms? No, I don't think so.
Anyone who wants to be involved with that stuff moves themselves over anyway.
It's odd because the Europeans were the first real entrepreneurs with colonialism, but it seems like that part of European culture (or maybe those particular minded Europeans) were exported and sent off as well.
I'm personally very interested in colonial era history and subsequent history of the Americas since that was the beginning of modern North/South America, and would love to run across a writeup someday attempting to breakdown the differences between new/old world thinking. Because even the Latin nations like Mexico are significantly different in how entrepreneurship is admired than from say, Spain or Italy.
The problem with anything programing or computer based is that I feel compelled to learn something new if I'm not working on a project, so even in my "off hours" I'm reading about a new language or algorithm or whatever.
And these days the odds are good that your personal projects or interests may contribute to your career, in which case your job and your interests are hopelessly intertwined. Now you have no way to avoid thinking about work unless you completely drop your hobbies.
I was going through this process for a while before I came to the conclusion that I needed to pick up an artistic hobby. I figured my entire life was very unbalanced towards technical betterment and improving my technical skillset. I took up photography as a hobby for my off-time. I no longer think about work when I'm not there or there's not an emergency with someone paging me. It's a really nice feeling to be able to apply the same amount of mental hyperactivity to something non-technical. Just don't fall into the gear obsession trap!
I've had conversations with hiring managers who believe that the only good programmers are those who do it for 60+ hours a week whether paid or unpaid (I do not pursue these positions). What worries me about not having "technical" hobbies is falling behind. Theres always an unlimited amount of things to learn, and in much of the culture on this site if you're not actively making things in and out of work then you're not following the ideal.
Well there's a level of truth to that. The best programmers tend to be the ones who are autodidacts who are passionate about their career path and it tends to spill over into personal life. The best are the ones who were learning and building at a young age and accepted "technology" as a part of their personal identity and built their life around that. Hiring managers know this and target these individuals because they know these individuals will align their efforts to the companies interests and they reward them for it.
Personally, it's not worth the stress. I was in the hospital for stress induced heart failure last year and work was a contributing factor along with urban life. Now I divide my time amongst other things. The market where I live is competitive and anyone who expects me to work a 60 hour week for them all the time and attack me for not doing so can politely fuck right off as it's not worth my life. Thankfully I don't have to deal with this; companies don't like paying overtime and I'm thankful to work for a company that respects my time.
Thats right - its not a thing where you can just get into having never touched a PC. People who aren't into technology as a rule generally don't do well as programmers, but at the same time the idea of people spending 20 extra hours PROGRAMMING (not just reading,etc) outside of work I've found leaves very little for life. Granted, I'm still working to get into some non-work-related hobbies that might involve programming, but finding the time with family obligations is just plain difficult. I spend a TON of my idle time reading though.
Well, that's true but then I love my work enough that I have fun learning about new things and playing around with new languages/frameworks/whatever triggers my fancy.
I think loving ones work is the only way to really maintain good work/life balance while working from home.
Rereading my message, I wasn't clear at all :) What I meant is that if you love your work, your stress levels do not rise and if it's enjoyable enough as a hobby, you can spend a lot of hours working but still be happy because you're doing something you like (and I'm lucky enough that I have to deal with very little bullshit that detracts from my enjoyment of work).
My work/life balance is essentially balancing things between my hobbies and my family. So, it's a much nicer situation than if I was working on something I didn't love and I had to balance that with hobbies and family life.
Saying no to your boss is a nice policy, but most of the destructive aspects of modern tech jobs are not optional things. 'Saying no' to those things means not having a job (at least in this field)
It depends.I am a consultant and have worked for many different companies on many different projects. In most cases, people say "yes" without even being asked by their bosses - out of (imaginary) fear of losing their jobs. We are fortunate to work in an industry where, even in a stagnant economy, finding another job is not a huge problem, should it come to this in rare cases (although looking for work is never fun, I know).
Please man up and don't do it to yourselves and to other people.
That said, outside of paid work, I often work/read up on stuff which benefits ME, whether it is professional or personal development.
A lot of government contracting jobs exist for programmers that are really 9-5 with ~zero overtime. Granted, they pay less than SV salary's people talk about on HN, but it's still plenty of money compared to most people in the US.
I work at a defense contractor; I can confirm this. 9-5 and no overtime. Sure, I have to keep timesheets, but whatever.
Actually, my salary is on par with the standard salaries for my area. No, it's not SV level, but salaries in Dallas are much lower than SV across the board.
Cost of living is so much cheaper, though, that I'd rather work at a defense contractor in Dallas than at a unicorn in SV. I can handily afford a 1500 sq. ft. townhouse on $65k/year, here... (I could afford it on less actually... I was making $42k when I first moved in). I don't think anybody in California can say that.
anyone who thinks running a food truck is somehow easier, or less stressful, or offers more freedom than sitting in an office and developing software for someone else is in for a rude awakening.
Yeah, you might not be cooking and serving off hours, but you're going to be doing marketing, you're going to be doing purchasing, you're going to be talking to clients about locations, you're going to be fixing your recipes when your order of beans didn't come in right, or when the price of ketchup spikes.
If you own your business, no matter what, you are always thinking of your business. Especially when your business is small and will always be small enough that you're the only significant leadership in the entire company. You won't be doing too much delegation of responsibilities in a food truck.
That's still a job I would consider one that can't be turned off at home, because if I had that job I would be reading journals to learn about the latest advancements.
When I said factory I mean like someone who works on the line fixing the machines and works on a fixed schedule with a team of people who all do the same thing.
If you do work like that, you're usually working shift(so you might be working days one week, nights the next, and graveyard after that), and you're physically exhausted enough at the end of the day that all you want to do is eat dinner and fall asleep.
I'm guessing that you don't realize that factory/plant maintenance is a pretty big industry with its own periodicals, journals, research, websites, industry organizations, etc?
One of the last things I was supposed to be piloting at my last S/W dev job was Predictive Maintenance scheduling and working with the service techs on what data they used to decide when something needed to be repaired.
Yes, to some extent, but I'm talking old school, working on the same machine for the last 25 years kind of work. I have a family member with this job. He makes good money doing it, but when he's off he's off. There is nothing he can be doing to improve his output -- he's reached the peak of his job and is perfectly happy with that.
If things are catching fire "all the time", they need full-time firefighters. Get that frequency down to "once in a while" and an on-call role becomes reasonable, IMO.
Same here; at work, I work. As soon as I leave, I drop it (although sometimes I get stuck on a hard problem and it won't leave my head for the rest of the day/until I sit down and focus on something else). Nobody I work with has my personal cell number, and even if they did they wouldn't ever call me. Big plus, all of our users work 9-5 in the same timezone so we don't have anybody using our software past 5pm anyway.
I can't speak to the others but my mind will often continue chewing on problems when I'm outside of work, like if I'm driving home, over dinner, etc.
There's also a nagging bit that says "the wife and kids are asleep, there's nothing stopping you from sending those emails/working on the fixes you were looking at earlier". Then one email becomes four, a feature is completed/tested/checked in, and it's midnight.
It's not that my employer feels entitled to free labor, it's that my brain can't stop thinking about work. My job has somehow become my hobby.
This happens to me, too... I'll have a problem that gets stuck in my head that I can't stop thinking about. In the car... making dinner... exercising... the whole time it's there, in my head, hanging over me. Sometimes to take my mind off of it I go work on other programming projects, but I am worried about burnout from programming 70+ hours a week. I've looked for other hobbies, but so far programming is the only one that I thoroughly enjoy and can stick to for an extended amount of time.
Can't avoid it sometimes with distributed teams. I have a meeting at 3:30 AM Pacific tomorrow morning (I kid you not) because there are people in the meeting from 5 wildly different timezones (and I drew the short straw since I am the only one in Pacific timezone)!
UK law requires a minimum 11 hour break between working periods. I'm not sure how that situation would work (it's rare, given the UK's timezone).
A friend in Sweden is sometimes on call overnight, but is expected to sleep. If he's called, he gets the rest of the day off, because of Sweden's implementation of the EU law these rules implement.
For the vast majority of human history, work has always been something that was interwoven into our lives. From hunting and gathering, to farming and ranching, to woodworking and blacksmithing, and so on, up until the industrial revolution, nearly everyone "worked from home" and I'm unaware of any documented ill health effects from this. Intuitively, I'd suppose that aggregate stress levels actually rose with the advent of commuting to dedicated factory/office workplaces, as factory quotas and office micromanagement are far more psychologically demanding than the farm or home workshop in which you ( or your remote, usually undemanding lord, in the case of feudal work relationships ) set your own schedule and degree of competitiveness.
EDIT: The sub-thread poster kind of hit on similar issues to mine - just a different take, then:
Most posters below conflate or ignore two major aspects in their examples:
1. Physical vs. intellectual work. I had a few almost-sleepless nights over the length of my career, worrying whether my proposed (being implemented) architecture/solution would scale. Long-term mentall stress like this can lead to psychological issues, even depression. I am not saying physical work is a bed of roses, but when you stop working, you don' take your work to bed with you. And when you are physically tired, you actually sleep better.
2. Working for yourself vs. making someone else richer through your (unpaid) sacrifice.
Working on a farm is never ending, yes, but you own the farm and all the extra work benefits YOU.
There is an insidious survivorship bias here: all that leisure time was only enjoyed by the ones who survived.
A society where the mean lifetime is 35 that works 20 hours per week gives people significantly less total leisure time than a society where the mean lifetime is 85 that works 50 hours per week.
Or in other words: all those dead infants got no leisure time at all.
In each of those cases, none of those occupations can be really be interwoven into your life as tightly as a job where +90% of your labor is done via a laptop computer. If you're a farmer, woodworker, etc. you still need a separate place of work from where you live, be it a workshop or the fields. In the evening when the farmer returns to his house to rest, there is no question he's done for the day, and he can fully relax and sleep.
The dangerous mindset is that if you're capable of working whenever and wherever you are, then why should you ever really disconnect? This problem is an epidemic with people who don't know how to create a mental separation between work life and everything else, and I would argue that although it's easier to fall in the trap if you work over a VPN, it can also happen for any worker that is permitted/encouraged to work at any time of the day regardless of the situation.
In each of those cases, none of those occupations can be really be interwoven into your life as tightly as a job where +90% of your labor is done via a laptop computer.
Software development is not a special occupational snowflake, and I'm going to guess that you've never been within the property boundaries of an actual farm, let alone actually done farm work. Your job is interwoven into your live so much because you choose to allow it, and don't know when to say "no" to your boss. Close your laptop. There, work's over. Farm work? Yeah, well, those fences aren't going to mend themselves.
You don't live at the office, do you? Not metaphorically, I mean literally sleep there. No? Guess where the farmer sleeps? At work. Every day. Extrapolate from there.
At the same time, you probably own the farm if you're living on it. Someone who's doing unpaid overtime for their company isn't getting any benefits from it.
Done for the day? Relax and sleep? Ha ha, I can tell you've never taken care of farm animals. What happens when they get sick, or have babies, or get loose, or a storm suddenly blows in, etc?
I can't help but think that the key here isn't Software vs everything else, but level of abstraction. It really seems the with software, and much computer driven work, your work as well as your products exist as purely abstracted projects. Woodworking requires abstract thinking, but the end result is usually something made out of wood, or the conclusion that you can't make what you were thinking about out of wood.
I do plenty of woodworking, including woodworking with CNC/Software. But, I do know when I'm done with a project because the abstractions are over, the plans are drawn and implemented, and the project is built. Then, its done.
* farmer ... separate place of work from where you live*
For quite a lot of human history, and still in some countries, farm animals were kept at home. The "done for the day" was enforced as much by the lack of electric lighting as anything else.
Almost any work in history had and 'end', i.e. you could finish it. You can almost never finish a software project, you can always work more. That makes a huge psychological difference.
You can certainly finish gathering food for the day/week/month/season. Knowing that you're gathing at X bushels per time period and you need Y bushels to finish out the season, it's pretty easy to figure out when work is over for the day, even if there is "technically" more to do (there's always more to do everywhere in every business that isn't bankrupt and closed, that doesn't mean every hour of every employees day requires more contributions of labor)
There's nothing special about software. There are tons of finished software projects, many of which I worked on. There are probably more finished software projects out there than projects currently under development.
Oh, you'll get another batch in almost exactly one day. There's lots of mythology about the chicken cycle (as if theres only one "chicken") being 25 or 27 hours vs our wall time clock, and chickens don't live forever, but...
Same line of thinking WRT military, farming, etc.
On a very small scale I'll never type that specific line of code again, probably.
There are very few ways to earn a living that don't terminate the procedure with "repeat from beginning of procedure"
No, that's not what we're talking about. You gather eggs until there are no more eggs in the coop. That task has an end, and then you are finished. You may begin a similar task again at a later period.
If you were asking about a job where you do it once and it stays done permanently forever, that's silly, and it's not what the guy you replied to was referring to.
Well that might be true, but when you're at home you have more choices of what you can be doing at any one moment, and too much choice can be stressful. Also when you're at work you have more external pressure from your peers to get busy, while at home you need to be more self-motivated, which is more mentally difficult.
Well this shouldn't be a surprise to anyone who has been following what others have mentioned is a best practice for working from home: Set work boundaries, both in terms of time and physical location, as to what constitutes work and what is otherwise personal/family time.
Enforce set hours as to when you are actually working as opposed to when you are doing something else, and let others in your household know what they are. Create a separate physical environment that you can mentally associate as being where you perform work, and work only, and take any other activities such as social life and games out of it -- preferably using a different computer altogether.
Setting virtual walls where work begins/ends can greatly reduce the cognitive overhead your brain has to endure when trying to separate what is work from the rest of your life, and thus lower overall stress.
From working in co-working spaces, I've met a lot of freelance people, and some people have it worked out. Set hours, strictly observed. The same days and hours each week, whatever they may be, and then life can be planned.
It's very easy to slip into 'flexible' hours when doing freelance, which can often mean working all day, any day of the week, not taking proper breaks, for weeks on end.
I've done that, felt awful for long periods, and needed time to recuperate afterwards. My body gave me a lot of signals to communicate that this wasn't good for me. I overheard another guy in one office who was doing similar hours to me, telling his Dad on the phone that he was sleeping really badly, a problem he hadn't suffered from before.
Same here. I can be somewhat flexible about when I work during the day. I choose not to. Instead I often work out of a co-working space and work the same hours daily.
Instead of all these methodologies for managing programming teams, I've often wondered why no one came up with methodologies for managing employees working from home.
That seems to be an untapped market for the "methodology" folks.
I've worked from home for years, and not as a freelancer. I just have my work hours like I would in any office.
It's worked out well for me, but it would be difficult for many people to hack it due to the extra discipline it requires. I can see why companies don't want people doing it but there's definitely big economic potential held back, and environmental/mental harm done from the daily travel into the office.
I grew up in rural Iowa and worked the typical farm boy jobs, went to school all the way through in Iowa then lived in Chicago, Nord Pas de Calais (France) and now Austin. The majority of the population that doesn't come from a similar diverse cultural background (talking true, meaningful rural cultural diversity here not skintone) and there's a lot to be said for having "grit" ingrained in who you are, it helps with handling remote work in my opinion.
You really do need to set boundaries, so the article's not wrong. On the other hand, I couldn't juggle my child's preschool and my spouse's teaching schedule, if I didn't have flex time.
The article isn't actually talking about flex time or flexible schedules. It's talking about "grazing" your work, always being available, keeping track of work emails after hours or answering work calls outside your scheduled time, etc.
I just read this interview with Brunello Cucinelli and found it inspiring. "In this company, you cannot send emails after 5:30 PM, when the company closes for the evening. The day after, when you turn up for work, what are you like? You are a still person. You are better." http://pi.co/brunello-cucinelli-2/
I usually try to learn/use a language I don't use at work. Then take a leisurely approach to learning the new language. Many times it works. Many times it doesn't. I try to do things I know I won't be doing at work right now. The stuff I do outside of work is just because I'm interested in it. I also workout, watch TV and meet up with friends etc... which involve not being at work mentally.
I've been on an always-on project for the last year or so where taking time away from work means that there's more to catch up on when I come back, no matter what. In some cases taking too long away from the project means a huge pile of other people's mistakes have accumulated, and I have to go in and clean them up.
Incidentally, I've also spent a portion of the last year on medical leave. The two have interacted pretty poorly so far, and I can definitely confirm part of the article's argument, at least in my case: When your work and personal lives are intertwined like it describes, the stress never goes away and you're constantly amped up. It's not good.
I am happy to note that nobody sent work emails over the holidays, so that's nice - at least then you get a chance to use that time to disconnect and get some distance from things and spend time with your family.
The place I worked in a few years ago handled this the best. We had a level 2/3 support team embedded in our division who handled 90% of calls.
The calls were taken by junior folks who were overtime eligible, they rotated 1 week cycles and received 20% of their hourly rate, plus a 3 hour minimum for time worked. They handled all vendor dispatch, all telco callouts.
For the resolver groups, there was a severity-1 process, with an on-call manager & call tree to the higher skill people. People were on call for two-week cycles, but any call-out to these people was treated as a defect in the process.
The average was 2-3 escalated calls to senior staff on different teams per month, out of about 5-7000 calls total.
It can. I just worked through Christmas, without any real external pressure. As always, putting in extra hours requires much more extra effort than the reward you're getting for it, so it does not make too much sense.
If you work from home you have to set boundaries and go out of your way to set the tone. Meaning, everyone knows you are working those hours at that place everyday. When you're not within those hours you're not working, period. This is how I worked from home when I telecommuted.
Being a startup founder now, I don't really find a good balance and my health is suffering. So I'm trying hard to follow my own rules this year. It's tough. There is so much work to do.
If you work in ops, you will get paged sometimes, and you'll handle maintenance windows/unplanned emergencies during off hours. It's the cost of doing business. I don't see this as "flexible work", necessarily - we don't say that a nurse on a 14-hour shift has flexible hours. That said, if you handle a midnight outage, your boss had better be ok with you coming in late the next morning.
I think it's very important to separate your work life from your home life so you have time to switch off and decompress. Never give your personal phone number(s) or email address to bosses at work - carry a separate work phone if you must, and turn it off or leave it at the office. Also don't check your work email from home, ever.
BYOD (Bring Your Own Device) where work pay you a pittance to use your personal cell as a work phone is a joke. There is no universe where it's good for you.
If you set this expectation from the very beginning, it will be much easier than trying to change to this down the road.