> For some topics though, it's not just a matter of time savings. I'm working on a topic now that doesn't really have many useful books, so I'm having to read technical specifications produced by industry groups, which lack context and are pretty opaque. I'm missing having a book that explains these ideas in a coherent fashion.
I know a couple of tech book authors, and this is how they all got started on their first book. :) There was no good book, they did all the work of becoming an expert, and then curated their learnings into a book for others.
There are two groups of engineers - if they embark on opaque documented problem - one will write a book and share everything they learned, the other - patent the ideas and make sure nobody else uses them without paying.
I know a couple of tech book authors, and this is how they all got started on their first book. :) There was no good book, they did all the work of becoming an expert, and then curated their learnings into a book for others.