3 ms·
Every single point is spot on from my own experience. Subsequently many of the points won't sit well with the techie crowd.
by mbesto 14y ago
Every single point is spot on from my own experience. Subsequently many of the points won't sit well with the techie crowd.
- randall 14y ago"Subsequently many of the points won't sit well with the techie crowd." I'm not sure what you mean? Why wouldn't battle-tested well-worn advice work with the techie crowd? And who is the techie crowd? Programmers? Tech lovers? I'm just confused by your comment.
- tel 14y agoProbably w.r.t. handling market risk before tech risk and the general dangers of growing an MVP.
- ryguytilidie 14y agoThis was the first thing I thought as well. Honestly all of them seemed fairly common sense and obvious. Didn't really disagree with any.
- mbesto 14y agoGood point. I should have explained. Things like: "Stop writing code" "Don't worry about engineering" "It's a marathon" Won't sit well with technical people (mainly programmers, CTO co-founder, etc)
- nona 14y agoAs a tech co-founder, I thought this deck was spot on. Maybe it's because I've been through that experience that I don't feel threatened at all byt hat slide. "Stop writing code/did you talk to your customers yet?" - he's so right. I've had to trash a lot of iterations of our code because we didn't heed (or grok) this advice. I still think code is very important. But coding the best thing ever and it not being used is a nearly 100% waste of effort. I can imagine that developers who haven't gone through such an experience might feel different, though.
- deleted 14y ago[deleted]