Live data from Hacker News

Half-Baked Product

weli.dev

81–90 of 447 posts

Re: Half-Baked Product

#81
post #29

Ouch, that hits close to home, and it seems like it does for a lot of others out there as well. So what's the solution? Is there a playbook that avoids these pitfalls, or is it just the cost of the spin. Ideally, something early engineers can point to when we see non-technical founders falling into familiar traps.

If someone has the answer I'd like to know as well. I think the most important question to ask yourself is: Where did the story go sideways? At what point what character could have prevented the disaster?

For me there is no right answer. Maybe the engineer should have been more pushy with what things not to add. Maybe the founder entrepreneur should have been realistic. Maybe sales should have not had to promise things that were not developed yet. But to each of those there is a counter-argument of why that needed to be done in that moment.

Take it as a mental exercise.

Re: Half-Baked Product

#82
I found the part about the engineer's motivation interesting:

> The founder offers [the engineer] 20% of the company and total freedom to build the perfect oven. The salary isn’t great, but there’s the promise: [...] And something more important than money: he’ll finally get to build the oven of his dreams.

That turned out to be a complete lie. Not necessarily a deliberate one - I think it's quite possible both the engineer and the founder were initially believing it - but it was still a situation that never existed in that way.

Essentially, they weren't aware of all the constraints that existed for their oven design and then mistook a situation where the constraints were unknown with one where there were no constraints at all and they could just build whatever they wanted. But the real constraints were set by the market, investors and corporate customers and those were already there before they even stated the company.

(I don't think it means you have to submit to those slavishly and can never bring anything of your actual vision into your products, but it feels naive to be completely unaware of them.)

Re: Half-Baked Product

#86
post #57

While the majority of comments are absolutely right in recognizing and lamenting such situations plaguing our industry, let's not forget this is an ultimate first world problem. It can be stressful and frustrating but we are a privileged bunch to be able to call this 'pain'.

it's a more complex version of what happens in the third world too, it's not about class it's about people

Re: Half-Baked Product

#87
Wow I was laughing internally. I couldn’t dare to laugh out loud because this story is too real to me. The moment I noticed that I just had to look back my life. Good read

Re: Half-Baked Product

#88
This was such a great read! Thank you! Too bad Oven Inc never got more headcount. Otherwise the engineers could've had a day hackathon week while the managers and founder went to a retreat for a strategy offsite.

Re: Half-Baked Product

#89

Earlier quoted context omitted.

Do you mind sharing why it was expensive lesson?

I think the opportunity cost for not moving to a different gig really hurt me, since AI/LLMs were just about to explode at the time I noticed the red flags. I chose to stay because I strongly believed in the mission of my last company (aka really wanted to make that perfect oven), and had some misguided sense of loyalty. I ended up staying a few years. A wiser version of myself would have cut my losses after at most…

learned a similar lesson at last company. should have left after six months as "lead" engineer (of two people, not really much to lead there... which is related to why i crashed and burned out, funnily enough)

i was definitely the another Engineer in my story.

Post reply on HN