Skip to main content

Lessons from Donald

I am very fortunate to be surrounded by some amazing people. Some of them I learn something from. These are lessons from Donald.

#1 Help if people are asking for your help.
There is one pattern I see Donald do that continuously makes him a great resource. Donald will help you if you legitimately asks you for help.

#2 Don't correct people's mistakes before they make them.
This one goes hand in hand with #1. When Donald told me about this it was in a context of football, it went something like this: “a smart blocker doesn't take the ball away form a player because he is scared of a fumble, a smart blocker just gets ready to jump on the ball the second the fumble actually happens”

#3 Ask people for help if you can use it.
Asking people for help gets them bought into your goals. If they don't like your agenda you will hear it early, if they do then they will feel like a part of the team.

#4 People don't like surprises.
Marriage proposals and occasional flowers notwithstanding people don't like surprises. Prep people if you can prep them. It's best if they are bored in a meeting instead of defensive or scared.
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!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

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…