Entertaining, very AI prose though.
Disagree, I assumed it was a 10 year old story because it was written in the personable style of the old internet…
Half-Baked Product
101–110 of 447 posts
Re: Half-Baked Product
#102Re: Half-Baked Product
#103Uncomfortably accurate, but a fantastic read. Somewhere between the candle button and "It doesn't rotate clockwise" I stopped laughing and started remembering.
Agreed. This could be a story about my last startup... A good reminder.
Re: Half-Baked Product
#104Entertaining, very AI prose though.
I disagree, this read very non-AI prose to me. No "its not x - it's y", or em dashes etc.
Re: Half-Baked Product
#105Earlier quoted context omitted.
I hope it's not the approach of using less water by not rinsing properly in the end, so people have to either eat soap or rinse everything manually afterwards, wasting far more water. I swear Bosch is so terrible at this.
Perhaps a match for the UK market? From what I've read they often don't rinse the soap off of dishes there (I wish I were making this up).
If there was enough soap residue to matter you'd notice the taste.
Re: Half-Baked Product
#106Earlier quoted context omitted.
It sounds like you're joking, but I've long dreamed of a different type of dishwasher. One that washes instantly. I don't need it to fit more than a single plate at one time. Just put something in from one end, and out comes clean and dry plate on the other end. Like a car wash. I am quite certain these exist already large kitchens and I seem to remember one from a school diner from maybe 35 years ago, but I've alway…
Restaurant dishwashers use an enormous amount of water. They require a hot water supply that’s much hotter than residential heaters typically supply. They require a more complete manual pre-rinse and scrub. They only accept kitchenware that’s made for them and destroy the rest. Restaurants cycle dishes a lot during a single mealtime. Homes don’t. I don’t think “I can’t wait 2 hours” is typically a real problem.
Those I've used in the UK aren't so bad, they're cold fill only with a heating element in the sump. It takes maybe 15 minutes to fill and get up to temperature at the start of a shift, after that each cycle is ~2 minutes.
The hot water is recirculated during the wash, the rinse uses fresh water from the tap with the excess going out an overflow. A little sump water gets replaced every cycle, but enough stays that it's back up to temperature before you've emptied and refilled it. There's also a small peristaltic pump to top up the detergent directly from the bottle.
Not much benefit in a home setting unless you fancy having it hot and ready 24/7 though.
Re: Half-Baked Product
#107Earlier quoted context omitted.
I gave up, how did this make it to page 1 jeez.
I've been experimenting with writing longer-form content. I do agree the main point could be condensed a lot and I'm not the a great writer by far. This is kind of a rant and really cathartic for me to write after working more than 5 years on startups. Just wanted to share it.
I loved it. It was cathartic to read, too. It's really a rather short story. There's no accounting for taste.
Re: Half-Baked Product
#108Has anyone ever experienced the alternative? to building products from scratch, growing a business, without the drama?
I did at peerdb
Re: Half-Baked Product
#109Reading this made me hyperventilate
Same here
Re: Half-Baked Product
#110Ouch, 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.
My personal take:
- you need aligned incentives across the board. Sales and accounts mustn’t promise what the company can’t deliver
- people need to defend their area of expertise whilst listening to what others are saying about theirs. For me this boils down to a division between technical and business focussed. Techies need to push for non-client facing technical improvements without making everyone ignore them every time they say “technical debt”, and they need to accept that sometimes you just build shit to get business through the books. Sales/accounts need to accept that sometimes the build budget is taken up with mysterious technical drives that will be worth it. When I say “must accept” I mean accept that it must happen some percentage of the time - each case still needs to be backed up by a business case.
- ultimately this needs to come from the top - founder(s) must balance these facts and drive it through the whole organisation, and in the article they didn’t