Unless you live outside big cities, I'm not sure if 2 hours of commute is that common (at least with my South West European perspective, maybe is different in the US/elsewhere?).
Unless you live outside big cities, I'm not sure if 2 hours of commute is that common (at least with my South West European perspective, maybe is different in the US/elsewhere?).
I've found it the complete opposite in software. Zoom screen sharing is so much easier than peering over someone's shoulder at their dark-mode IDE. Copy-and-pasting a command in the chat window - what an improvement! How many times have I said this to someone?
> "s c p space s v 0 1 colon forward-slash t m p"
Ug.
Design meetings are so much easier when I can see the UI on my screen, instead of halfway across the conference room.
We also do a lot of work with a team at another location and again - when we are all on zoom together now we can all see each other, we can all interreact when each other. It used to be 6 of us on one conference room and six of them in another conference room trying to talk to each other over a tinny speaker.
I hope I never have to go through any of that ever again.
Like, a couple weeks ago I had to waste half my day to go into the office and sit in a 3 hour meeting. I got some useful information out of that, but there was SO. MUCH. OVERHEAD. I could've watched the webex from home and saved so much time because the relevant parts were 2 10 minute sections spaced out by like 2 hours.
Plus I hate sitting close to people who had onions for lunch. And alcohol. And it's always that dude you've gotta pair program with that smells like a gorilla and has bad breath. xD
It would be harder in the office - too many people talking over each other in separate meetings. I can't imagine. So we all end up fighting for few conference rooms, or we squeeze once again into each others cubicles, losing the advantage of multiple screens and trying not to talk to loud and disturbing everyone around us.
I've spend decades developing in offices with other engineers, collaboration is always difficult when what you are collaborating on is always tiny text on a small screen. Zoom is better.
I find Zoom in particular to be a crude place to get this type of work done. Why do I have to send a huge video stream that roasts my laptop just to share a few kilobytes of text? I can’t scroll around or select text to point something out.
If the streamer’s text is too small, I’m shit out of luck there too.
Visual Studio Code has great collaborative coding tools that I have found work really well in a local network setting sitting near coworkers. Zoom is a total cudgel in comparison for this task.
I am a father of four (though they're here less now that they're leaving the nest), happily married, active in a committed church community and love outdoor things like water skiing, flying planes, snow skiing, biking, etc. I build things like legos, stand up paddle boards, Ford ranger engines, and the 1000 ft addition we added to our home. I enjoy my work--sometimes I love it even, and other days I'm ready to rage quit, because I'm one of those difficult to manage dramatic people--it is hardly my whole life though.
I have spent nearly 10 years (2 different gigs) of my 30 working years working from a home office. In both instances, it was awesome at first, and then I came to hate it. I totally concur with the GP. I'm just not as productive at home. I know that most of us in all 3 teams where we've done some remote work are generally more productive when gathered. No amount of technology solutions has improved that.
My suspicion is that there are other factors at play here. In my case, I've worked in companies where the software development components of the company are relatively small (anywhere from 2 up to at most 18 people). My commutes have all been (relatively) short (15 minutes or less). I've always had flexible schedule available to me--come go when you need, get the work done. And at times, I do actually choose to sequester myself at home to write a mountain of code that just needs a mountain of direct writing.
I'm curious if perhaps it's not so much work at home, as it is some degree of autonomy that needs to be given to people to manage their own work load. That kind of autonomy tends to go down as company size goes up. If corporate overhead burns up a lot of ones time, then it may indeed be that people feel they are getting more creative work down at home.
What I'd like to see is more flexibility, less middle management (because I think this is the real source of most of these issues) and more of the "teach the employees correct principles and allow them to govern themselves" gestalt.
Do you have data to back up your suspicion?
Big incorrect assumption here, my primary focus is not my work but my hobbies, family and friends. I don't like working in the office mainly because it's social but because we all are more productive. I like to be efficient at my job, even though I don't think it's my primary focus in life.
You can't just write something like that and then accuse someone of a "big incorrect assumption". Work is work, I work to do my job, if you want to go to the office to be with people because otherwise you live alone that's okay, but you can't just turn around an say "I have plenty of friends, it's about being more productive".
The pandemic has done some of that figuring out for us.
These flats would be considered tiny by American standards and you have a lot less privacy/independence from your neighbours.
Yep, that sounds as ridiculous as your statement.
And/or (like me) you like work being somewhere different to home, and don't have room for a dedicated home office. In fact even if I have the room I'd prefer for work to not be in the house. Being able to work from home is useful to me on occasion, for both work and personal reasons, but I did not like it nor feel myself to be productive when I was there all the time. If I had no choice but to work remotely I'd probably rent an office space and have to factor that into my costs and benefits analysis of the job.
Then again I currently work a 15 minute slow-ish walk from home (or less than a 10 minute run back) if I take the most direct route, and can get home to entertain the cat at lunch many days, so the commute isn't a significant factor like it will be for many.
Your top speed is less and your average speed is more. Cars never seem to get past 15mph in that kind of traffic.
Motorcycles are nice too. Good top speed, lane filtering to avoid traffic, plus real brakes, rear-view mirrors etc. Feels a lot safer than my electric skateboard used to.
I live alone too and I hate for me when people at the office became an erzats social circle. It is not. It is not a social circle but a workgroup you have little control over; you might end up with really difficult people, great teammates you love might leave, project might get cancelled and that group might get disbanded altogether.
Even if you had the best workgroup, most of the time those people will not be in your life for long or deep. They won't help you move, drive you to and from an outpatient procedure, won't play with your kids or even be by your deathbed. And you do need people who would do those things in your life. For this reason, I liked the social lack WFH created because it was closer to the state of reality, and forced me to invest in my real, non-workplace relationships.
To be clear, I am not saying you can't make lifelong friends in a workplace, I am saying you shouldn't satisfice your social needs with a workplace. Just like hunger is a signal to point you towards nutrition, loneliness is a signal to point you towards nourishing allies. And workplaces are not places to procure that.
Any deep social needs are satisfied by my long time close friends who I see every few months or my partner if I'm dating.
I don't think you can make that call what someone should and shouldn't do to satisfy their social needs because everyone has very widely ranging needs in the first place.
I feel perfectly topped off just by being in the room at a coffee shop with people for a few hours for instance.
That is why I said satisfice.
Good on you that you know exactly what you need. I thought I did too, and it took a burnout and extended time off work to realize how I was mostly deceiving myself. Most people are not that transparent to themselves, that is why they have to be careful with the stimuli that seem to fulfill a need in the short term but create serious deficiencies in the long run.
A bag of potato chips will curb your hunger but you'd be severely malnourished if it was the only thing you ate for a year. Cocaine, amphetamines even caffeine will give you an elevated sense of agency but you'll quickly spiral down to addiction with little corresponding real-world, long-term gains. A workplace, a coffee shop or even binging netflix alone might create a sense of a peopled life, but none will be real allies that can have your back in a time of need.
If you count weekends, you have 5 * 8 + 2 * 16 = 72 hours of "free time". so 5 hrs commute / 32 hrs = 6.94% or 1/14.4 of your time awake.
Also, I'm not following your calculations. If we establish that your 'free time' is 72 hours per week (8h/weekday and 16h/weekends), and the commute time per week is 10h (2h round trip x 5), it would be 10/72 or roughly 13.9%.
And besides that, laundry is going to have to be done regardless, so its not like they would be saving time by commuting to work instead. The laundry will still be waiting when they get home.
You can do the same way with commuting, enter the bus/subway/train and then do other thing while there, you don't have to wait until you arrive to start doing other things.
> And besides that, laundry is going to have to be done regardless, so its not like they would be saving time by commuting to work instead. The laundry will still be waiting when they get home.
You could have someone else do the laundry for you.
Maybe it was a bad example. I wanted to compare activities that we usually do where you can perform multiple things at the same time. Commuting is generally a passive activity while we wait to arrive to our destination, just like laundry is a passive activity until the machine is done.
In my pre-covid life, I often couldn't even hold a book on the subway as it was too crowded for that. There were times (near daily) I couldn't even reach into my pocket to take my phone out to put on a podcast due to the crush of people (and oh my god the stress when your headphone's cord would get hooked on an exiting passenger).
My commute, while long enough to do something useful, was never useful. Crowded platforms, crowded trains, and transfers down long crowded corridors made it impossible to do anything else. And I'll be damned if I'm going to do more work on the way to and from work!
This works but only in very specific types of commutes. I used to take the train which took 30 minutes each way and I always got a seat, perfect for reading, maybe even light work. Now after almost 2 decades I know that that's the exception and almost always my commute was pretty much wasted (I don't consider listening to music or podcasts productive, it's nice but not productive).
Even listening to an audiobook or podcast is such a passive thing it's hard to call it "doing" something.
What do you do?
Constant talk and interruption are not conducive to the work of a software engineer.
During the times you are coding, yes. But a software engineer is more than a coder, so there are times when collaboration is very useful.
But nothing distinguishes a junior and a senior more than the ability to work independently.
(Although obviously those statements aren't absolutes, hence the use of the word "often".)
We are talking Months and Months" by stopping other teams going of at a tangent or flat out just not doing what they are told.
The seniors used to be called "architects," and the "driving projects/design" used to be called RUP.
Your seniors should definitely be thought leaders, but when they get "too senior" or "too important" to write code, the company is done innovating. That's a major organizational smell.
And if your code isn't expressive enough that the design can be extracted without major effort, then the two will inevitably diverge at some point. Many bugs will appear.
More seriously though, it's part of skilled project management to organize work in such a way that seniors don't need to constantly collaborate to stay in sync.
Thanks to the incredibly bad city planning (which is common all across North America) and complete joke of local transit options (also common in NA), you regularly see folks with 45 minute to 2 hour commutes one way.
Folks are losing as much as 4 hours out of their day even though they live in a small city that should be easier to commute but isn’t due to corruption and laziness of the city.
To be clear, we’re not talking Seattle or Portland, we’re talking obscure cities like Ogden, Calgary, Edmonton, etc.
North America is a massive turd compared to practically anything in Europe. Some of your far flung towns have better transit than some of our metropolises.
tldr; it is drastically worse for commutes in any non-major American cities. You have no idea how good you have it in Europe.
I tend to agree with this, and I've worked remote (hybrid) for over 12 years now. For me, a hybrid is the best. Most tasks and problems can be solved well asynchronously and for those, give me a WFH option. It's great for all the reasons this thread creator mentioned and time cannot be understated. The commute alone typically requires a vehicle and the much of maintenence time I spend in my free time comes from wear and tear of commute driving as do expenses to expedite repairs for necessity of a car for work. This stuff all adds up.
Once every now and then, in person meetings and problem solving synchronously is good where virtual just fails. Usually this involved external clients and so forth or some physical, hardware related aspect of work. Software alone I can typically do fully remote as it's assumed everyone is competent and can easily share needed information and visuals with one another.
>Unless you live outside big cities, I'm not sure if 2 hours of commute is that common (at least with my South West European perspective, maybe is different in the US/elsewhere?).
I lived in rural US and my experience is that commutes tend to be longer, both in distance and time, in rural areas. While traffic related commute times tend to melt away, with less density, people tend to drive further for better employment opportunities. Sometimes this involves living near but not in a large metro area and driving hours daily to pull in high income with low COL at the sacrifice of great commute times. I know a surgeon in Texas who commutes around 4-6 hours each trip (nearly doubles his income), someone near NY/NJ who commutes 6 hours daily to drive in, and people in small areas that would drive 2-hours to a nearby plant that pays more. One of my peers used to work 3 positions and one required driving an hour each way to. One of my older directors actually lived 2 hours away and purchased a condo near his job where he worked and stayed throughout the week then returned home on weekends. I presume his wife who didn't work would sometimes stay at his condo but never felt comfortable breaching that discussion.
For them, the time they lose can't be spent working elsewhere and average out to the same higher rates and they're willing to sacrifice that time to pull more in and provide for their families. This is ultimately because good paying opportunities are often few and far between in low COL areas and highly competitive as well. For me, living in a metro area makes more sense these days. You pay more for property but recover that in terms of commute time and TC. You also have more security depending on the area by there being more opportunities to transfer to should you want/need, without changing commute times too drastically. If you live in a rural area and the diamond in the rough position you found disappears, you have to consider significant lifestyle changes for you and your family or even consider uprooting and moving. There are trade-offs either way you go.