Everyday Golang
gumroad.com
gumroad.com
Also, no returns policy, no samples, nothing. Never.
> Offers and discounts: > Not entirely satisfied? Ask for your money back within 7 days of purchase, no questions asked.
So far 82 sales, and positive reviews on Twitter.
The base price is 50 USD today, 79USD normal price, find out more about that here:
https://blog.alexellis.io/i-wrote-a-book-about-golang/
The 250 USD tier is for 5 people, not for one. That's why it's called Team Edition. So it's a saving of 145 USD vs buying individual copies, or saving 395 USD vs 5 copies of the Premium edition.
To be fair, this is the first time I've tried 79USD, but when you talk about page numbers you are missing the point.
If the content and examples are useful to you, then it's worth much more than 79 Dollars and today's launch price is 50 USD, so far 82 people have bought at that price and a few on the Premium tier.
I posted a link to a blog post to the other posters, have a read of it where I mention price. See also DynamoDB book's pricing - https://www.dynamodbbook.com/
Most of the chapters in this TOC are absolute basics, that would be covered in any Golang book (e.g. writing HTTP endpoints, fetching JSON from HTTP endpoints, using goroutines, etc). And most of the leading books on the market are around 500 pages, give or take, and cover much more.
One-hundred pages with 15 code examples is basically ~15 blog posts, packaged up in eBook form. If you're able to convert that into $5-10k or more, then that's amazing! I should self-publish a small book myself. I would not have seriously considered a project like that, because quite frankly I just don't understand the target audience. Why people would pick boutique self-published options over an O'Reilly or Manning book, etc.
Here we are also talking about A4 pages, in an epub format it's 180 pages on a standard font size, but we digress. More is not more, less is more when it's useful and you can learn something and apply it.
I've reviewed several of the books you've mentioned, and have them on my desk. They are huge and unwieldy, with much of their content available in the Go docs or standard library.
This book is use-case driven, and some of those examples are for different skill levels. Certainly, editing is likely to be more thorough with a large publisher, but the feedback loop and the ability to iterate are an advantage here.
An example: the part of unit-testing in Go (originally a blog post) was referenced in the Kubernetes documentation as an example of how to learn to unit test.
Serverless For Everyone Else has sold ~ 450+ copies with a similar structure and very high ratings. It's not about page count.