I've been building out my Jamstack book (https://cutintothejamstack.com/) and the preview version (which constitutes about 30% of the book's outline) just clocked in at 300 pages 🤯so I'm rethinking what's important and what isn't.
What parts of the programming ebooks you read are most important to you? Setup? Theor? Just code?
What parts do you feel are unnecessary?
The best way I've seen books laid out is having all the core concepts in a section, and in each section have example code on the right and on the left the explanation of the code along with a little bit of context and theory, for more in-depth theory, condense it, make writing style simple for a Jr. dev to understand, but short theory and code samples (good ones, not using cars and fruit as examples, make it business oriented since most devs work for businesses). It's hard to find these books, but when I do, I get them, also a great publisher that does this is Murach books, you should check out their format and copy it, problem is they only have a few areas they cover.
Great feedback, thank you!
My definition of perfection can be summarized as simple, concise and valuable.
React's documentation is a fantastic example. It's simple enough for a junior dev to understand (not many fancy terms, great pace of progression). But it also provides enough value and conciseness, which is appreciated by more experienced programmers.
Compare to Angular's , which is full of programming lingo and obscure "explanations" that impress no-one and make it overly difficult to figure out what they hell they're trying to explain.
Great points. I definitely try to teach in plain English as much as possible, being very clear and to the point. I hate it when I have to look up a dozen terms to understand something that should be simpler.
To be honest for niche books I think theory is far more important than code as you could find plenty of it on web.
Say JavaScript, one can find loads of online tutorials/code on web for specefic tasks however a descent theory on prototypes or other core concepts are difficult to come by.
Again my preference depends a lot on the topic, but I generally tend to like books having loads of theory (also keeps me from being tempted to read code and skip over).
Good to know. What about books on frameworks and such? Does that still apply...in other words, you'd want more conceptual and general information about how to use the framework (high level patterns and paradigms), rather than just code on how to do tasks?
Well frameworks are a different ball-game.
If I may recommend could you give a quick read to some scheme books like SICP or any of the Racket books.
Additionally Pragmatic Programmer books are also enjoyable.
But again you are kind of putting a way to build applications using React and Next.js so keeping an appendix of code would be beneficial (maybe something like xv6 on OS core fundamentals)
Sorry the comment may seem scattered !
Eagerly waiting for the book !
PS: Do you recommend some books like the one you are writing ? Mostly in e-book format.
Thanks so much! Love the Pragmatic Programmer books.
I honestly don't know other books like the one I'm writing. That's why I decided to write it. If you find any that are similar definitely let me know.
By the way which text editor are you using for writing your book.
I often feel word or general text related document quite cumbersome while writing a document containing both code and text along with photos.
Though LaTeX may be a solution but I was looking for something with the ease of text editor but in which writing code is also easy (in terms of no auto capitalization or spell check on code).
I often end by feeling frustating while taking notes on a book.
I'm using Ulysses:
https://ulysses.app/
It lets you write in markdown, so creating code blocks is as simple as adding a double backtick - so spell check won't get in the way.
It's got pretty good syntax highlighting, for JavaScript at least. I've exported from Ulysses into a Google Doc and PDF, and it preserves the code formatting and highlighting well enough. It also exports to markdown, docx, mobi, etc.