Also it's not really fun. It's a frustration ridden shit show. You spend all day solving complex problems instead of building business value.
A fine example of where the tradeoff ends is spending three weeks solving fundamental networking issues due to stack complexity and immaturity.
Good luck with that.
We do exactly that for a living here, we're essentially 5 people who are all CTO grade and have run our own companies. If you can fool us for a whole day you've deserved your investment, but I highly doubt anybody ever got away with that.
Most parties are aware of this and will do their very best to avoid going down that road, the few idiots that don't usually end up in a bad way though some may get lucky.
Cutting down the fluff you've just confirmed what I said. Basically when it does not cross into legal criminal fraud as defined by law you can't call it a fraud. Same as with taxes, especially corporate. One can be and idiot, creative, fraudster. The middle one is subject to interpretation and the amount of money involved. "Doing very best" does not necessarily mean not lying.
You can see this happen every day, plenty of cases that are fairly obviously - to a layperson - fraud end up not being prosecuted because it is hard to prove the facts and then there is the matter of intent. Still, nobody is fooled.
I hold myself to a far higher standard than my former employers.
Also, this is a fundamental property of innovation, innovation usually is made possible by the new and shiny things. I run the software side of a hardware startup, and I wouldn't have been able to run such a complex software system with such a small team if it wasn't for all the shiny stuff. Yes a lot of it is wobbly, but we're also comfortably a year ahead of the established players.
Larger pools of people, and cheaper infrastructure.
Not necessarily talent and cheaper scaling in my opinion.
It's likely that you would be ahead of established players with old, not shiny technology as well. Established players have an inherently harder time progressing in most circumstances and an entirely different maintenance burden in pretty much every layer of their product. Shiny, new technology accounts for much less than people think it does.
Does this even matter though? Shitty technology choices don't always translate to poor business outcomes.
Of course it doesn't always play out like that (to every rule there are plenty of exceptions), but investors don't like to be associated with companies that fail or that blow up their reputations either because it makes their exit that much harder or even impossible.
I've seen investors that took the responsible route and made fixing major security issues or other undesirable elements of the target companies a condition to investment and typically these investments succeed in the longer term, not in the least because they cleaned up their act and could then turn that into a USP relative to the rest of the field.
Even so: better invest in a company with a mediocre product and a stellar sales team than to invest in a company with a fantastic product and a mediocre sales team. The first one will get you a better ROI, and tech can be fixed post deal.
Thank fuck I was just a contractor and not a founder or shareholder.
Why? Most companies fail due to a lack of product market fit not because they picked the wrong software stack. Hence investors time is better spent on company outcomes and not micromanaging whether the backend team is building using Java or Rust or whatever’s trendy.
Many technology and process choices are just style and preference, absolutely. Others have a material impact on the effort and time to ship a feature. (I’ll leave examples as an exercise to the reader; I imagine any example I used could turn into discussion of “ah you’re doing $FOO wrong.” I suspect this tendency entangles with why these choices seemingly frequently impact business outcomes, from my perspective.)
If you are an early stage investor and you are writing lots of checks to cast a wide net do you really have the time to do that level of due diligence? Presumably a quality founding team and a decent demo is enough to tick that box.
If you are a series A or above investor, does it really do anything to provide this advise after the fact?
I image that the assumption is that if the company is successful you can afford to bring in more seasoned people to fix things. At least that’s what I’ve seen on my travels in the Bay Area.
At no point should "fun" be a line item when determining what technology to select in a high stake environment.
We are in finance and we picked the most boring technologies we could find. Most of our stuff doesn't even talk to the network stack. I can't imagine running our transactions, with their piping hot PII, through the labyrinthine monstrosity that is modern "best practices".