Skip to main content

Anniversary of Paperless Life

In less than a month it's going to be a year since I stopped storing paper. Last spring before my move from Madrona to Capitol Hill I did a bit of spring-cleaning. As I was cleaning out my closets and the attic I realized how much old and useless stuff I had. Some of my old tech toys ended up with my friends. Most of my old clothes ended up at Good Will. And then I started cleaning out my files. For a guy who has been on the bleeding edge of tech for a bit I had a surprising amount of old statements and receipts. Consolidated it was three full boxes.

During my childhood my parents told me not to lose paper. I remember carefully storing and filing my bank statements “just in case something happened.” My car was hit in the late nineties and sure enough I had a full folder of papers for a car that was totaled a decade ago. I was torn: I had an emotional attachment to my old dusty paper, yet I was too lazy to move these boxes with me. I decided that I am going to go paperless.

I decided to scan some of the most important documents from my past and have them backed up online. I promised to myself that going forward I would not store any more paper. It seemed like in the age of Internet it should be pretty easy. After all Chase already offered paperless statements and Fidelity did too. My Comcast bill could be viewed and paid online and so was AT&T’s. Those were the first steps and they took care of a lot of my paper.

This seemed like a piece of cake and I lasted without accumulating any more paper for about a month. Then I had a dentist appointment. My dentist is great when it comes to my teeth, but his assistant still writes the bills by hand and stuffs them in little blue envelopes that cost 40 cents to deliver less than a mile. My accountant insisted on sending me things via mail and the worst was healthcare. Between the Polyclinic on Broadway and Regence I must have 5 letters for every visit to the doctor.

I had to counteract this somehow. I employed two services: for anything where people wanted me to sign anything I used DocuSign and for all the paper that people wanted to send me still I created an Earth Class Mail account.

It took a little getting used to. Not for me, but for all the people that all of a sudden were shocked that I resisted their attempts to send me pages of stuff in the mail. My accountant was probably the most shocked. I kept telling her that I really don’t want my tax return sent to me. I kept reminding to send me things in a PDF file via some secure delivery service such as our own DocuSign, but she kept on trying to give me paper. Thankfully EarthClassMail would scan it in and then, if there were signatures required, I would DocuSign it and send it back to her via e-mail.

So after 5-6 months of constantly attempting to fend off the influx of paper at my door I finally ended up getting most of my important mail electronically. My life has altered a bit. I stopped going to my mailbox to see if there is anything new. The only new things were junk mail from Pizza Hut and Office Max. I tried taking that stuff out and putting it into the recycling bin but then I got lazy about that too. I stopped going to the mailbox altogether. On the eleventh month I went to clean my mailbox one more time and to my surprise it was completely clean with just a yellow note from my local post office. It read: “Your address has been marked as vacant.” According to the old paper world I might no longer exist.

Comments

mike b. said…
Wooo hooo!!!! DocuSign reposted my article!

http://www.docusign.com/blog/2010/04/19/anniversary-of-a-paperless-life-possible-with-esignature-and-other-online-services/

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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 accessible…