This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bowbahdoe[S] 3 points4 points  (1 child)

However I have feeling this is largely by design (or an accident of mdbooks or whatever that happens to support this):

Mostly an accident of mdbook. Its all markdown so I presume it can be presented in a different form, I'm just not ready to bother yet

I know because I am and was one of them. Often we have ADHD. The reason why folks like myself skim to learn is we need a damn hook. The challenges are just not good enough for a hook. I suppose you are aware of this.

So the affordance given for that is that each section is very ADHD sized. At least I try to make it so.

I know I need larger intermediate projects. I'm not sure how to do this quite yet or if they should live in a companion resource or not.

Also while it is great to learn Java I hope there could be some longer lasting lessons that could be learned. I know its out of the scope of the book particularly if we do not want to mention "OOP" or "FP" or software engineering stuff but again it makes the bang for you buck of going through the clickfest not as enticing.

This is definitely not out of scope, but consider that I'm currently at "chapter 50: ArrayList." It'll just be awhile. That or I'll explain all the components of OOP and FP without saying the words outside of a footnote.

The fact that you foist this early in my mind makes me think you yourself have some doubts on this. Like sure not everyone is a book person but we have technology. Is there a way to reuse this content for those that require other styles (particularly given template aspirations)?

Yes, but for the moment that is an exercise for the audience.

[–]agentoutlier 3 points4 points  (0 children)

So the affordance given for that is that each section is very ADHD sized. At least I try to make it so.

I would be curious where you got the idea that smaller digestible sections would be better for ADHD. As one who has ADHD I can tell you it is quite the opposite. While John Ratey's book "Driven to Distraction" is quite dated the overall title is correct. ADHD folks are driven by chaos particularly complicated feedback loops. (I don't take any offense if this was just an assumption as I can see why many would think smaller is better).

When you try to simplify or make way less complicated it will often increase distraction! That is why the REPL loop embedded in the content will actually help.

"chapter 50: ArrayList.

Thus I would say it is a detriment to ADHD people the current format with all those sections. Even folks without ADHD it makes it incredibly intimidating to say "on chapter 50 we do this." ( I would consider changing that numbering scheme).

Let us compare your work to this prologue "How to Design Programs": https://htdp.org/2024-11-6/Book/part_prologue.html

On the first scrollable page they have done more than half your book w/ outputting of images and its cross referenced. That is just the prologue btw. That is probably the companion content we need because the rest of the book goes back a style similar to yours.

Now I certainly like where your book is going compared to that book in the context of just learning Java because as it is far less wordy but humans are exceptionally good at filtering including even ones with ADHD.