From 1806da03899486f9790f2b1382f94e478a176456 Mon Sep 17 00:00:00 2001 From: Ben Visness Date: Mon, 1 Aug 2022 20:29:56 -0500 Subject: [PATCH] Polish up the latest fishbowl --- src/templates/src/fishbowls/code-reuse/code-reuse.html | 2 +- src/website/fishbowl.go | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/templates/src/fishbowls/code-reuse/code-reuse.html b/src/templates/src/fishbowls/code-reuse/code-reuse.html index 526d8656..6cc84407 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?
- is the leafs concept related to Casey's components? or how do they differ? + is the leafs concept related to Casey's components? or how do they differ?
diff --git a/src/website/fishbowl.go b/src/website/fishbowl.go index 98e40dbb..a3f9e393 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", },