mirror of
https://github.com/harvard-edge/cs249r_book.git
synced 2026-05-08 09:57:21 -05:00
[GH-ISSUE #810] Inspir. from Prev Textbooks - Add Exercises #5549
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/cs249r_book#5549
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @huskydj1 on GitHub (Apr 14, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/810
Adding more exercises might help tie ideas together and make throughlines more visible.
Pseudocode
For instance, this section might benefit from an exercise about pseudocode and how a process like this would be implemented in practice (for instance, prompting the reader to write pseudocode like from the original paper, shown below).
Tying back Concepts
Some ideas feel very high-level, and it could be helpful to draw them back to fundamentals explained earlier. For instance, how do the different memory management strategies affect the total memory equation?
From Stanford's course, drawing back to real-world examples
This exercise draws ml system requirements to twitter's trending hashtags. Helps understand scope, iteration of ideas, etc.
@profvjreddi commented on GitHub (Apr 14, 2025):
Hi @huskydj1 — thank you so much for the candid feedback!
I really appreciate it when folks take the time to share thoughtful suggestions and ideas for improvement. The book is very much a work in progress, and I take all feedback seriously -- so it genuinely helps shape and refine things as I go.
Just a quick heads-up: please don’t read the Federated Learning chapter too closely right now. I know it’s in there, but it definitely needs a full rewrite. I’m already working on a major revision offline and plan to push an update soon — hopefully by the end of the month.
And please keep the candid feedback coming — I really value it! 🙏 My process is usually iterative: I write a first version, get feedback, then revisit sections in cycles of improvement. Messages like yours are exactly what help move things forward.
By the way, if you come across anything you’d like to submit a PR for, feel free as this is a community resource, and all contributors are publicly acknowledged here: contributors.
@profvjreddi commented on GitHub (Aug 23, 2025):
Resolved - Exercises added to chapters