Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (42)

On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 The day I became an architect Sep 11, 2024 Are developer jobs truly in decline? Jun 29, 2024 Form follows fiasco Mar 31, 2024 Thanksgiving reflections Nov 23, 2023 Working from home works as well as any distributed team Nov 25, 2022 Book review: Clojure for the Brave and True Oct 2, 2022 The Toxic Clique Sep 28, 2022 All developers should know UNIX Jun 30, 2022 Good developers can pick up new programming languages Jun 3, 2022 Java is no longer relevant May 29, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Best practices for building a microservice architecture Apr 25, 2022 Kitchen table conversations Nov 7, 2021 What programming language to use for a brand new project? Feb 18, 2020 On elephant graveyards Feb 15, 2020 Microsoft acquires Citus Data Jan 26, 2019 Teleportation can corrupt your data Sep 29, 2018 What does a Chief Software Architect do? Jun 23, 2018 Leaving Facebook and Twitter: here are the alternatives Mar 25, 2018 When politics and technology intersect Mar 24, 2018 The technology publishing industry needs to transform in order to survive Jun 30, 2017 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 LinkedIn needs a reset Feb 13, 2016 In memory of Ed Yourdon Jan 23, 2016 IT departments must transform in the face of the cloud revolution Nov 9, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 On Managing Stress, Multitasking and Other New Year's Resolutions Jan 1, 2015 Software Engineering and Domain Area Expertise Nov 7, 2014 Infrastructure in the cloud vs on-premise Aug 25, 2014 On anti-loops Mar 13, 2014 On working from home and remote teams Nov 17, 2013 Thanking MIT Scratch Sep 14, 2013 Thoughts on Wall Street Technology Aug 11, 2012 Scripting News: After X years programming Jun 5, 2012 Eminence Grise: A trusted advisor May 13, 2009

On working from home and remote teams

November 17, 2013

As some of you may know I have been working from my home office for the past couple of years. I am often asked what is it like, or whether I am productive, and so I decided to put my thoughts down in this blog post.

Exactly two years ago I decided to take on an exciting opportunity at a startup. Having spent a vast chunk of my career on Wall St. I was ready for a change. This opportunity came with an important perk - I could work from my home office full time. After consulting with my family I decided to accept this gig.

Working from home most certainly fits in with my family's schedule. I am better able to shoulder parenting responsibilities. If there is an event at one of our kids schools in the middle of the day I am able to attend. If there is an emergency I can coordinate with my wife and get the kids sooner.

The fact that I am not spending two hours a day community is a major bonus. I did the math once that a one hour commute each way adds up to a full eight hour work day every four days. At roughly 220 working days per year it adds up to 55 days of commute per year, or one year of nothing but commuting for every four years worked. Spend twelve years doing that and three years out of your life are consumed by commuting. Ponder that.

While it may seem that my work-life balance should be better it is not always the case. With BYOD policy I am always connected to work. This is not necessarily a function of working from home, but it is often difficult to completely unwind since everything around me reminds me of work and of tasks I have yet to get to. It is important to set up a workspace that is logically separated from your living space - a spare bedroom, a basement office, etc. - something you can close the door on at the end of a work day.

As far as team collaboration goes I observe no difference from working in an office, other than relying on electronic conferencing tools as opposed to face-to-face collaboration. Remote teams are possible with the right approach to management and with the right people on the team. Expert level employees that can work independently with minimal supervision can easily work remotely and be productive.

Now, the support system is still important even if you have noone but experts on your distributed team. In an actual office people form cliques and have lunch break conversations. That allows an outlet for venting frustration, and helps people stay in the loop. For a remote team an equivalent of this would be a chat room where developers can communicate informally without management snooping.

Part of the support system is also management feedback cycle. It is important to maintain regular communication with your supervisor. Just because the team is remote and comprised of experts in the field it does not mean that they don't require reviews, evaluations and course corrections.

With the right approach remote teams are not only possible but they also serve and essential role in some situations. They allow smaller companies attract and retain talented employees wherever they may be located. Larger companies can benefit from a workforce that is empowered to manage their schedules and balance their work and lives. Anything involving knowledge can be done outside of geographical boundaries. As for me, working from home is an important benefit at this stage of my life.