I’ve been working from home 100% for going on 10 years. I’ve had a mix of experiences re: disconnecting from work, and three things that I believe are key:
1. Work out of a separate office, ideally with a door. Don’t go in that room except when you’re working. If you work from a laptop, (mostly) never take it out of that room. Obviously some don’t have this luxury, but if you do and you’re not doing this, I highly suggest trying it.
2. Remove work communications from your phone. If you have a separate email account for work (highly likely), remove it from your phone. If you have Slack or some other chat app installed for work, remove it or remove your work account. If your company truly cares about a healthy work-life balance, this shouldn’t be an issue. If you need it for oncall, only install it then, then remove it.
3. Stick to a schedule. Log on and off about the same time each day. Don't jump on work for an hour or two here and there throughout the whole day. Log on, put your time in, log off. Don't work on weekends. There are times when you may need to put in extra and/or odd hours, but this should be the exception, not the norm.
With these three things in place, I am — quite successfully — able to get the pre-smartphone feel of disconnecting from work while working from home.
Point 1 is very important, I can confirm with also a decade of doing this.
One note I'd like to add is pay attention to your lighting, have a special "work-mode" set of lights that you turn on when you work and then turn off when you are no longer working.
I use the same work desk for non work stuff, but I turn off my "office lights" and it's a completely different vibe.
Everyone's tastes will be different but as for me, these are my preferences:
- Office lighting: at least 20k lumens of 5000K light with high CRI. For me I like to approximate the brightness of daylight. It's especially useful during the cloudy days of winter. My office is in a basement so the cheapest way to do that is string lights (like for outdoor patios), but with high quality LED bulbs.
- Personal lighting mode: regular house lighting, 3000K (so skewing towards a more yellowish, incandescent-like light). I still enjoy high CRI because I can't stand things looking bland but that's less important. More spot lights, less ambient light.
Anecdotally, I don’t find point 1 to be necessary at all. Points 2 and 3 are vital, however. As long as I cut work off at the end of the day, I’m fine.
Yeah, working from home for four years now and I only have one office and desk. It's used for work, of course, but also when I'm writing for my self, or playing video games with my friends.
I don't have any problem disconnecting from work, but it probably helps that I have a different computer for work that goes in a drawer at the end of the day.
I do follow points 2 and 3 though and I think those are essential.
Sure, the important part is you do a clean break from work and work mode, there's many ways to do so.
Me, my work-desk and pc-gaming-desk are one and the same, but I have different keyboards (PC vs Mac) for the one or the other. It's not ideal though, I'd love to have a dedicated office space and time with e.g. an own kitchenette so I don't have to dart in and out of the shared space of the kitchen multiple times a day.
I'd say that's my main issue; my workspace is separate, but everything else isn't. And it disrupts my family members' days as well. I should go to the office more often.
I agree with you. I continue sitting in my home office after I stop work, and I don't feel tempted to check in at all. #2 and #3 are paramount to me, though.
I believe there's still a mental separation you get from having separate physical spaces for work life and personal life.
E.g. there are times that I do break the rule (very rarely) and get on my work computer (e.g. download work documents for tax prep), and part of me feels like I'm back at work.
If you've not tried it before, it may be hard to relate or recognize the difference.
I don't know about everyone else, but once I close all my work apps, I completely forget about work. I just got other things I wanna do on my mind so I don't see why I would think about work.
Work to me is like going to the bathroom. I go, do my business, then leave and it's back to my normal day. With WFH, that's even more the case.
Would be interested to know which lighting products you are specifically using. I've started dipping my toe into the pool of improved lighting, but the number of products out there is quite overwhelming.
10 years ago the specialty bulbs were all metal halide and CFLs but nowadays, they are LED and much better; some are even dimmable. Sites like 1000bulbs let you search by type, brightness (in lumens), color rendering index (CRI; over 90 is best), temperature (in K), angles (for spotlights).
Many people spend a small fortune on light fixtures and then use the cheapest bulbs in them. I prefer the opposite.
To extract one bit from that: I'm a huge fan of separate devices for separate purposes. Work laptop vs personal laptop. Work phone vs personal phone. Games device vs reading device. Social media device vs productivity device.
I'm much better at contextually driven focus than I am at working mentally to keep things separate. Which I've come to be ok with, in that a lot of my creativity comes from divergent thinking, from jumbling and sorting out things. But that flexibility is a pain when I want to really focus. Different devices help me be clear about what I'm choosing, raise a barrier to distraction, and make it way easier to notice when I'm off task.
E.g., I only use HN from what I think of as my distraction laptop. Social media, fun Slacks, and HN only work on this device. Which is old, so its battery doesn't last, and which is plugged in and kept in a hidden niche next to a not-super-comfortable couch. Taking this approach let me turn off the noprocrast setting here while keeping my fuck-around-on-the-internet time in check.
My recommendation (working 100% remote since 2018).
2b - have a separate work phone
If people choose to send emails outside business hours it's their choice, but you don't have to answer. If you do, as part of your contract... Well, you saw the contract before you agreed right?
2c - Set clear boundaries between when you're off work, off, but on call and at work. How? Personally I don't mind being "on call" for <25% of a time, but I absolutely positively have to have extra money every single hour I'm on call(lets say 10~20% of normal hourly rate), and 150~200% rate for incident response time. That's the only way I can do it. But what if your employer pays you double the hourly rate all the time and "implies" it's a 24/7 on call commitment? Isn't that even better financially? Well, yes, but it's definitely not better for my peace of mind. Somehow I don't mind being on call when I see a tally for it at the end of each month, if it "just happens" (and frequently) I quickly start hating it.
> Work out of a separate office, ideally with a door.
A small-apartment version of this is to have a work laptop at home (or carry it home from in-office), but to keep it in a drawer when not in use. Same with a work smartphone.
For people who have to be reachable in emergencies, a real radio pager (best privacy, still company-issued, and it could maybe also go in the drawer), or their preferred automated emergency contact method to their personal smartphone (SMS, email, app). Optionally with a de jure on-call human in the loop. Or just a work-issued smartphone or tablet that can be configured in software to only alert on emergencies.
When emergency contacting personally-owned devices, to minimize taint with business information, the only information conveyed is to check work laptop within X minutes. (The company should also have be a rock-solid log of each such contact, for various reasons.)
(One early startup, where I was leading engineering and had bespoke MVP appliances as part of a factory production line halfway around the globe, and I hadn't yet set up a better alerting method, I just used an iPad for this. The iPad had 2 purposes, about the only things it could do: (1) compartmentalize the sketchy videoconferencing app we used, away from the Linux laptop that was early-startup powerful; (2) be a fairly discreet "picture frame" display in the evening, so that I'd notice emails from factory management or our alert system. With more time this could've been polished to be better for my nerves, but it was still definitely better than having the work laptop visible 24/7.)
Good points. I religiously turn on my laptop at 9 in the morning and turn it off at 17:30. During that time I am always reachable but after that the laptop is off and I have no work related apps on my phone.
Also: when I am on vacation I am gone and won’t work. My team has my phone number for extreme emergencies but that never happened so far.
> Also: when I am on vacation I am gone and won’t work. My team has my phone number for extreme emergencies but that never happened so far.
If you're already doing #1 (don't take your laptop out of the office) and #2 above, then this is automatic. But yes, those should especially be followed when you're on PTO.
Yep point 1 I think is the most important, but if you don't have the luxury of an office at home, having a start of work process, and an end of work process is really important e.g. at end of day, close laptop, put away in a drawer, and tidy up work paraphernalia, then sit down and have a cup of tea while reading a book. It mentally bookmarks the start and end of work, and allows your mind to reset from work mode.
These are all valid point if that's your thing. It reminds me of coffee brewing advice where the very first stated goal is "make repeatable brews" and the expert explains a very meticulous protocol they've repeated and perfected for years now。
It's nice and fine if you never get bored of it.
When people bring their laptop in the kitchen or closet, or go to coffee shops, libraries etc. it's often not because they haven't found a perfected routine, but because they don't want to sit/stand in the same exact spot in the same posture 8h a day every weekday for decades.
Point number 2 also has caveats: with a family it can be easier to allow semi-random interruptions a few times a day and work a bit after everyone's asleep than sticking to an ironclad schedule and being absolutely unavailable when your kid's having tea time or needs a quick help.
For sure, a lot of the things you're describing boils down to the flexibility -- as a perk -- you get from working from home.
But I believe it's the flexibility that make it hard for people to mentally disconnect -- it blurs the lines between work and life.
And, to your point, that's totally fine if that's your preference. I think what we're both saying is that the three points I make above are, in a way, sacrificing some flexibility in order to maintain that separation.
For me, I'm completely fine giving up some of that flexibility so that I can maintain the mental separation. But, to me, I have the best of both worlds in that I still have the option of flexibility in cases where I really need it. But I only try to exercise it when I really need it.
1. disable notifications, if you can't get rid of work-connected devices: perhaps your work computer is your only computer, and you want to watch a movie on it, just configure chat/mail whatever to only work in _pull_ mode rather than _push_. Don't worry, if something is really important it will reach you.
2. enforce time boundaries through routine. E.g. go to the gym at 17:30 every day so logging off means physically detaching yourself. Or pick up your kids, or take the dog for a walk. Make yourself accountable to non-work.
3. corollary to 2: start work when work start, not before. Do not work in pajamas, do not check your email during breakfast. Do your own things, then start working.
I have not been 100% good at doing all of these, but even doing this a bit has had massive positive effects to not doing it.
The not having work on my personal phone was a big gamechanger for me as well, even before I worked from home. Not sure when or why I made the decision but very glad I did.
I feel like the other 3 points above all help with this. That's not to say that I don't log off, and still think about something I'm working on, or wake up thinking about it (this depends on what I'm working on, how much pressure I'm feeling, and how complex/interesting it is).
But honestly, this doesn't feel any different than it always did. Pre-smartphones, I still would sometimes drive home and think about what I was working on on the way home, or "bring work home" with me.
I think the brain thing is (mostly) independent of the WFH/WFO thing -- as long as you're doing the other three things above. Otherwise, the brain thing is compounded.
> How do you disconnect and shutdown the problem solving part of your brain?
I dont.
Instead, I substitute MY OWN projects and goals and things INSTEAD OF work's goals. So instead of killing my innate curiosity and problem solving, I change its focus to serve me.
You need to do this even if you don't subscribe to the idea of work life separation. You'll find better solutions to complex problems if you can rest, exercise, pursue a hobby or other distraction for part of each day. The subconscious needs recruitment for anything non trivial. Log it and state the problem that isn't yet solved explicitly in writing. Then affirm to yourself that you will come back with a solution.
The best thing I've found is Logseq. Any other note taking app would probably do, but the important thing is that it's a "daily journal" style where I brain dump relevant things into bullet points. This has come in really handy for many other reasons as well.
I've been using Logseq for the last few months and it's wildly better for me than using things like Evernote for this. I used to be big on having a lot of structure in terms of notebooks and notes, a lot of which contained project journals of one sort or another. But the way Logseq makes journaling a primary interface makes things much easier. I tag some things I want to be able to find later, or link them to pages. But I have a lot fewer dedicated pages now, and have to worry a lot less about maintaining consistency in some sort of broad ontology.
I use paper. Sometimes I refer back to the last few pages but rarely go back further than that. 99% things... Seem like really good ideas but if they don't stick then they probably don't need a dedicated home. And if they do stick.. well, I'll have to flip a few pages and copy them into my personal wiki or something so they can have a longer life.
I leave my home office and connect with my kids or go outside. Just the action of getting up and leaving the work space and starting a new activity seems to do the trick for me, YMMV of course.
We’re witnessing a categorical shift in how people sell their time.
Once upon a time, maybe a hundred years ago, people worked “days”. This was a product of the available technology at the time. The average labourer didn’t have a pocket watch to know exactly what hour it was to clock in and out. If someone worked Tuesday, they worked from sun up to sun down. They got paid “a day’s wage”.
As time-keeping technology became more prevalent, people started working hours, not days. People started to work “8 a.m. to 5 p.m.” In this period, the constraint was now commuting. The average person lives approximately 30 minutes travel from their work and this has held roughly true for most of history. If you need to travel to work, you’d better earn enough hours’ wage to make it worth it.
Now we’re seeing something new as commuting evaporates. People are working on the order of minutes. E.g., “I have a 30-minute meeting at 2 p.m., then I’m making lunch for the kids. After that, I’ll put 60 minutes into project X before the repair guy comes by to fix the oven.”
To get the same work done, people are starting to distribute it across a full waking day (even if subconsciously). Our systems and ideas haven’t caught up to this new world yet. We aren’t earning “a minute’s wage”. But it’s hard to not see the progression now that I’ve noticed it.
In the 1990s, even as a software developer, I never answered emails after working hours. Why? Because we didn’t have access to the office mail server outside the office. It was physically impossible to work from home. Add to this the fact that I didn’t have a cell phone or a pager, so when I left the office, nobody could get in touch with me even if they wanted to.
On reflection, the separation of home and work was so natural that everyone took it for granted. Time moved more slowly. You felt more free because you could just disappear for an hour by going for a drive or a walk.
I'm honestly surprised that more companies haven't invested in broader vacation policies. My experience has been that the constant "on" state wears you down. The only way to get to "off" is to be OOTO officially for a week+. Add in parental responsibilities and you really don't have any headspace for yourself.
Would love to have 5-8 weeks per year, that would let me take at least 1 week's worth of time per quarter to recharge from the constant 24/7 rush.
Out of curiosity, how many of your coworkers have kids?
I have 3, and I've always found it a bit ominous that even when I'm on large teams (8+) I'm typically still the only person with kids. So far:
1. job 1, team of 8, only 1 other IC had kids
2. job 2, team of 10, nobody else had kids
3. current job, team of 8, nobody else has kids. If you expand it to the suborganization we're in, you get ~16 people and only one other person has kids.
And it's not like these teams are mostly college new grads or anything, it's usually people like me in their 30's.
I always wonder how much of a disadvantage it is that other people get to clock out of work, enjoy an evening, sleep through the night, and then wake up and go to work. Whereas a parent is going to clock out of work and clock in to parenting, and then when it's kid bedtime, you finally get 2-3 hours to fit in personal time that's usually still not "you" time but is you spending time with your partner.
I'd never trade my kids for my career, and I find the time I spend with them incredibly fulfilling, but it's definitely extra load. And I do depend on being good at my job to help feed them and stuff. And I did opt into this, so it's hard to say it's "unfair". But I feel like our society doesn't need more reasons not to have kids given fertility is already below replacement rate.
Fertility is definitely not below replacement rate. Maybe in western countries.
You find it hard to say it's unfair but you seem to hint to it. I don't think it is in the slightest.
Also you sound like a software developer from the US so you likely can afford to work say 80% and "recoup" some of that free time.
Yes, I meant in the West, where much of the high-tech work the article is about.
Well of course I feel it's unfair at some level! That is indeed why I made the comment.
Assuming we want society to continue, someone has to have kids. And while of course we don't want to force individual people to have kids, we should (again assuming we do want humanity to continue) probably try to achieve some kind of balance to where large swathes of people don't self-select out of having kids due to economic/career reasons.
And if the working spouse tries to shed home responsibilities to help them focus on their career, this simply promotes inequity, both sex-wise (since more women are stay-at-home spouses than men) and class-wise (wealthier people will be able to hire additional help, while poorer people will not).
Do you really have 2-3 hours after kid bedtime? By the time my kids are asleep, it's already late and have no left time to do anything more than going to sleep myself
It varies a lot - sometimes the kids are in bed by 8 and I stay up till 11. Sometimes they're not in bed till 9 and I stay up till 12 and regret it the next day. I suspect as my kids get older (they're 4.5, 2.9, and 0.8 years old atm) that will shift later and later as they converge towards more 8-9 hours of sleep per night. I'm already starting to see it with the 4.5-year-old who will often stay up until 10ish playing in his room. Probably going to need to start allowing him a later bedtime.
Children seem like a liability in almost every aspect. I'm honestly a bit surprised when anyone mentions they have/want them, and I'm not even a type A/career climber, who I would think would see them as even more of a liability.
They're amazing. They're a lot of work, and a lot of that work is at odd hours ("3am: dad I'm scared of the wind also I accidentally peed on the floor") and/or highly frustrating ("me: son, please stop leaning out that window. son, balancing precariously halfway out his playhouse window: why. me: because if you fall out of it, it will hurt. 2 mins later: falls out of window and it hurts.") (also - feeding kids of any age).
But it's so worth it. My oldest is old enough to be playing with legos, and teaching him how to follow the instructions, and then seeing him both follow the instructions and then also deviate from them sometimes with his own creativity without compromising the rest of the build (well, usually) is just amazing to see happen. And then take this sentiment ^ and apply it to practically every facet of life. Having kids is about finding magic and bonding in both everyday things, like watering the garden together, and in the once-in-a-lifetime things like going on a vacation to someplace.
But of course it's not for everyone! It is really hard work and it takes a certain maturity and disposition for selflessness to be good at it. So I of course respect people who want to opt-out.
But - setting magic aside - so much of our economy is literally predicated on populations either continuously growing or at the very least not shrinking that we need to be careful about fertility rates. I think we can look to Japan to see what happens when you make your society too much of an economic rat race: people either solely focus on it or drop out of it, and both will cause fertility rates to drop.
A good step in the right direction here is that it's probably in the interest of us all that people who want to have kids are enabled to do so. (And indeed we have some policies like this already - public schools, child tax credits, etc).
And note that my concern about none of my coworkers having kids is mostly in this vein ^: it seems to me like it's a bad sign if a bunch of people with ample means are all still deciding not to have kids despite nominally having the funding to bankroll it.
It is really hard work and it takes a certain maturity and disposition for selflessness to be good at it.
I think it's easier to be selfless about it if you don't have any ambition outside of your typical 9 to 5 career. For a lot of people genetic propagation is the summit of their existence, and there's nothing wrong with that.
I did find that it's important to work on teams where folks have kids. If you're politely vocal about the time blocks... it helps. But honestly I've had to use the 8PM-11PM slots for work with folks on the west coast. I treat is as a red flag if the management/other senior engineers don't have kids.
It worked alright for about 1.5 years, but ... I need to get more PTO to sustain this type of work load.
> Would love to have 5-8 weeks per year, that would let me take at least 1 week's worth of time per quarter to recharge from the constant 24/7 rush.
At least 1 week of vacation per quarter (in addition to normal holiday time) has been fairly standard for every senior-level tech job I’ve had in a long time.
I had one job with a generous vacation policy that resulted in some people taking 8-10 weeks of vacation or more per year, in addition to normal
holidays. They had a great time, but honestly it started to become a burden for everyone else to work around them.
Toward the end it was getting bad enough that some projects were basically stalled because you could never get everyone on the project to be available at the same time. We’d push the project forward as much as we could, then wait a week for another round of people to come back to work, then push it forward as much as we could while working around the rest of the people on vacation this week, then repeat.
It would have been okay if it was a lifestyle business where delivering quickly didn’t really matter much, but it was a less established business where we were slowly running out money. They tried hiring more people but that only increased the burn rate.
The end game was that they clamped down hard on vacation time. A lot of the people who were only there for the lax vacation schedules left. Ironically, it was more relaxed to actually do work there after it became more predictable and you could depend on people actually being available to work.
There’s probably a good middle ground but it’s not as easy as just letting everyone take a lot of vacation all the time.
I saw HubSpot (a former employer) started turning short weeks into a "week of rest". Seemed like a great idea, just synchronize everyone's vacations so that no one plans work for that week.
Unfortunately, I have yet to find a place as such in EU. In my 11 years of career, I have yet to see myself or my team ever stopping. While I hopped several jobs, everywhere is same, super ambitious people working non-stop and then get stern e-mail from HR that their previous year’s whole annual leave is due and must be taken before March 31.
Fortunately, I’ve seen within same org, teams which are always on vacation or are collecting pay with 4h coffee breaks and 2h morning breakfast, but sadly I never managed to land into one of those teams.
The “non-stop” kind is majority in EU, but somehow we like to tout the “wow must be US thing”. At this point, I believe these comments are coming from some minority group from a very specific country in EU.
I suspect many of these comments are from people in the 20% that actually do most of the work.
There are plenty of jobs where people almost never start working. I have friends who've worked corporate jobs doing little-to-nothing for years at a time, collecting 6 figure salaries until the move on to the next gig.
It also meant that, when I was "in the office," I pretty much needed to be IN THE OFFICE. I couldn't really disappear during the workday on a regular workday by going for a walk or being available at home for this that or the other thing without making specific arrangements. I had the flexibility to do that from time to time but it wasn't a casual I'll be in my home office while the contractor is doing stuff.
It's a tradeoff but, for me, not a bad one overall. No one expects me to jump into action at 9 at night but if I'm watching the TV and can solve someone's problem in 5 minutes I can do so--if I feel like it.
> when I was "in the office," I pretty much needed to be IN THE OFFICE
Well, we're getting back to that anyway... they're pretty much demanding that we all drive 45 minutes to sit at a hoteling spot that we reserved ahead of time in a noisy open office so that we can get on zoom calls with our remote coworkers all day (and be asked to "please mute because your background noise is very distracting") - and then drive home and still be available "after hours".
Glad I spent years of my life getting an advanced degree for this, I guess.
Well, some people are. I've just gone into the office when it made sense for a couple decades now. It does make sense to go in most days for people doing certain types of work, e.g. when they need access to equipment, but one of the (few) positive outcomes to the pandemic that I see is that a lot of routine meetings now default to virtual at least in my circles.
I agree. I feel a lot more OK to take time to run errands or grab lunch offsite because I know if someone needs me, I can just answer on Slack. Similarly, I can work from a coffee shop or other location and know that they can reach me if needed.
It's still like this in some limited cases. My brother-in-law is a glazier. He clearly needs to be on-site to do this. Work can't follow him home. My wife works in software just like I do, but she's worked exclusively on classified projects for 20 years, so work can't follow her home because she can't legally receive any of the relevant data at home. Work phone and work e-mail are on airgapped networks not accessible from home.
In the late '80s, my coworkers would work at night by answering emails (proprietary network) and looking through code on hardware supplied by the employer.
Indeed. Work fills the time allotted to it. If you know (even subconsciously) that you can take work home with you, it becomes easier to give yourself permission to dilly-dally during work hours. And it becomes easier for everyone to dilly-dally at work during work hours and in such a way that they feel less guilty disrupting others because, hey, you can just work later just like I can, right?
This is especially true when you are young and single. Some people have families and they do not have the time to drag out their tasks until the late hours of the night because of the severe consequences of neglecting their other responsibilities. Young people are also often under the delusion that only the moment exists, and that they will live forever and stay young forever. Nope, you only ever get older and you will be old sooner than you realize. And then you'll be leaving annoying comments like this one in the comment section.
But even single people should be able to appreciate how stretching things out means you can do less with your time. It's not like you fill those in-between moments with valuable activity. You usually procrastinate doing worthless things. Besides, task switching isn't free. You have to build up context which allows sustained deep work to take place.
We've lost the culture of maturity and seriousness. FOMO is a symptom of that. Self-promotion and social media are a symptom of that. We prefer engaging in shallow put-ons instead of being adults.
It's alright for us oldies who already have firm boundaries on this kind of thing, but the new batch could use our support here. Always-contactable is becoming (has become?) normalised, and it's just not on.
My practical advice:
- Do not put Slack / work e-mail / any comms to do with work on your personal phone. When they ask "why don't you have X on your phone", the answer is that you have a security policy to keep your personal accounts safe, but if they'd like to buy you a work phone, and pay for the contract, you'd consider carrying it. Which leads me to ...
- Establish whether you are being paid for on-call. If not, then you are not on-call
- "I sent you a message", isn't the same as "I spoke with you and made sure you understood the message I relayed outside of work hours"
I realise that these things are easier here in Europe than in the U.S.A. where labour laws are a little less fleshed out, but well, I can't help there :P
I remember reading the following quote (origin lost to me):
"Look at photos of businessmen on the streets of New York in the late 1890s. Then compare them to photos of people today.
One of the first things you'll notice is how little they are carrying e.g. no briefcase, laptop bag etc. This is because in those days if you left the office there was no expectation of doing work. Everything you would need to be productive only existed in your office. Plus, you were completely unreachable once you stepped outside so why bring anything work related?"
Now, sure, a messenger could be sent to find you at lunch and you could argue that a business lunch is still 'work' but I've always like the idea of "out of the office, out of touch".
Seeing the amount of people that answer late night chats from people in other timezones upsets me. What upsets me more are the people on vacation answering chats as soon as they’re pinged. That behavior changes work culture and expectations the more it happens. Bad managers love this sort of thing. I learned a long time ago that to keep my sanity I need a wall up between work hours and my personal life.
Having managed teams in Asia from the US, let me provide the alternate view.
You are in Asia and it's 10am HKT/10pm ET. You are facing a problem/issue that you are 90% sure someone in the US knows the answer to.
You are faced with:
- being blocked all day till US business hours
- trial and erroring your way through the problem
My view as the manager was always "I trust you to send me a message up till 10:30pm if you need something and I will respond. Don't abuse that but I'd rather be contacted late once in a while vs you being blocked all day."
That sounds like the company really hasn’t set up their teams for success. There are a lot of assumptions here that it’s on the individual contributors to solve these issues at a high cost to their personal lives.
Counterpoint, I work in an international company where teams in Europe often need to liaise with teams in the US. The policy is: if it needs to wait, it waits. If it can't wait, you need to reorganize your teams' responsibilities so that those who are reliant on each other are timezone-aligned.
> If it can't wait, you need to reorganize your teams' responsibilities so that those who are reliant on each other are timezone-aligned.
I'm not a developer nor a manager. The team responsibilities; we are one of the most efficient. Our teams cross over the globe: Hong Kong, China, Japan, America's,
My manager is spot on. The team are fine, it's just the nature of work.
Is there anyone on your team that just isn't around? Keeps a strict schedule - I've found that even working across time zones with tight deadlines, some people just have a hard stop.
> When work was done at work, and there was no chance of continuing your labors at home, your job didn’t seem nearly as all-consuming or onerous .
Working as a software engineer in the early 00s, when you had no chance of continuing labor at home, you'd stay at the office way later and potentially miss the last train home.
I'm sure there were better and less demanding companies, but the picture depicted in the article is IMO way too rosy. In several companies I've had months where my extra hours' pay litteraly doubled my base salary as we stuck in the office to meet crazy tight deadlines.
So as someone who has worked as a developer for 15+ years now, this is an honest question. What kind of things are you getting emails about after hours that can’t wait until tomorrow?
I have heard these horror stories for years but never experienced any of it.
Everyone who would be sending me email wants to be off work as much as I do. They’re not working after hours so neither am I. Even when I worked for an agency earlier in my career I can count on two hands the number of times I was contacted after hours, and it was usually an emergency like some clients database imploded.
I'm someone who occasionally sends an after hours email, but I don't expect them answered or even received until work-hours. They usually result from starting some very long process (e.g. full rebuilds, expensive tests, automated bisections, etc) that can take 30m+ near the end of the day, so I walk away to go cook and clean. I'll check on them and fire off relevant messages before I lose the mental context with sleep.
Have you considered the possibility that you don't in fact need it tomorrow? Like maybe if someone is bothering you for something that you need tomorrow, maybe you fucked up somewhere and you should pay the penalty for it instead of expecting a coworker to reply to a message while they not working.
This is probably unfair because I'm self employed but:
My customers are on Slack so I don't have much mails going on with them. I have Slack on my laptop and my tablet but I didn't install it on my phone. They know that if I'm offline on Slack they can whatsapp me or call me. That rarely happens, especially the phone call. Not every year.
I check my mail a few times per day. It's a very long time since I disabled push notifications of new mail message. Nearly all of them would be for automatic notifications of events.
This means that when I'm not easily reachable if I'm not working unless my customers really want to contact me. Apparently this doesn't bother them. I've been going on like this for at least 10 years. I wonder what we used before slack, maybe Skype: I remember many more Skype chats and calls. Meet and Slack replaced nearly all of them. Actually Skype screen sharing is better than theirs: it can be zoomed and gets closer to be full screen.
Finally, I don't have anybody to compete with inside my company, because my company it's me.
I try and make a point as often as I can of drawing the line between work time and personal time. Unfortunately being a programmer, my job is also one of my favorite things to do... so I often find myself eyeballing slack messages about the latest interesting problem the team is solving.
It’s really time for office workers to unionize to demand basic rights like:
- Ability to disconnect after work
- Explicit pay for any after hours work (no more salary workers being forced to work 24/7)
- Limits to hours worked per week
- Meal breaks (no being forced to eat lunch while on videoconference )
- Safe work environments with minimum distance between workers and air flow / filtering requirements
I started working as sw dev in 1998. I remember being quite exhausted after work. Had a dial up connection at home, mostly used for chatting and napster, but I also continued working after hours, either on pc or laptop. There were floppies and cdrw's, so it was certainly possible to take work home or homework to work.
Bottom line is that if you are very much invested in tech or work, it can be exhausting, even without any direct line to work.
I dreamt about being connected to the internet wirelessly and roaming. As soon as that came in our pocket, it became handy (you can look up anything at any time) but also addictive.
What i want to say... It's not the tech itself that supposedly made things worse, it is the habits that you make from them.
If you tell your boss that you will not respond after hours or won't work late hours, that would take courage but today that is still plausible.
Work/life balance should be a personally checked boundary, it takes practice and patience to get it right, no matter of whic era of tech.
In some fields, if you choose to not allow work to follow you home, you have to be at peace with not having certain opportunities. That horse is already out of the barn. My wife is an academic; and there are two parallel careers going on with her. First, the work of the day. Then there’s “homework” - Zoom committee meetings, reviewing papers as journal editor, constant, year-round. Possibly Cal Newport has discovered something that most of the academy has not. But much of academic work and politics of the academy goes on after hours. I’d imagine other fields are similar.
> There’s a lot about early 2000s culture I’m not eager to excavate, but this idea of the constrained workday certainly seems worthy of nostalgia.
It's not nostalgia to me. Except when working on my own businesses or a real emergency, my work ends at the end of the workday. It always has, and that has never changed.
Working outside of work hours is a choice, and one that I mostly choose not to do for other people.
I kind of like work following me home. It lets you get a foot into those arguments about how "you don't have a real job, because I have to go to a coal mine and extract coal for 8 hours a day and you just sit in front of a computer". You can respond, "yeah, but the work never ends! that's what they pay us for."
I miss those days! I had them from the 80s on after high school. You did focus more while at work with a sort of weekend mentality when 5 or 6 pm rolled around. Now, I run my second company with a single phone with my personal number on it and an eSIM for my business number. If I have told clients I will be away, I simply filter text, email, and calls by the account and/or SIM they come in on. It's not the same, but it buys me peace of mind not to jump on my phone or laptop. I am very honest to clients about stepping away and if I will be available in off hours. I started studying for my CDL, because at age 59, I was actually considering taking 100k to 150k driving a 25 to 50 ft long fuel truck 35 to 45 hours a week and dropping out or tuning out of tech. Working retirement!
My father had on-call in his job for decades in the last century, that did not mean he was constantly thinking about his job, it meant he could be reached to go if anything bad happened.
Being reachable via phone is not really the same as checking slack notifications every ten minutes.
I mean this isn't actually a large problem, at least in programming where I am familiar with a lot of trends. It is very common for people to immediately sign off for the day the minute their work day/shift is over and not do anything else after. If people want to do that then sure they can, but they also trade off the ability to earn raises and promotions by doing the bare minimum. Getting a work-life balance is important absolutely, but the answer is also not to only work the bare minimum you have to in order to get paid, especially in fields like software development where your job is not to write code, but to deliver a product that currently requires code to be written. When something breaks in software development, you don't wait 12 hours for someone to get back on shift, someone does need to be on that as soon as possible, since if that happens with something as important as say google or AWS, it breaks the infrastructure of most things, certainly most important things, on the internet.
Please, enough with this mentality. You don't need to work overtime or sacrifice your work-life balance to grow and earn raises or bonuses. For anyone reading that is working in a company that works like this, just know that there's a better world out there. Your brain can't focus for 12 hours a day no matter how much you try to convince yourself, and the more you push it the worse. It's ok to be paid to be on-call, but that's totally different than working extra hours for free to earn your CEO a big fat bonus.
I did say work-life balance is important, but also you are not being paid to sit at a desk for a few hours a day. If you work more then you should get paid more, I never said anything about working more for free, so please stick to what I was actually saying? Also try reading a book called Stolen Focus regarding the human brain's ability to focus, which is diminishing due to people actually not working on expanding their focus
Yes but the habit of working overtime in companies often leads to others feeling like their are "just doing the bare minimum" as you say. Working 8 hours and being productive throughout the week is not the "bare minimum". Companies that encourage people to work overtime are usually toxic places to work on that see jobs as a privilege instead of a partnership. In my workplace we strive to make sure that people don't over do it, regardless of being paid. You can't be on-call forever, and you can't work overtime forever. That's just not healthy and sets bad examples to juniors.
Thanks for the book recommendation, although that's missing the point.
You are a 2nd-year CS student.* You have never worked as an engineer. You do not understand what the real world is like. Please stop waxing about shit you don't know a la /r/cscareerquestions.
They may be 2nd year CS student but the world they experience is not any less real than ours who have been in the industry for 10-20 years.
You may disagree with them and that's fine. There is a sort of generation gap obviously and our opinions would differ from theirs. That's fine too.
But what is really unacceptable to me is how you dismiss their viewpoint because they are a 2nd-year CS student! What if they were not a 2nd-year CS student and still believed the same things?
Please be better than this. Comments like yours make these threads a terrible reading experience!
> Saying that an author lacks the authority to write about a topic is a variant of ad hominem—and a particularly useless sort, because good ideas often come from outsiders. The question is whether the author is correct or not. If his lack of authority caused him to make mistakes, point those out. And if it didn't, it's not a problem.
> But what is really unacceptable to me is how you dismiss their viewpoint because they are a 2nd-year CS student!
> Saying that an author lacks the authority to write about a topic is a variant of ad hominem
This is not really about authority. An outsider can have good ideas. A person who has no experience and no knowledge of the subject will usually spout nonsense as seen on this thread.
If someone was talking about how child birth doesn't need any sort of pain medication because the experience isn't that painful, wouldn't you want to know if they had actually given birth at least once?
Concretely, reading what a person who has never worked a full time job (much less had to juggle having a family and a full time job), has to say about work-life balance is pointless.
Reading their thoughts on how not working overtime precludes raises and promotions is a waste of time.
Watching as they finish their rant by appealing to a sense of duty that every software engineer must have because "if Google or AWS goes down, it breaks everything" when the people responsible for these systems are a tiny minority of all software engineers...
Come on. If OP was not a 2nd year CS student, I would have been surprised.
No, his comment is spot on. A 2nd year CS student doesn't know jack shit about working in a professional capacity, and should not be sharing terrible advise that leads to burn out that other people may follow because they too don't know shit about working in a professional capacity.
Advice carries accountability, and if you don't have the necessary experience to carry advice, it is much better to shut your trap than to reveal your ignorance. The type of inclusive coddling you are doing does not improve the world, it makes everything worse and socially penalizes people for speaking the truth. /You/ are the person who should re-consider your comments.
> Saying that an author lacks the authority to write about a topic is a variant of ad hominem—and a particularly useless sort, because good ideas often come from outsiders.
There are many others who are engaging with the arguments this young person made without bringing their age or professional status into question. That's a healthy debate. What is happening in this subthread is not!
The background can usefully affect one's choice of whether, and how, to engage.
In this case, the post already was pretty poor, on its own merits, as has been pretty well covered all over this thread. The added info took it from poor, to poor and risible, and also probably worth ignoring or quickly dismissing with a post (for onlookers) then not continuing to engage, even for those who might otherwise be inclined to start a back-and-forth conversation about it. Like, one is unlikely to dig up some well of hard-won wisdom on this specific topic that might change one's mind, from this poster, by engaging with them, given that background info.
Who's speaking (or writing) matters. It may not matter for determining whether they're right or wrong, but it matters for how (and whether) one responds.
Both are good. I did both in my other comment. Appeal to authority and ad hominem may be fallacies, but there is truth to the fact this person is speaking advise without any basis for offering it, which is relevant and helpful to point out. It is improper to chastise someone for speaking the truth.
I think the internet would be a much better experience if every person online had generic details about themselves attached to their handle; e.g. age, ethnicity and nationality, parents' net worth and income, employment history or lack thereof, etc. So just like in real life, I could easily dismiss the strong opinions of others who do not have the experience necessary to form any educated opinions on which they speak.
Yes, there is no truth, and no one's reality is less "real" than others -- but children are known to talk confidently (dare I say arrogantly) about things which they know not, when they think there are no consequences. Therefore, I would like to be able to easily filter out their opinions, so as to improve my reading experience, and that of others.
If they were not a 2nd-year CS student, they would either be: very early into their career and lucky, willfully naive or privileged, or simply a malicious and adversarial person. Atleast a child can be taught to act properly.
> I think the internet would be a much better experience if every person online had generic details about themselves attached to their handle; e.g. age, ethnicity and nationality, parents' net worth and income, employment history or lack thereof, etc.
I strongly disagree.
> So just like in real life, I could easily dismiss the strong opinions of others who do not have the experience necessary to form any educated opinions on which they speak.
And this is why. In evaluating an opinion, it doesn't really matter what the person's background is. Experts can have wrong or crazy opinions and laypeople can have correct ones.
What matters is how solid their arguments for their positions are.
I disagree with their comment too. I too believe their comment is way too much wrong. I disagree with them. But I would not go so far as creating a throwaway account (like you did) just to do dig up their past threads to find out that they are only a 2nd year CS student. It does not matter to me that their views (which are diametrically opposite than mine) came from an experienced pro or a 2nd year student. What matters to me is that their views are opposite of mine. That can be expressed without digging up their past threads.
It's not an ad hominem attack, a second year CS student is highly unlikely to carry the experience of years working in the industry in order to be able to answer this question with any degree of reliability. Calling them out on this is spot on, and I'm getting really tired of people attempting to deflect or whinge about toxicity because an certain argument doesn't sit well with them.
> It's not an ad hominem attack, a second year CS student is highly unlikely to carry the experience of years working in the industry in order to be able to answer this question with any degree of reliability.
You are literally providing an example of ad hominem attack and yet you are claiming that it is not ad hominem?
Their argument is wrong of course. So you and me are in agreement there. And their argument is wrong on its own merits. That they are a second year CS student is besides the point. Their argument would be very much wrong even if they were a 20 year experienced professional.
I guess you meant "if you produce more then you should get paid more", right? If so, yes I agree. But if you imply that just by working 25% more hours peer week than my peers I should get paid more, well, that's idiotic (maybe I'm working more because I cannot be as good as others who need less time to do the same?).
At least in IT, working more doesn't necessarily mean to produce (things of value) more.
Not that I agree with this sentiment. But you do need to do these things if others are doing so. It’s like weight cutting in combat sports. It only takes one person who does it to force all others to as well.
There is a huge difference between "doing the bare minimum" and working outside of your regular working hours. One can do nothing at all working 10h/day, while another can provide high value working 9-5 (or even less).
Obviously, there are people who work 10h/day and produce high value as well, but it's not a requirement and most sane tech companies out there do not expect that from you.
From 2010 through 2020, I was working as a mathematician, programmer, analyst, researcher full time on an odd schedule, Tuesday through Saturday. I was also working on a side hustle. I was doing fashion photography as a hobby, with the intention of going full time.
When the work week ended, my photography week began. Work was on its own computer and I never included any work communications in any of my personal devices. When we hit lockdown, everything was done from home. That said, they gave us iPhones for our regular telephone communications.
My time is mine. I earned raises and promotions, and had benefits based on my desires. I worked my schedule. If someone scheduled a meeting during a time when I was off, I would discuss that with the person. If I was needed, I'd attend; otherwise, it was my time off.
Yes we had Outlook, Teams, Slack for communications. I would stay connected during the work week, but when I was off, it was my time. My supervisors had ways to contact me in an emergency, and I let them know it was okay to do so in an emergency.
The fashion work ended, but it was one heck of an adventure! It was my time.
You should work hard and be productive during your regular work schedule, not doing that is a breach of contract. But expecting to put more hours than required regularly, it's also a breach in contract.
If you need to be available outside of regulars hours, you must be paid. If something must be up 24/7h, hire more people and set proper work shifts so it's covered.
Raises and promotions should come if you do good work, not if you work longer hours. Which will probably lead to burnout or depression.
When I go to a restaurant and order a hamburger, I don't expect to get a sirloin.
> It is very common for people to immediately sign off for the day the minute their work day/shift is over and not do anything else after. If people want to do that then sure they can, but they also trade off the ability to earn raises and promotions by doing the bare minimum.
So, when this happens, the employer is offering more money if the employee continues working? The employer is asking them to do that, and employees are saying "no, thanks" to the extra money?
The way you wrote your whole post really reads like you aren't talking about paid overtime.
So what you're saying is you made an assumption about what I said, took that assumption and wrapped your entire thing about it without knowing it was true. I recommend taking things at a surface level and not trying to read 50 layers into it
While I agree with the general gist of what you're trying to communicate, the person you're responding here did no such thing. Take a step back and re-read; they're just following what you're suggesting to one possible natural conclusion. If you don't believe that's what would happen, you can state that without accusing your partner in this conversation of "reading too deep".
If something breaks and suddenly no customer can use the product and its 5pm and the engineers say "Welp sorry, my shift ended a few minutes ago so I'll fix it tomorrow!", that is in fact the bare minimum. If an engineer does that, they can be expected to not be earning any raises for actually doing what they're supposed to do, which is not to sit at a desk for a few hours a day, but to deliver a product
The problem is that you are saying two different things in your replies. On one hand you say that you aren't suggesting that people work for free, and on the other hand you say that people leaving when their shift is over should not be rewarded with raises.
If employees are being paid to stay after 5 or be on call, then their shift isn't over. If they aren't being paid for their time, they absolutely should go home. If the product cannot afford to go down, the company is responsible for keeping paid staff on hand. Expecting people to work beyond the agreed amount and punishing those that don't by removing opportunities for advancement is reproachable. It may be the norm, but it shouldn't be.
If the company doesn't have a decent on-call plan for such issues that happen outside of regular hours, then why on earth should I be the one who has to fix that? The company is not making me a favor by giving me a job, nor I am making a favor to the company either; it's just a regular business transaction and contracts matter. If my contract says 40h/week, then why the company should expect more? If my contract says that I'm getting paid X per week for doing on-call, then sure it's my job to fix shit outside working hours.
If you tell that "you break it, you fix it", I say "agree, but during working hours"
> which is not to sit at a desk for a few hours a day, but to deliver a product
Please, let's be professionals. You work is whatever your contract says (which yes, it usually says "to deliver a product" but it also says "40h/week"... at least mine says so)
No. If the product needs to be available 24/7 then is sensible to expect a budget to do that. As in every other industry, you have around-the-sun resources allocated, proper oncall shifts, and whatever other safe net you can think of. Expecting a proverbial engineer to jump and fix things adhoc is poor business planning and fantasy-football level management.
That's why OOH (Out Of Hour) On-call Rotas are a thing.
I work as a SWE and when I'm done, I'm done.
Except one week a month when I have my OOH shift, which is on a voluntary basis in the company I work for. If something breaks during time out of office hours, then it is my responsibility to take care of it. I do, however, get paid quite a nice extra sum just for being on-call.
The company should be hiring staff to ensure continuous coverage, not relying on someone who has worked a normal "shift" to work overtime because the company is too cheap to hire the support and operations staff that it needs.
It's 5pm where? If the answer is "anywhere", then the company needs 24-hour coverage in multiple time zones, so there's always somebody on shift.
You seem to be under the impression that there is no level of effort between "sit at a desk for a few hours a day" and "be on call 24 hours a day". I can't imagine why.
The solution to this is proper support chains and on call schedules. Not to have every engineer on call 24/7. If your application is so mission critical, just expecting someone will always pick up the phone is irresponsible.
It's only the engineers problem if the engineer has signed a contract specifically stating that they have to work overtime in emergencies. If not then it's the company's problem.
You are not getting a promotion for working extra hard. Google and Amazon can afford to staff 24 hours a day if the service requires it.
The way you get promotions is through networking. You are better off spending time on the golf course. The next level isn't about working harder throughout the night. That's code monkey thinking. It's about being able to understand and communicate big picture while fitting in personally. The midnight jolt cola sessions leave you tired, sicker looking and sounding crazy to the suits above. Show them you can do the new job don't show them you can do the job of two of you.
The idea that someone who leaves work when their day is over is "doing the bare minimum" is an incredibly toxic mentality, and it leads to burnout but doesn't get you ahead. I know from personal experience. Based on your post history it seems you're still a student and have never worked in a professional capacity. I highly recommend you introspect about this and disabuse yourself of the notion that you will in any way be rewarded for working unpaid overtime, which is exactly what it is when you are in tech.
It's something a lot of people don't realize, but many technical roles are exempt from overtime, even when hourly, /by federal law/ in the US. Most roles are also salaried. You gain no direct benefit from working more hours, and it has many fringe downsides and no upsides. Working unpaid overtime skews capacity planning and budget cycles, and leads to teams which are consistently understaffed and under-resourced without reduced expectations. Being "a hero" is actually bad for yourself, your team, and your company. Now that I'm involved in budget processes, resource allocation, and prioritization much more heavily than I was in the past as an IC engineer, I can see exactly how damaging this behavior is.
In /reasonable/ companies, capacity planning is usually based on trend analysis of past completed story points and sizing, averaged against headcount. Being "a hero" fucks up the average and messes up capacity planning. In unreasonable companies, ignorant managers will happily work you to burnout if it helps them drive a sale and take credit for it without any care for your health and wellbeing. Burn out isn't something you can fix by taking a vacation, it's a serious serious problem that can have life-altering repercussions. I have so many acquaintances over the year in tech that developed substance abuse problems, serious mental health conditions, and in many cases had their lives fall apart because they inappropriately managed their work/life balance and burned out.
You should really reconsider sharing advice when you have never actually had any experience. I realize in your 20s you think you know everything and you're invincible, but I'd posit you consider an alternative, which is that you don't know shit and you too one day will get old and die. Perhaps you should re-prioritize before you pay the toll.
Life before cellphones: The after-work activities of young people in 2002 - https://news.ycombinator.com/item?id=36402076 - June 2023 (138 comments)