The Pivot

Just because you learn from certain businesses doesn't mean you need to start off selling to them. Many businesses start by meeting the needs of smaller businesses and work up to larger ones.

A slight spin on that assumption that I've seen in some lean startup materials is to assume that "software delivery is constant and guaranteed" - which is used to help move the identification of risk away from technology and towards the business viability.

In that case, I think it is somewhat useful, but speaking as a software developer - it is very rarely the case that a software project goes as smoothly and reliably as a fancy pitch deck makes it out to be. It is easy to say things like "small iterations", "continuous delivery", "move fast", etc but much harder to, you know, do them. Any old team thrown together off the street is not going to have that skillset to achieve that.

I don't think it entirely discounts the ideas or concepts, but I certainly gives me pause.

It's an important point, and it's not just the software industry. If two companies X and Y provide exactly the same or similar service, but company X's user experience is superior, it will probably win out. Consider that Dominos just released the ability to order pizza via a voice operated app. Their pizza is not going to be any better than it was the day before, but by giving people a (supposedly) better way to order, they may be able to take market share away from Round Table or whoever.

Just to add to your first point: it's hard for people to recognize that there can be a huge difference in ability between the best and the 20th best team. They can both be great, but the 20th best team is much less great than the best one.

This goes against most of our intuition (at least, mine), because there's essentially no difference between the 10,000th and 10,020th most talented teams. But it becomes obvious when teams are put in repeated direct competition with each other. e.g.: how many people expect the US (ranked, I think, 13th in the world) to beat Germany (ranked 2nd) in the world cup?

  It's a lot easier to say you will do anything to 
  succeed, and act the part and struggle, and listen 
  to your investors like they're bosses, and let your 
  startup die out, while going through the motions, 
  than it is to be relentlessly resourceful.

Well said. The rest reads like the ten (well, maybe four) commandments of Please Fuck Off And Die with your bullshit-as-a-service, viral social mobile app.

  - platitudes about there being lots of talented teams

  - a founder or two, not that dedicated but there because 
    he/she isn't sure what else to be doing

  - startup vanity projects
  
  - lack of modesty to actually sell

To that last one, I'd also append "a peacock's hubris that their shit is so hot it doesn't need a pathetic and grovelling or disingenuous sales pitch."

That's a double edged sword, though. Everyone knows that a shitty deal is always preceeded by a hard sell, or cold call, even though not all hard-sell sales pitches/cold calls necessarily package dog shit.

This is the MBA shit list though. There's also a version for developers which invloves being an aloof, detached, aimless, defensive coder constructing an opaque fortress of code out of a want for job security, or over-engineering out of a cryptic brand of obstinate vanity or morbid curiosity.

And then there's the ivory tower developer that sows the seeds of confusion into every meeting, phone call and conversation because more often than not, the developer possesses a keen awareness of the total technical ineptitude of the stakeholders, who may in fact suffer actual intellectual disabilities, or might just be completely out of their depth in a field far more complicated than they bargained for.

Coming up against evil developers is like fighting a lich king commanding a pack of tarrasques. You will be bled dry by them, and transmogrified into a ghoul.

Consider it a situation not unlike being brought to a police station for questioning without a lawyer. Retain an expert, who is assuredly on your side and knows the law. Even if you are a lawyer, don't default to the idea of representing yourself (especially considering security concerns and crypto). A second pair of eyes, formal QA and testing, and sometimes an entire community is required to professionalize the fruits of many technical disciplines.