Skip to main content

Staying Hands On


A while ago I’ve reached the point where getting into the production code and contributing has become almost impossible.  Part of it was because of the variety technologies that engineers in my organization have used, part of it was due to meetings and crazy schedule that I was subjected to when I reached Director level.

However, I still make it a point to get some coding done.  Why? I think part of it is because my family is in the medical field. Among doctors a person high up (at least while I was growing up) was a “chief surgeon” or someone who commanded a lot of respect for their “technical” knowledge.  It seemed like back in those days you couldn’t hide behind any excuses like “I am not nearly as smart as these guys”

How do I stay hands on?  First of all it’s all about making time.  Yes there are some meetings you have to say “no” to and there are some dinners and tech mixers that you have to skip.

Second is finding out bite size projects.  I am fortunate enough to work on a team that deals with new platforms and APIs.  I can usually add value by building a prototype against the new API first.  It helps me figure out if the tools and the features for the scenarios are available.  In the past several weeks I tried working with Parse and Azure Mobile services. It was fun and helped me answer some questions about mobile backends, now I can actually speak intelligently about the tradeoffs of each.

Another way of staying hands on without being a part of the Scrum team is to do a lot of code reviews.  I find those helpful because you can actually have coherent conversations with customers and partners without having to drag your engineers along to every meeting.  It’s also great because you are a newbie in all the new code and you can make sure that things are readable and accessible for when you hire new people.

Staying in the code will help you keep a pulse on your code base and stay connected with the team.  I recommend it.



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!

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…