Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 2c2fccaa19ccffee11ef0f45374ea5284944ddec
parent d1364eed8afb7625381735fbe91c008ec75ee350
Author: Jake Bauer <>
Date:   Fri, 24 Feb 2023 17:05:32 -0500


Mcontent/garden/arboretum/ | 4++--
Mcontent/garden/arboretum/ | 8+++++++-
2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/content/garden/arboretum/ b/content/garden/arboretum/ @@ -32,8 +32,8 @@ if you're being really minimal, but a set of two forks, knives, spoons, mugs, plates, and bowls per person is the most versatile. Some nice-to-haves include a blender/food processor, more baking sheets/cake -pans/pie pans/etc., a whisk, a handmixer, an immersion blender, a large stock -pot, and a pressure cooker. +pans/pie pans/etc., a whisk, a grater, a handmixer, an immersion blender, +a large stock pot, and a pressure cooker. ### Knife diff --git a/content/garden/arboretum/ b/content/garden/arboretum/ @@ -131,10 +131,13 @@ speed unless you are specifically targeting a performance metric. Names should be descriptive and clear in context, but not redundant or excessive. In general, procedures should be named based on what they do and -functions should be named based on what they return and variables and types +functions should be named based on what they return. Variables and types should be nouns (e.g. `num_cakes` or `Parser`). ``` +draw(); +compute(); + x = compute_length(x); if (valid_length(x)) ``` @@ -142,6 +145,9 @@ if (valid_length(x)) is better than: ``` +screen_changer(); +do_stuff(); + x = length_computer(x); if (check_length(x)) ```