Polish up the latest fishbowl
This commit is contained in:
parent
25e13df04d
commit
1806da0389
|
@ -476,7 +476,7 @@ You also refer to them as "leaf libraries", right?
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<div class="chatlog__content chatlog__markdown">
|
<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>
|
</div>
|
||||||
|
|
||||||
|
|
|
@ -106,9 +106,9 @@ var fishbowls = [...]fishbowlInfo{
|
||||||
ContentsPath: "oop/OOP.html",
|
ContentsPath: "oop/OOP.html",
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
Slug: "code-reuse",
|
Slug: "libraries",
|
||||||
Title: "Responsible code reuse",
|
Title: "When do libraries go sour?",
|
||||||
Description: "TODO (Ben)",
|
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,
|
Month: time.July, Year: 2022,
|
||||||
ContentsPath: "code-reuse/code-reuse.html",
|
ContentsPath: "code-reuse/code-reuse.html",
|
||||||
},
|
},
|
||||||
|
|
Reference in New Issue