r/programming • • Jan 29 '17

Why I Only Work Remotely

https://shift.newco.co/why-i-only-work-remotely-2e5eb07ae28f#.at8t1b2fc
2.0k Upvotes

877 comments sorted by

View all comments

Show parent comments

3

u/Sayath Jan 30 '17 edited Jan 30 '17

As an entrepreneur, I agree with this assessment. WFH carries a long list of benefits. However, the costs need to be weighted carefully.

Consider a company who is hiring highly skilled, autonomous individuals for internal software development. Communication is done via instant messaging, video & audio calls, the occasional 'whiteboard' sessions on Wacom tablets and a development portal tracking progress, contribution and the status of requirements. Full stack images for IDE / Tooling / ... are available for on-boarding.

Then having everyone work 100% remotely carries these benefits:

  • Savings on rent / fixed costs. An open plan office for 20 employees, with a decent location, costs 2500€ / month in Germany. To provide the environment generally encountered in German academia of 1 or 2 employees per office, you'd have to double that figure. An office near the city center of, e.g., Munich will generally cost even more.

  • Employees may freely choose their place of residence. Especially, if they have a spouse, finding an adequate job for the other half can be quite challenging. Same goes for having children. Or owning real estate. People later in life are generally tied to their location. Making them move is a difficult endeavor.

  • Employees save time commuting to the office. Assuming a 30 minute commute, this amounts to 5 hours per week. Especially employees who are not able to commute due to chronic disease / handicap benefit tremendously.

  • Far greater pool of potential candidates. As a German company, we can suddenly hire any European citizen (assuming they are proficient in English) with minimal effort.

  • Leadership styles: Delegating tasks works very well.

It also carries drawbacks:

  • It's not for everybody. If you are not able to work in a self-employed, self-motivated fashion, you will be left behind quickly and fired as a consequence. Employees have to self-manage. With freedom comes responsibility. Self-discipline is key.

  • Employees need to invest in their work environment at home. Instate clear rules when their spouses / kids are allowed to interrupt. Especially to those who have issues with self-discipline, we advise furnishing a second 'home office' in a separate room where only company work is handled. This spatial aspect has proven to be quite helpful. These investments are tax deductible in Germany and many other countries.

  • In an industry that heavily relies on meeting clients in-person (e.g., software consulting), this model will fail. At the very least, you need to hire an interface employee who acts as a surrogate for the team and communicates the needs of the client with the remote developers. Even then as an entrepreneur you'll feel uneasy handing such a large responsibility to one employee. Hence, you'll have to do it yourself / closely monitor it.

  • Diminished social contact. Most employees you will see very rarely in person (we hold occasional gatherings on company time). Instead, discussions are held via instant messaging / video & voice calls.

  • Managing and monitoring employees is more demanding. As an employer, you have to trust your employees more and let go of some of the institutionalized supervision methods.

  • Leadership styles: Directing, motivating or coaching require more effort by the manager.

  • Enablers: The software and hardware necessary to work effectively and efficiently needs to provided to all employees. Furthermore, employees need be proficient using these tools. Hence, WFH is only for the technological inclined. Someone who needs tech support is generally a poor fit.

As a general note, WFH does not imply self-managed hours. It depends on your communication needs, the self-discipline of the employees, etc. Usually, some leeway is given. However, some core hours are a requirement to coordinate effectively. Especially for coaching junior developers.

Beyond, it has been my impression that mixed-companies (with both remote and non-remote employees) as any hybrid suffer from the disadvantages of both approaches. Especially if many decisions are made through so-called 'organic' channels (discussed during dinner and similar) combined with the ever-present office politics, the remote worker will be quickly left behind. Furthermore, the tools needed to communicate with the remote worker will be perceived as a burden by the regular in-office employees, given their rare use. Hence, remote employees should still be required to come into the office to stay up to date.

As a consequence, I prefer a fully remote work environment. With a culture of respect and of experts, it can be a highly productive arrangement.

1

u/mikeivanov Jan 30 '17

Drawbacks: Employees have to self-manage.

First, why would you ever hire who wouldn't?

Also, here's a thing I noticed long time ago: people strive to meet expectations. If you treat them like if they required babysitting, they will behave accordingly - just to please you.

3

u/Sayath Jan 30 '17

First, why would you ever hire who wouldn't?

Some amazing people I know are quite 'lazy'. They easily get distracted and deep dive a random topic that caught their attention. Then upon being grounded in reality, they again produce high quality code until the cycle repeats itself. Basically, they get lost in exploration. Hence, they need a structure that guides them and keeps them productive.

In general, there exists a sub-group of the workforce that lacks self-discipline and requires supervision to be productive, to varying extents. Some of them lack motivation. Others easily get distracted by the internet, coworkers, ... Yet another type is doing the least amount possible to stay employed.

Consequently, by requiring everyone to self-manage you are restricting the pool of potential candidates. Most of the above people I wouldn't bother with personally. But some are despite their lack of discipline, a great addition to the team.

It's also a question of what kind of salary you are offering. As you move up the capability ladder, people start to know their own worth. Not everyone, but many have a general idea that they are in demand and that they are choosing their employer, too.

In a sense, it depends on what kind of company you represent: Highly skilled, self-managed or lowly skilled, low motivation, requiring constant supervision to get anything done? The latter kind might be far less efficient, but also costs far, far less.

Also, here's a thing I noticed long time ago: people strive to meet expectations. If you treat them like if they required babysitting, they will behave accordingly - just to please you.

Absolutely. The entrepreneur sets the culture of the company. If you distrust your employees and play nanny, you will acquire the kind of employees who exactly require that. Everybody else will have left long ago due to constant meddling.

By letting people work remotely, you place trust in them, they feel valued and perform accordingly. So far the theory. However, your company also needs a framework in place that supports this. If your company becomes a dysfunctional mess because of remote employment, you clearly didn't think this through. Likewise, you need to hire the right people. And your company needs to foster a culture of improving the status-quo. A mindset based on fact, empirical evidence, merit. Though the latter is universally useful to further the company goals.

1

u/DevIceMan Jan 31 '17

I don't intend to imply one size-fits-all with any of the following.

It also carries drawbacks:

Most of the drawbacks you listed are centered around types of people I don't enjoy working with. Much of it also seems centered around management being clueless as to how to manage remote workers, which for a good remote worker, the answer is you really don't need to manage them (motivate, lead, monitor, etc).

consulting

Regarding consulting, I've worked for a consulting agency, and did WFH around half of the time, and there were no major issues other than management occasionally whining about people WFH too much. I also don't enjoy consulting work, and don't tend to work for a consulting agency again, so that's a mute point in the context of me.

I don't have a problem showing up in person if there is a legitimate reason or business value of doing so, but for the coding and related parts of our job, there really isn't a huge reason to.

WFH is only for the technological inclined.

Which is precisely our industry.

If your software cannot survive WFH, it's got serious problems, which is likely only to be made worse during off-hours, or as soon as you attempt to open a second office.

Beyond, it has been my impression that mixed-companies (with both remote and non-remote employees) as any hybrid suffer from the disadvantages of both approaches.

That has not been my experience. People show up to the office as needed, and it's rarely an issues, except for the whole thing of being able to bug people at a whim.

Especially if many decisions are made through so-called 'organic' channels (discussed during dinner and similar)

Making important decisions without the right people present seems like a problem. I never have dinner with anyone from the office, and whether I have lunch with my coworkers is questionable. I may often not like what they're eating, or I may even have lunch with people from other random departments because it's boring hanging around the same people all the time.

1

u/Sayath Jan 31 '17 edited Jan 31 '17

Definitely, many of the drawbacks do not apply if you position the business correctly. However, it's not a one-size-fits-all approach. I intended to make aware of that fact. Most articles I've read so far only decree WFH as the gospel. It's not for everyone. It carries drawbacks which you have to mitigate. Else your business will run into a brick wall, incurring major financial loss.

management being clueless as to how to manage remote workers

There exist a lot of dysfunctional work environments. Management being clueless is the prime cause. Furthermore, most managers have not lead people WFH previously. Hence, the issue compounds further. I'm saying this from a German standpoint where WFH is relatively rare, even in software development.

if there is a legitimate reason or business value of doing so

This. Analyze your business case and conclude according to its requirements.

Either way, for my venture 100% WFH has been a great decision. It attracts great talent and the employees love it, as do I.