Skip to main content

Long Form Communication in Software Development

deep work cover

After spending a better part of the decade with Slack, HipChat and Microsoft Teams I joined a team that chooses to work a different way and the depth of work is evident.  The engineers on the team contribute a lot to the Kubernetes codebase and it seems like hours and days of uninterrupted time are critical to the way they work.  This made me think about the necessity of “always on” culture.  Is getting someone unblocked worth everyone keeping an eye on Slack throughout the day?

For those who have read the timeless classic Deep Work by Cal Newport this is a well explored subject.  I have read this book a few years ago and it immediately resonated with my experience.  I think about some of the key ways that I worked early in my life and I realize that my mentors were preaching and practicing deep work.

Growing up I went to a boarding school where at night homework was done behind a desk, in the classroom with the entire class sitting there quietly.  There was a teacher present who could answer a question if you had one. This taught the kids how to sit down and focus for a few hours at a time.  ADHD was not in fashion back then, and when kids that had their attention drift, they figured out how to bring it back to their homework.  Discipline does wonders!

When I was doing my undergraduate work at University of Washington in the late 90s responding to an email was not expected for a day or two.  Very few people talked about a quick e-mail conversation, in fact most of the e-mail clients were polling every 5-15 minutes when you were connected via the dial up modem.

Today Slack and Microsoft Teams are a part of engineering organizations’ workflow.  A lot of people believe that the chat systems gained popularity because people enjoy have a quick, interactive conversation, but maybe there are other features that attract people to systems like Slack?

Here are reasons I like internal chat systems that have nothing to do with the quick mode of interaction:

1. My inbox is not a mix of internal / external / system notifications in one place

2. The rules, such as GitHub notifications go to #github channel, are done once for the team and people do not have to start from scratch like they do with email.

3. Search is close content and it searches all of the channel history even prior to people joining.

The downside is that the interface lands itself to quick, not very well formed communication. The message gets hashed out interactively instead of the messenger thinking through the question and doing research.

My current team prefers to have long form thoughts in a Google Docs.  People read the documents, comment and edit the content.  The documents can be on the subject of software development, processes changes or product requirements.  Meetings are mostly limited to just Tuesdays and Wednesdays.  There is no expectations that someone is going to respond quickly to your request and there is no expectation that you are responsive at all times.  The amount of traffic in the chatrooms is fairly small.

I have been enjoying this flow quite a bit in the last several months.  I remember that even typing up a 3 page document would sometimes take a day because something would ping me all the time.  Instead of e-mail triage I became accustomed to the notification triage, each one of them taking me out of of my train of thought.

I don’t think we are done with the evolution of communication just yet.  There seems to be something missing between long form communication, chats and the flood of information that goes to my inbox. I am hoping that someone is working hard on it as we speak.


References:

Deep Work by Cal Newport

https://www.calnewport.com/books/deep-work/


Comments

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team. I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me! SDE/T or QA Engineer interview checklist from Mike Borozdin If you like this checklist you might want to check out these posts: Emotional Intelligence in Software Teams   and  Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Should this be a microservice?

After having developed several distributed systems and been a part of dozens of architectural discussions I decided to put together a way to frame the microservices debate. Microservices have been fashionable for some time. A lot of it stemmed from the fact that big and successful cloud companies are using microservices.  It seems reasonable that to create a “serious system” one must be using serious tools and architecture, today it’s microservices.  No engineer wants to be called out for creating a solution that “doesn’t scale.” The definition for a microservice varies, but overall it tends to be a piece of your system that can run somewhat independently (unless of course it depends on other microservices) and has a REST or queue processing interface.  Overall code encapsulation and separation of concerns have all been around for a long period of time.  Current evolution with containers, fast networks and REST API allows people to easily integrate pieces of their system using web