Shutting Down My Baby
fabiandietrich.com
fabiandietrich.com
Lesson learned I hope: It seems to me that the author wanted to be an entrepreneur foremost instead of solving an acutal problem. What the author wanted was their own startup with the accompanied startup experience, and so the "problem" was rather secondary and maybe even thought of after that desire?
I mean:
> It turned out that writers actually like to write themselves, and the current level of technology was just not good enough to make them really satisfied with whatever output they got from my product.
Really? It continues:
> Even though nearly everybody on this planet has heard the “machine learning” buzzword by now, the less technologically experienced hobby writers that I talked to didn’t have a real understanding of what they could expect from my product. This fundamental knowledge divide really made me think about how to reach this group of people.
Again, this really gives me the impression that you're not trying to solve a problem. You're "thinking about how to reach this group of people" to sell them your dream of having a company, not something they want or need.
I mean, to a certain extent, running a startup often means convincing people of a problem they didn't know they had. I think a more accurate simplification of their post mortem is something like:
"I had a problem and solved it for myself. I thought it was a problem others had, but it turned out most people didn't think it was a problem, and I couldn't convince them otherwise."
It feels like a mature version of this product would be ideal for publishers and other customers of authors.
However I suspect we are not there yet technological wise and therefore he was unable/didn't attempt to sell the product to these companies.
To do what? Auto-generate new books about a particular series when the writer doesn’t want to write any more?
Possibly with some prompting help from a ghostwriter?
This is actually a very effective approach if you have something to offer they both want & need.
Exactly. It's like inventing a knitting machine and reaching out to hand-knitters. You're offering to destroy through automation the thing they enjoy. The right market to reach out to would have been consumers of writing.
To the extent that this already exists, it's used to create blogspam for SEO purposes. AI-generated text is going to make the next generation of the internet so much worse.
After reading this line, I literally went thank goodness it flopped.
I don't want to read autogenerated content no matter how good it may be.
Yes, AI can be useful in a lot of domains, but autogenerated content to read? No thank you. I like to experience what the writers themselves come up with.
And what if the writers change their style?
> AI-generated text is going to make the next generation of the internet so much worse.
This kind of thing combined with global warming would make for an interesting future.
AI can put out hundreds of thousands of articles telling you why global warming is a good thing. After all, nothing has meaning to an AI: not its own survival, and certainly not yours.
In other words you can predict the outcome of someone else's endeavour, because of your own experience, you could tell them your prediction, but they'd go ahead anyway because experience has to be lived, and is seldom passed from one person to another.
This startup post-mortem seems to happen almost weekly, and despite all the literature (formal and informal) it seems like the same mistakes are made over and over again.
To the author I say, well done, you are gaining some valuable experience, and learning some valuable lessons. By all means get a job to replenish empty coffers, so that when you do another startup you apply those lessons learnt (and if that fails you'll have more experiences to share.)
For my own journey I got lucky. We bootstrapped the business with no investment, writing custom software, until we found our product niche and pivoted into selling that. I have no idea if that strategy would work today - and alas the experience of our mistakes (of which there were many) is unlikely to be transferable.
Good luck! (seriously, a big of good luck really helps a lot...)
This is true in general. People still go ahead because their thinking is your situation is different than mine, and also that this time it will be different since its not you but me who will implement it.
Yes, it's impossible, but imagine the possibilities if he succeeds... [1]
[1] from the sheep who thinks he's a bird, and is teaching the other sheep how to fly..
I suppose in rare (jargon- or abstruse knowledge-heavy writing, and activated only by ctrl+space, etc) it might be useful.
Here's what I would pay for: something that would generate a structure / a detailed lists of scenes, given a list of characters and a theme, or the beginning of the text, or maybe from scratch.
I'm an amateur writer, self-published my first novel last year, which is doing reasonably well. I like to write scenes, dialogue, interactions, and given a scene context, can sometimes write fast.
But I have a hard time coming up with what to write, what scene to write, what comes next. I generally know where the whole story is going and how it's going to end, but what needs to be written now, I don't know.
I suspect many authors are in the same situation.
I asked him: an app for rhyme suggestions? He said yes, but that it was more for suggesting ideas.
Not that an app wouldn't be useful to someone, but if they need rhymes today, bookshops (and websites) have an MVP already.
[1]: https://en.wikipedia.org/wiki/Walker%27s_Rhyming_Dictionary
Rhyme dictionaries are significantly older than that. https://en.wikipedia.org/wiki/Qieyun
(Ironically, old Chinese rhyme dictionaries have considerable scholarly importance because they allow us to determine whether old Chinese text probably rhymed, a task the text itself does not help with. They are less valuable for the other direction of retrieving a list of rhymes for a particular character.)
Yup, that's a first mistake, no? Shouldn't one build projects for others? It's a fine distinction, but getting that first customer is so important (or so I've heard).
If it turns out not to be an untapped niche though, or not a good one... ugh. ;)
That's also how it worked for my product I'm very successful with (I built it for myself).
If you try to think what other people would use and build a product around that you will most likely fail.
> Yup, that's a first mistake, no?
No. The anti-pattern here is
"Build something you think other people would want because you would like it."
transforming into ->
"Build something you think other people would want because you would like them to like it."
(there's a subtle change)
In three or four startups I've been associated with, this was going on. In psychology it's 'projection', and I think many young entrepreneurs fall into it.
Indeed it's a common problem in digital technologies - the development of a feature by one group of people, who've become convinced another group want it, so push it against all evidence and market behaviour.
Innovators can get enchanted by their own idea, and really want to be "creatively validated" by what they see as an "audience". This has gotten worse as software startups took on the characteristics of a "new pop music" business.
Or, (with existing semi-succesful companies) they get mixed up in unconscious ulterior motives for wanting people to adopt an idea (such as displacing another product/paradigm they dislike, or effecting some kind of control over users (DRM etc).