Linux Containers Authors: Yeshim Deniz, Zakia Bouachraoui, Elizabeth White, Liz McMillan, Pat Romanski

Related Topics: Linux Containers

Linux Containers: Article

Telecommuting: There's Nothing to Be Afraid Of

And it can assemble a best-of-breed staff

We started a recruiting firm almost six years ago. At the time, I thought about the number of telecommuting positions we would get moving forward; after all, we were working with professionals doing Open Source development. It only made sense that the outcome of the Open Source model, successful off-site collaboration, would result in corporations letting these people work off-site. For the last six years, I've found it to be quite the opposite. Granted, there are many developers who are allowed to work remotely, but not as many as I originally thought. So the question is, "Why is that so?" I'm going to repeat what we've been told by the management class, but I'm ultimately going to argue corporations have to offer this option more routinely.

The process of Open Source software creation involves dispersed individuals working remotely around the globe. Some of the top developers that we have worked with in the United States are in remote places such as Wisconsin and Iowa, not exactly what you think of as technology hubs. But that's the beauty of Open Source. It lets people participate no matter where they are. Conversely, we sometimes find candidates in remote locations who are having a hard time finding a job that maximizes their talents.

When we work with a new client, we discuss the possibility of opening the position to folks who want to telecommute. Nearly ever time I bring it up I'm told no. There appears to be a lack of trust and flexibility in corporate policy though in most cases the companies get an in-depth look at the engineers' work as a result of it being Open Source.

In my opinion, the driving factor in whether or not a company should open a position to telecommuting is if the work is measurable. In other words, is it relatively easy to determine how long it should take a good engineer to complete a particular project? Say a company needed an engineer to write a device driver. From its experience, it should be able to say that it will take a good engineer three months to complete such a project. And if that's so, then why not let him do it remotely, if he's not in a position to be an on-site employee?

Companies, however, generally stress the need for the person to be on-site to collaborate; but, even if the person is on-site, do engineers always communicate face-to-face? Because of all the communication vehicles we have at our fingertips much of the communication done inside companies today is by phone, instant messages and e-mail even if the person is just a few cubicles away. So does it really matter whether he's in the next cubicle or 500 miles away? Isn't the communication format the same no matter what the distance? In most cases, the answer is yes.

Besides the telecommuting issue in an initial candidate search, challenges can arise after a person is known to be a productive employee. Due to bureaucratic corporate policies, some places risk losing top-notch employees over telecommuting. In one recent case, that's exactly what happened. The person was a productive team member for a significant period of time, but because of his lengthy commute to and from work, he wanted to work remotely part of the week. After multiple conversations with his manager and his manager's superior, such an arrangement was deemed to be against corporate policy. They were afraid that if they let one person do it everybody else would demand the same treatment. Of course one never knows whether that would have happened but they lost a key member of their engineering team.

There's one time when I believe it's essential to have the people on-site to collaborate and that's during the architectural stage. If the company is a start-up determining its product or service mechanics, or perhaps an established company designing an extension to an existing product, I can definitely see the need to have everyone at the same physical address; the architectural stage is a crucial time for a company, involving brainstorming sessions and other face-to-face meetings. Bouncing ideas off one another is critical to the success of a finely designed product or service.

At the end of the day, I think the companies that implement Open Source methods into their business practices will let people work from afar because it gives them the best chance of landing the talent they need. Most of these people can travel to the office on an as-needed basis if the company deems it necessary. But to dismiss telecommuting out-of-hand is a potential critical mistake in getting a job done well. Of course, every situation is different, and one must deal with it on a case-by-case basis. Fortunately, Open Source is thriving and pushing us to work differently.

More Stories By Brent Marinaccio

Brent Marinaccio has been with HotLinuxJobs since its inception in early 2000. HotLinuxJobs is a recruiting firm that specializes in the placement of Linux/Open Source professionals. As director of open source recruiting, Brent has gained considerable insight in the subtleties of recruiting in the Open Source world.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

IoT & Smart Cities Stories
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...