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!

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…

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 …