TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Self-published Ansible book – 87k copies, 300k revenue, 41 revisions

165 pointsby lwhsiaoalmost 2 years ago

9 comments

0xbadcafebeealmost 2 years ago
I have mad respect for Jeff.<p>I really, really, <i>HATE</i> Ansible.<p>There is a special place in hell where all the worst of humanity go. It&#x27;s a room where you must build either Ansible or Jenkins infrastructure, for eternity.<p>Since Jeff is a professional, I am assuming his book does not detail the myriad ways in which Ansible is just fucking horrifically designed and a nightmare to use. Where the docs are usually missing or incomprehensible. Where important features seem to just not exist. Where barely anything works - but when it does, it works in a totally asinine way, that you will spend hours figuring out. Even if you&#x27;ve done it before. Or the nightmare that is trying to debug it, or use it with modern cloud infra and best practices.<p>Sometimes - <i>rarely</i> - Ansible is an OK solution. It&#x27;s more lightweight than its competition in the configuration management space, and it <i>can</i> be portable, if you add all the portability yourself. Well-maintained Galaxy stuff is quite useful and can save you weeks of time and years of therapy.<p>But for the most part, it and its Configuration Management brethren are better left for systems where someone is manually monkeying with them and breaking them, and you need something automated that also has some dependency-tracking to fix complex things for you.<p>The Cloud is still, sadly, mostly not immutable. So we still need shitty &quot;orchestration&quot; (Configuration Management) tools to maintain it. But I really hope they go away. I have never seen a Configuration Management tool that I have liked, because their very concept is automated duct tape.<p>(my bona fides: 20 years operating large-scale systems, including a reimplementation of DynamoDB, which was powered by OpenStack and AWS infra scaled dynamically by Ansible playbooks. I. Still. Have. Scars.)
评论 #36535952 未加载
评论 #36530518 未加载
评论 #36531974 未加载
评论 #36531276 未加载
评论 #36569348 未加载
评论 #36535371 未加载
评论 #36550939 未加载
评论 #36531763 未加载
thevagrantalmost 2 years ago
The revisions are key. It makes the book worth buying.<p>Many technical books are out of date within a few months of publishing and get no revisions
ramijamesalmost 2 years ago
The fact that the majority of his revenue goes to health insurance is abhorrent
评论 #36533341 未加载
评论 #36531020 未加载
glauconalmost 2 years ago
I was very surprised to read that even avoiding traditional publishers he&#x27;s only receiving 30% of retail in, at least, one case.
评论 #36529423 未加载
评论 #36532188 未加载
评论 #36530073 未加载
1473-bytesalmost 2 years ago
The insight into publisher royalties is interesting for sure. Though I will say regarding ansible, I just can&#x27;t like it. I rather use a python library like netmiko for configuration of vm&#x27;s.
vidarhalmost 2 years ago
It&#x27;d be a huge success to achieve this even for a traditionally published book with a publisher pushing. For a self-published one it&#x27;s extremely impressive.
oofnikalmost 2 years ago
I bought a copy.<p>Thanks, Jeff, for being interminably helpful.
john-tells-allalmost 2 years ago
I bought this! Got immediate value in that I found simpler ways to accomplish my business goals. Thanks!
madmodalmost 2 years ago
I bought this and it was very helpful!