2 ms·
I don't have anything new to say about Boston vs. SV, but about this: would you rather be at an important team in a lesser-known company, or a less-important t
by gruseom 18y ago
I don't have anything new to say about Boston vs. SV, but about this:
would you rather be at an important team in a lesser-known company, or a less-important team in a well-known company
... that's a no-brainer for me. I'd much rather be on an important team in a lesser-known company. By "important" I mean strategic to the business. Such projects tend to be a lot more satisfying, as well as more rational (assuming a basically functional environment). And the lessons they teach are better lessons.
I've noticed two things about less important projects in larger companies. One is that they often get killed before they have a chance to release or gain traction - and it doesn't much matter how successful they are. This is because they're starved for executive support. The other is that they tend to end up in technical ghettos, working on something that seems cool at the time but is divorced from users and the business, and so doesn't have much value.