Skip to main content

Continued Education

A couple of weeks I got done reading “The Hard Thing about Hard Things” by Ben Horowitz.  I received the book as a gift at Box Developer Day (http://www.boxdev2014.com/) and it turned out to be one of the best management books I’ve read in a while. You should definitely spend the $15 to buy the book yourself.  One of the key things that I took away from the book is the emphasis on training:

Almost everyone who builds a technology company knows that people are the most important asset. Properly run startups place a great deal of emphasis on recruiting and the interview process in order to build their talent base. Too often the investment in people stops there.
Horowitz, Ben (2014-03-04). The Hard Thing About Hard Things

Since reading this I started implementing a training program for my engineering team at DocuSign.  We picked out Tuesday mornings at 9AM to have a one-hour class where we can share some of the things that I have learned over the years.  The first class was on the concepts of agile project management.  I took for granted that people knew the concepts and philosophy of Agile and thought that books like “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle were read by everyone.  It turned out that the majority of the team has not read them.

That was a light bulb moment for me: there are a bunch of basics that I probably think are too basic to teach, but for some people its net new information or at least a refresher.  I encouraged the team to buy and expense the books that I mentioned, and got working on the second class – the basics of the Internet.   In this class I am going to cover the basics of the internet that I feel people never fully dive deep into such as cookies, error codes, DNS, SSL handshakes, HTTP request and response structures and such.

While attending NY Tech Day and meeting with some partners in New York I had a chance to get lunch with Ben Siscovick (@bsiscovick) and he recommended a blog post from a16z.com that talks about progressions of Jeff Jordan through the management ranks at eBay.  The funny thing is that naturally I am following a very similar path and now that I am managing a team of close to 20 people I am turning more into a coach than a player.  I definitely recommend reading the full post here: http://jeff.a16z.com/2014/04/17/leaving-it-all-on-the-field/

The next class is on Tuesday.  I will let you know how it goes!

Post a Comment

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!

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …