Just a suggestion. In Section 11.5.2, I noticed that two subsections appear to overlap, repeating some of the explanations, though neither seems fully complete. I’d suggest merging them into a single, more cohesive subsection to improve clarity and avoid redundancy. This is not major and negligible; perhaps it would also be helpful to cite key problems of basic memory units (e.g., cache, scratchpad, etc.). Table 11.11 could benefit from a quick pass for readability, especially in terms of row alignment and visual clarity.
Originally created by @formlsysbookissue on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/946
Originally assigned to: @profvjreddi on GitHub.
Just a suggestion. In Section 11.5.2, I noticed that two subsections appear to overlap, repeating some of the explanations, though neither seems fully complete. I’d suggest merging them into a single, more cohesive subsection to improve clarity and avoid redundancy. This is not major and negligible; perhaps it would also be helpful to cite key problems of basic memory units (e.g., cache, scratchpad, etc.). Table 11.11 could benefit from a quick pass for readability, especially in terms of row alignment and visual clarity.
Thanks, this is great. Keep the feedback coming. I will improve it in the coming few days.
<!-- gh-comment-id:3214962360 -->
@profvjreddi commented on GitHub (Aug 22, 2025):
Thanks, this is great. Keep the feedback coming. I will improve it in the coming few days.
@formlsysbookissue commented on GitHub (Aug 25, 2025):
Thanks a lot! I'm happy to help improve the book. I really appreciate the encouragement, and I’ll keep an eye out for other improvements as well.
<!-- gh-comment-id:3219033919 -->
@formlsysbookissue commented on GitHub (Aug 25, 2025):
Thanks a lot! I'm happy to help improve the book. I really appreciate the encouragement, and I’ll keep an eye out for other improvements as well.
@formlsysbookissue Thanks so much for the thoughtful feedback—it was spot on. 🙏 I’ve updated the text, and if you have a chance, I’d really appreciate it if you could take a look. When I’m writing, I often get caught up in the details of each section, and since I revisit things after breaks, I sometimes miss overlaps or redundancies. Having your kind of feedback really helps me see the bigger picture, and I deeply appreciate it.
Please review the updated text, which should build into the live version here -- dev -- it usually takes an hour for these builds to pass all the tests.
<!-- gh-comment-id:3221476717 -->
@profvjreddi commented on GitHub (Aug 25, 2025):
@formlsysbookissue Thanks so much for the thoughtful feedback—it was spot on. 🙏 I’ve updated the text, and if you have a chance, I’d really appreciate it if you could take a look. When I’m writing, I often get caught up in the details of each section, and since I revisit things after breaks, I sometimes miss overlaps or redundancies. Having your kind of feedback really helps me see the bigger picture, and I deeply appreciate it.
Please review the updated text, which should build into the live version here -- [dev](https://harvard-edge.github.io/cs249r_book_dev/) -- it usually takes an hour for these builds to pass all the tests.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @formlsysbookissue on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/946
Originally assigned to: @profvjreddi on GitHub.
Just a suggestion. In Section 11.5.2, I noticed that two subsections appear to overlap, repeating some of the explanations, though neither seems fully complete. I’d suggest merging them into a single, more cohesive subsection to improve clarity and avoid redundancy. This is not major and negligible; perhaps it would also be helpful to cite key problems of basic memory units (e.g., cache, scratchpad, etc.). Table 11.11 could benefit from a quick pass for readability, especially in terms of row alignment and visual clarity.
@profvjreddi commented on GitHub (Aug 22, 2025):
Thanks, this is great. Keep the feedback coming. I will improve it in the coming few days.
@formlsysbookissue commented on GitHub (Aug 25, 2025):
Thanks a lot! I'm happy to help improve the book. I really appreciate the encouragement, and I’ll keep an eye out for other improvements as well.
@profvjreddi commented on GitHub (Aug 25, 2025):
@formlsysbookissue Thanks so much for the thoughtful feedback—it was spot on. 🙏 I’ve updated the text, and if you have a chance, I’d really appreciate it if you could take a look. When I’m writing, I often get caught up in the details of each section, and since I revisit things after breaks, I sometimes miss overlaps or redundancies. Having your kind of feedback really helps me see the bigger picture, and I deeply appreciate it.
Please review the updated text, which should build into the live version here -- dev -- it usually takes an hour for these builds to pass all the tests.