Skip to main content

Seattle as a "One Industry Town"

I recently came across a technical blog post that described Seattle as a "One Industry Town."

I have lived here for about 16 years, so I know a thing or two about the local industries. So what does Seattle bring to the world beside Microsoft (as this tech blogger probably implied).

#1 Seattle is still the center of American Aviation. Living here you hear about the Dreamliner, Boeing contracts and other things you don't really get to hear about in other places that much.

#2 Seattle is the home of Starbucks - the top brand in Coffee

#3 Seattle is where Costco was created

#4 The largest world retailer - Amazon.com is based in Seattle

#5 UW is consistently ranked as on of the top medical schools and facilities in the nation.

#6 Seattle is where most of the Waterskis and other water sports equipment is made by companies like O'Brien and H.O.

As you can see Seattle is way beyond just Microsoft even though Microsoft is one of the key components of our economy. Microsoft also plays an important role in importing some of the smartest people from around the world here. Seattle is often ranked as the #1 most literate city in USA.

So dear valley pundits - we are quite alright here.

-mb

PS: Last but not least - we are the providers of two out of four major cloud computing platforms here (Amazon and Microsoft) and there is no shortage of clouds here ;)
1 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…