2 ms·
Besides being very useful, the X volumes helped O'Reilly & Associates grow, which was great for our field. O'Reilly became famous for the "animal books", which
by neilv 4y ago
Besides being very useful, the X volumes helped O'Reilly & Associates grow, which was great for our field.
O'Reilly became famous for the "animal books", which were often indispensable bibles for a software technology.
Today, many of us will attack any problem via StackOverflow or Googling (or laundering open source with LLMs), framed as how to do a very particular something in a stack of software we understand maybe <1% about. (And sometimes we get certifications by studying for a test, as a way to promote our careers.)
But if we wanted to actually understand some level better, such that we don't have to ask as much "How do I do this specific thing, just tell me what to type?", but instead "How does this thing work conceptually, and what are the interfaces?", the documentation we need is usually poor and hard to discover, or nonexistent.
Example: At least one major cloud provider apparently has huge trouble keeping their documentation complete and accurate, and also generates a lot of noise of low-quality documents. (Maybe someone ran the numbers, and found that good docs isn't needed to attract and retain customers at this point of their market position, and poor docs means they sell more support contracts?)
Fortunately, there are still great technical books being published. (Example: if you're an experienced systems programmer wanting to use Rust, IMHO the first book you should read is the Blandy, et al. "Programming Rust" animal book from O'Reilly, and then keep it on your virtual bookshelf forever, for reference.)
I hope that "StackOverflow methodology" and LLMs don't further hurt the market for books and learning, and that we'll continue to see great books from O'Reilly and other publishers.