Unsorted collection of things that should be documented

[ISSOtm]

The goal is for the sub-threads to contain idioms, techniques, etc. that it'd be a good idea to have somewhere.

I'd rather not open an issue for this, because a single linear discussion would be hell to follow, and one issue per small thing would be too noisy.

(Also I'm collecting these here to avoid losing ideas as they come, and not opening PRs because my focus is currently elsewhere.)

[ISSOtm]

Explicitly talking about the Thing.end - Thing idiom.

[Rangi42]

Encouraging users to skim hardware.inc for bit/mask/value constants relevant to what they need, not just using raw values from Pan Docs. (As shown by rgbds-live's tweaked version of the tutorial's Hello World.)

[Rangi42]

As an intermediate step between Hello World's db graphics and INCBIN, explain the use of dw `01233210 gfx constants (and even OPT g.oO# to allow dw `.oO##Oo.). This could aid understanding of how 2bpp graphics are formatted (two rows being interleaved across two bytes can be surprising).

[Rangi42]

Refactoring techniques. Notice when you're doing the same thing over and over again, and be able to extract it into a subroutine. More advanced, show how to push/pop registers to save/restore context when using subroutines. This could again be demonstrated as a short series of transformations to Hello World.

For more advanced users, there's optimization techniques (tail calls jumps, fallthrough, conditional calls+jumps) which aren't just for code golf but will regularly be encountered in real code pretty early on so should be understood.