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 ;)

Comments

Ben Siscovick said…
yeah but your sports teams suck;)

-@bsiscovick

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…