Skip to main content

Who are you selling yourself to?

I just had a quick exchange over twitter in regards to Redbeacon being bought out by Home Depot.  First of all I want to congratulate Yaron, Aaron and the rest on starting a great company that got great traction.  Secondly why the hell did you sell to Home Depot?

I understand that a lot of folks in this world right now do startups and want to cash out.  If that’s why you are starting a venture – great!  You are basically running an R&D department for a big company, but if you are really passionate about your space selling to a company that sells 2x4s is a sure way to get marginalized and become irrelevant.

I have spent time in companies big and small.  I have created new features, new marketplaces, worked with partners and developed products.  In order to become a great company sales, marketing, development and executive sponsorship need to be in sync.

I can understand that a small product can be absorbed into a bigger offering and accelerate because of that acquisition, but when a company’s missions are so different it’s hard to imagine how the executive sponsorship, marketing and sales are going to rally behind the new lines.

Even when the company’s mission is aligned with your product’s mission it’s still hard to get the right support.  I’ve developed several projects that ended up going nowhere because the company was not aligned behind them.  Engineers put everything together and then… nothing.  It’s demoralizing and you can’t get folks to work hard on the next revision.

I think in a pinch Home Depot has to compete with Lowe’s on the best home improvement hardware and materials, not a web 2.0 solution for locating contractors.  My guess is that pouring money to market and evolve Redbeacon is going to be less of a priority than the core business.  Let’s hope I am incorrect.
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 …