But that's bad, right? It's like you're making the "Landing on the moon" documentary in the 1920. People don't want to hear about 40 years of mistakes, they want to hear about the end conclusions and you won't have any to give. That's why success-story books sell, but you don't see a lot of "will-try-to-do" books.
I should hope not. I'm trying to think of a situation where a developer wants to document a process (ANY process. In this case: building a profitable product) and it would be considered "bad".
> That's why success-story books sell, but you don't see a lot of "will-try-to-do" books.
This is a blog, not a book. Will-try-to-do blog posts are incredibly healthy exercises for the author/do'er and usually provide helpful content for the readers (if the author follows through and documents his or her thought process).
I'm not sure what point you're trying to make here, and (to me) your comments and tone sound dismissive. This fellow has nothing to sell -- it's an exciting endeavor that the author wants to document.
Tell you what - I'll get back to the topic & blog in 1 year time. I'll chat you up on HN and we'll redo the discussion. I'm willing to admit my mistake, but if they jakub ends this project in a-la-tim-ferris "book about selling books", I'll call my hunch correct - that he just played the community for self benefit.
If the project is left-for-dead, I'll consider my second statement about drawing attention too soon correct.
On the other hand, if the project is showing progress and does a fair writing - I'll gladly apologize to jakubgarfield and to you.
Yep, I'm trying will-try-to-do approach. It gives me some order and discipline and I could keep a record for myself. And I'd like to think that someone else would be interested in my plans and steps and potentially benefit from them.
