robfitz
Joined 19 years ago
Joined 19 years ago
Very interesting to see differences between the "mature" AI coding workflow vs. the "mature" image workflow. Context and design docs vs. pipelines and modules...
I've also got a toe inside the publishing industry (which is ridicilously, hilariously tech-impaired), and this has certainly gotten me noodling over what the workflow there ought to be...
The "good" spots are highly desirable and usually privately owned (or on a very long-term lease), and you often need to buy a boat to get the mooring spot beneath it. (A buddy of mine in London ended up with 3 boats while upgrading his mooring spot.)
Another options is to vagabond it, where you move your boat to a new area every week or two -- this is usually unserviced, so it's more like camping, but lets you use unofficial spots and is free.
(The last option is to find goofy loopholes. E.g., in some areas of the Thames, you can create a nesting habitat for an endangered bird on your boat, and then once the bird settles in, they can't force you to move, since doing so would destroy an important habitat. Sounds stupid but a surprising number of permanent city boats are there on some sort of loophole.)
It's true, as another commenter mentioned, that the expected result of most nonfiction is zero. But in my opinion, that's largely because most nonfiction today is built like software in built like software in the 90s, without proper user-facing iteration and refinement. I wrote a whole thing about it[2].
Books created as a cynical cash-grab are already negative value in terms of time investment and opportunity cost. I think they're only worth getting into if you care enough about it (either the end result or the activity) to do it regardless of the money. And then, only once that's true, perhaps start looking for ways to optimize it as a process and product.
[1] https://www.amazon.com/stores/author/B00J77JH5G/allbooks [2] https://helpthisbook.com/robfitz/useful/
Interesting to see how long even the industry insiders failed to take YC seriously. And then once it was working, they flipped immediately to complaining that YC was too powerful and too influential (unbeatable network effect, seed/A valuation inflation, and so on).
I also remember the constant naysaying about scalability and batch size. Our batch was ~19 companies. People kept naysaying, "Well this model is fine for now, but it will never work past 20 teams."
PG would always reply with something like, "Yeah, they said that when we had fewer than 10 teams also. We aren't thinking too far ahead; each batch, we just find the next bottleneck and solve it, and we'll see how far that gets us." Which evidently got them pretty far. A lovely example of doing things that don't scale.
As a side note since you're here, I'm super psyched that you've taken the time to share what you've learned in your new book -- it's the next one up on my list for serious study, and I couldn't be more excited about it. Based on the reviews so far, it looks like you've written something really special and that I'm in for a real treat. Can't wait :)
To a lesser extent, I also didn't exactly expect this to hit frontpage, so I'd sort of assumed that the only people who would see it were people who already knew me.
I'm still not sure about the answer to that, but this has at least prompted me to give it a proper think and decide whether I want to try to appeal to "the world" or just stay focused on my own little orbit. No idea where I'll end up, but it's an interesting question, and I appreciate you giving me the nudge to take it seriously.
It's also quite nice to know that if you happen to run into an unmarked sandbank, you'll only have to sit there, and not sit there sideways ;)
E.g., During a customer interview where I'm trying to understand what they've done (and predict what they'll do), I have vanishingly low confidence in their self-predicted behavior. So I prefer to try to look at what they've actually done in the past, talk to them to understand why they did it that way instead of some other way, tease out the invisible data (like what they tried or researched but didn't continue with), and then come to my own conclusion about how that's all likely to extrapolate.
But in terms of understanding and ascribing purpose to my experiences? Or understanding and empathizing with a friend or stranger? Or sending a message out into the world in a way that can stick and spread? In that case, it's kind of a subjective thing to start with, and it's all about the stories. (To clarify: not intentionally fanciful or fictional stories. Just "stories" in the sense of how we tie all these things that happen into something coherent and ordered.)
That was kind of a non-answer, and I'm sorry I can't be more helpful. I only understand a very, very small number of things. (Three, I think, although I'm working hard on understanding the fourth.) Apart from those few narrow domains, I'm just fumbling through it like everybody else.
Now: chipping away usefulbooks.com to support indie authors and maybe solve some pet peeves with the industry.
Also wrote three books about stuff I've learned along the way:
1// The Mom Test about how to talk to customers and learn what they care about when everyone is lying to you (momtestbook.com)
2// The Workshop Survival Guide about designing and delivering better educational workshops (workshopsurvival.com)
3// Write Useful Books about how to design and test nonfiction books as if they were a problem-solving products built for back catalog recommendability (usefulbooks.com)
X// Book-in-progress is about Outcome-Oriented Communities (early ideas on that at robfitz.com)
[email protected]
*