@between_team@shashcoffe@jgrenzemann Doing things that don't scale is a classic startup mantra, but I've always found you have to be careful not to incur too much tech debt - if your product is the tech, it better work as you scale! The user aquisition and process doesn't have to scale at the start
@shashcoffe@jgrenzemann@daniel_baum That's definitely true. In the tech side if you hardcode/scrap together everything you won't be prepared for growth.
@shashcoffe@daniel_baum@between_team yeah sure - but on the otherside: how many team/companies do I know that focus so much on "beeing prepared for growth" and it newer comes, because they move too slow and don't get any momentum on the market side. I'm quite aware that this isn't a yes/no black/white question - but anyhow: once you have found out what to build (product/market fit) its more likely for you to raise more money (and worst-case: begin from scratch with dev). But the otherway around is worse - no customers, no money - but very very well written code ;)
@mouna_selmi True, true. Founding a startup is like climbing the everest. In such an adventure you want to have folks around that you can trust/rely on - even when things get nasty and the relationships gets under pressure.
"What I tell founders is not to sweat the business model too much at first. The most important task at first is to build something people want. If you don't do that, it won't matter how clever your business model is."
For me:
"The word 'try' is an especially valuable component. I disagree here with Yoda, who said there is no try. There is try. It implies there's no punishment if you fail. You're driven by curiosity instead of duty".
https://twitter.com/paulg/status... - where he quoted me ;-). Was kind of awesome to be noticed by someone you have been reading and following for years.
Neuton AutoML