diff --git a/src/templates/src/fishbowls/code-reuse/code-reuse.html b/src/templates/src/fishbowls/code-reuse/code-reuse.html
index 526d865..6cc8440 100644
--- a/src/templates/src/fishbowls/code-reuse/code-reuse.html
+++ b/src/templates/src/fishbowls/code-reuse/code-reuse.html
@@ -476,7 +476,7 @@ You also refer to them as "leaf libraries", right?
                     </div>
 
                     <div class="chatlog__content chatlog__markdown">
-                        <span class="chatlog__markdown-preserve">is the leafs concept related to Casey's components? or how do they differ?</span>
+                        <span class="chatlog__markdown-preserve">is the leafs concept related to <a href="https://caseymuratori.com/blog_0024">Casey's components</a>? or how do they differ?</span>
 
                     </div>
 
diff --git a/src/website/fishbowl.go b/src/website/fishbowl.go
index 98e40db..a3f9e39 100644
--- a/src/website/fishbowl.go
+++ b/src/website/fishbowl.go
@@ -106,9 +106,9 @@ var fishbowls = [...]fishbowlInfo{
 		ContentsPath: "oop/OOP.html",
 	},
 	{
-		Slug:        "code-reuse",
-		Title:       "Responsible code reuse",
-		Description: "TODO (Ben)",
+		Slug:        "libraries",
+		Title:       "When do libraries go sour?",
+		Description: "The Handmade community is often opposed to using libraries. But let's get more specific about why that can be, and whether that's reasonable. What do we look for in a library? When do libraries go sour? How do we evaluate libraries before using them? How can the libraries we make avoid these problems?",
 		Month:       time.July, Year: 2022,
 		ContentsPath: "code-reuse/code-reuse.html",
 	},