$10K in sales
by Nick HaskinsThis project has been a roller coaster of emotions. At one point I thought about just shelving it all together, but I decided to push forward.
In 90 days this book on Ruby on Rails as made $10K in revenue.
If you have doubts about your project, or on the verge of quitting, don't! You could be so close. There's always going to be friction with whatever you're pursuing, but the key is determining what's worth fighting for.
-
2
Congrats Nick!
-
1
Great book! Really helped me understand how to get somethings working together that I didn't really understand how to do before (or why they worked).
-
1
Hell yes!!!
-
-
1
Hey, @nphaskins, I've ordered your book. Pretty nice content, but...
I've tried to contact you via twitter, email, website, anything and got no answer at all - and you are daily active on Twitter, as I thought that maybe you are in some remote location with your Camper. So taking into account that you probably don't have hundreds of message daily, and your product is not $1 value, I think would be nice if you have some time do some support of your product/selling platform.Some feedback about book:
- You have provided code snippets, but they don't have any numbering same as captions of images in book, so it is hard to check every snippet, so maybe include caption with snippet numbers in the book?
- You mention some things in the book which are not implemented in the example app at all - ahoy tracking and displaying later. I'm not saying full implementation but some example.
- The app does not include a test at all, I'm not saying that it should be 100% tested, but you have a custom approach for writing some things, would be nice to share what is best way to test it etc. I mean if you are showing the best practice of app design, would be nice to have test included as well to see your approach.
Maybe these are not most important things, but i think are nice to have.
I think apart from this book is very nice:) It is always nice to see some production best practices:)
-
1
Hey Baaart! Thanks for the feedback!
I have a community forum that I've been answering questions on just in case you missed that:
https://playbook-thirty-nine.mavenseed.com/community
- You are right!
- Yep that's correct. I didn't want to make assumptions about the app. Not everyone uses tracking. The purpose of the app was to show the basic implementation of the most important concepts like service object use.
- Correct! I'm a one man show. I don't use TDD, nor do I write tests. This is more suitable for teams, not solo developers.
Happy to answer any other questions!
-
1
Thanks for quick answer:)
I will definitely check community forum.
#2. I understand that app is just help to the book, but still, having even basic example of the concept within the whole app is I think better than code snippet. For example just one event type and very simple dashboard.About #3. I'm one-man show very often as well, and unfortunately, not having test and changing bigger and bigger applications, makes regression errors more often as the application grows. And if you will want at some point to sell your app, or outsource some stuff, tests are very good, not to mention any bigger refactor:)
Especially if you are not looking at your code for some time - I know that you are involved in multiple projects, so hard to believe that you have a perfect mental model of each of them in your head all the time:)I will do some post in the community forum, so we will not do offtopic here:) I have some suggestion, what else could be included.
-
1
I'm not a developer but know how hard it is to write a book then hit $10k in sales. Nice work Nick!
