Goldfish get a bad rap; they actually remember things for months, not seconds. Your agent forgets everything the second the context window fills up, making its memory worse than a goldfish. This series builds a context-aware app on Redis Iris in five 15-minute sessions. Session 1 covers Search (Sept. 16), Session 2 focuses on Agent memory (Sept. 23), Session 3 on Context retrieving (Sept. 30), Session 4 on Semantic caching (Oct. 7), and Session 5 on Fully built context-aware apps + use cases (Oct. 14). Save your spot.

This week's system design refresher explores why git revert causes conflicts. Unlike reset, git revert does not rewrite history; instead, it creates a new commit that undoes changes from an earlier one, keeping history clean and safe for shared branches. Conflicts appear when a later commit changed the same lines as the commit being undone. In a diagram example, Commit C2 added a feature, and Commit C3 changed those same lines. Reverting C2 now collides with changes from C3, triggering a conflict. Resolution involves running git revert C2, pausing at the conflict, manually fixing the file, staging it, and continuing the revert so Git creates a new commit that cleanly undoes C2 while keeping C3 intact.