Product.good -> people.good?

In tech and the startup world, there are tons of options - new startups spring up every day with “the next big thing” - or “the __ killer,” or “__ for [insert platform here],” or “__ meets __, AGGREGATED!!”

So when something really cool comes around - it seems to make sense to want to jump on board and share in their (or your expectation of their) success. But when you know little about the actual team you’d be working on, and conventional wisdom seems to put “the people” at the top of the list when considering school / workplaces / environments in general, how do things play out?

I like to think that good people want exciting projects. A good developer wants stimulating work, and once put in an environment with that stimulus taken away (either by a boring project or, for example, being bought out by a company which stifles the exciting parts), they’ll find a new place to play out their cool ideas.

So I think instead of worrying whether product.good > people.good or people.good > product.good… I’ll stick with product.good implies people.good (with the converse unfortunately not always being true, without good management / vision / etc). Here’s to the future.

Let me know what you think on Twitter.