4 ms·
You need to write it a few more times so it is clearer. Also I’m sorry if this is harsh, but technical books should be written by experts who have taught the su
by sglisp 5y ago
You need to write it a few more times so it is clearer. Also I’m sorry if this is harsh, but technical books should be written by experts who have taught the subject for many years and understand the best way to communicate the subject matter. Otherwise better leave it as a series of blog posts.
- phoe-krk 5y agoI don't understand the first sentence; do you mean writing it several times in succession and completely discarding all results but the last one, or more like an iterative process that actually looks back at what was written previously and improves upon that content? Also, I don't think I can really make use of the latter part; it implies that only people who have taught the subject for years are qualified for writing technical books, which - given that I am not a teacher and likely won't be one - gives the resulting vibe of "just give up" without any possible improvements. I can't make any use of that in order to improve my current or future writing.
- sglisp 5y agoTake a few weeks break between each write, you will start to see areas that are clear and those that you will not like. Connect the flow of paragraphs and chapters to each other - hard to see all this when you first write it down; but after taking a reasonable break - you will start to see which areas to change. I get your point on not being a teacher, but I would recommend doing it as blog posts then and not a book, a book implies something much more. Or maybe I’m just old school and not for the current times. After all, there are countless of ebooks of questionable quality on various programming topics.
- phoe-krk 5y agoOK - thanks, I'll keep that in mind for my future writing and for the second edition of TCLCS (if it happens). The first edition was written pretty fast (a total of six months?) and it did not have enough time to have enough of the "few weeks breaks" that you mentioned, so I can understand that it suffers from lack of text maturity. I'm curious about "a book implies something much more" though. I have seen multiple series of blog posts that then grew to the point where they were actually published as books. What's the difference between the two when one wants to tell them apart via their content? What's this implication that you mention?
- sglisp 5y agoAt least for me, those blog posts that become a book are not of very high quality. Very bad actually. For example, books (at least used to) have editors, and reviews by multiple specialists in the field. I can’t think of distinct step between personal writing and something publishing, so I cannot add meaningful comments to your question.
- phoe-krk 5y agoI've had the book reviewed and edited by several people (mentioned in the front matter), and you're not the first person to complain about the long-winded style. This likely means that we collectively screwed up with regard to the English layer of the book. Thanks for the feedback; I'll let my reviewers/editors know, get this fixed in the second edition, avoid doing that in my future writing.
- amanaplanacanal 5y agoPerhaps you could link to one of your books for an example of how it should be done?
- jhgb 5y agoWhile I think that arguments by sglisp could have been much more persuasive, I also tend to think that arguments along the lines of "If you don't like it, show us your own work" are disingenuous. One does not need to be a good baker, or even a baker at all, to recognize and reject stale bread.
- guenthert 5y agoNot many books pass this high a bar. CL is special, but many technologies won't remain relevant for many years -- how would we ever see books about those?