Skip to main content

Why I hate meetings, emails and phone calls




I hate meetings, emails and phone calls.  Does that mean I am a complete introvert that doesn’t like talking to people?  Not at all!  I just hate telling the same story or giving people the same answer over and over again.

In defense of meetings – I actually love the richness of communication that face-to-face communication offers.   However, what I find is a lot of folks actually do not take full advantage of this communication and are sort of half there.  Often times I look at a meeting and everyone but a couple of people are on their computers checking e-mail.  What’s the point of being in the same room if that’s what you are going to do?

Meetings, e-mails and phone calls miss a key component that new means of communication offer.  That key component is broadcasting.  A lot of information that people need is actually relevant for a lot of people.  When I created DocuSign DevCenter I specifically tried to push most of the communication to the forum.  At first people were really upset.  Salespeople came over to my desk wondering: “it’s a customer who needs help, just pick up the phone and talk to them!”  The strategy ended up paying off: thousands of developers shared questions and answers and now we have days when some posts are viewed 60,000+ times!

Of course a lot of communication is not meant for broadcasting, with the proliferation of social media I would argue that some folks actually dialed their broadcasting a little too far.  In the corporate world deal negotiations, performance reviews and trade secrets should all be disclosed in private.  Make those phone calls, attend those meetings and stay focused on the people you are in the room with.

For work related questions I always encourage folks to start with DocuSign DevCenter (www.docusign.com/devcenter) and for personal inquiries I am always reachable via Twitter: @mikebz, G+: https://plus.google.com/112023503898972747539 and FB: http://fb.me/mikebz

Happy Broadcasting!

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

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi