3 ms·

> if you're serious about "building product" [...] You > would build and run something yourself. Perhaps as a side project, something useful just for yourse

> if you're serious about "building product" [...] You > would build and run something yourself. Perhaps as a side project, something useful just for yourself. Lots of developers scratch itches they can't scratch at their day job that way; new tech, greenfield ideas instead of maintaining someone else's garbage, etc. And sometimes those devs go into business for themselves and realize that they don't get to spend all their time building product -- now they've got to build the marketing page and write a bunch of copy and take a ton of screenshots (of features they know they're going to change), and figure out how sales funnels work, and all the other things that go into running a business. Building and running your own company is the fastest way to get out of pure product development I've ever seen.

madeofpalk 6y ago
"building a product" and "building a company" are two different things, but i agree that for some kinds of products and scale, you need a company to make it really successful. I think about all the "lifestyle businesses" that are examples of products that don't need full on "companies" to exist. I think that if you are passionate about creating a product for people to use, then you will see through on all the other aspects of making that product survive and be used. Otherwise, what you're interested in is "development", and big places like Google will give you plenty of experience in doing that. This is not a value judgement. Personally, I have no problem working at a company where I'm paid to engineer products from the ground up. Maintaining things is boring. But that's just me.