> I learned a ton from my DE. Like, really, a ton. Before that, I had been writing on various blogs for about a decade, but writing online is all about being direct because most people don’t have time. With a book, it’s different. People made a deliberate decision to buy your book. Now, it’s your job to bring them somewhere valuable. And if that takes time (meaning more words), so be it.

I have a hard time with this point. It feels to me like a lot of books have A LOT of unecassery padding all over the place.

The example of taking 28 words and turning it to 120 is pretty good at showing this. The first paragraph is totally pointless - we are reading a book about 100 most common mistakes, obviously this mistake is very common, how did this increased the value?

Then we have another line that explaining what happens in the code, which is totally useless because the code is super trivial.

Then the code, with more explanations on the side as if the previous line was not clear.

And only after that we get to the crux of the issue.

I understand that book publishers feel they need to justify the price of a book by reaching the 300p mark in some or other way, but in my way this only makes the book worse.