1,228 karma · joined August 27, 2013
Pro Tip: write a tech book to advance your career, to scratch an itch, to learn by teaching. Don't write a tech book to make money. I don't have the exact numbers off the top of my head, but Go In Action is considered a successful tech book and it hasn't made enough money to make it worth the time invested if money was the only motivator. We donate all the royalties to a non-profit (Go Bridge https://gobridge.org ), so that was never our motivation... but I'd be seriously disappointed if I expected to make a living doing tech books with a traditional publisher. Maybe others who self-publish can chime in on how that's going for them.
Glad I did it. Wouldn't do it again :)
Sorry I couldn't resist.
Interesting to come across this article here. So few people have heard of distraction or seen someone with active distraction happening.
Note this is a toy deployment, not actual content. Don't expect all the links to work or any content to be accurate or relevant :)
[1] https://spin.brian.dev/blog/2022-03-18-caddy-zero-downtime [2] https://github.com/bketelsen/wasmblog [3] https://github.com/fermyon/bartholomew
https://www.npmjs.com/package/json-graphql-server
Some quick recipes to use both: https://www.cueblox.com/recipes/