Added TILs to the mix!

content/posts/when-easy-going-isnt-easy.md

@@ -1,10 +1,12 @@
 ---
 title: "When Easy Going Isnt Easy"
 date: 2023-09-08T10:02:55-06:00
-draft: false
+last-mod: 2023-09-08T10:02:55-06:00
+type: 'post'
 tags: ['personality', 'mental health', 'advice']
-summary: 'My people-pleasing brain demands smooth sailing waters, often at the cost of the emotionally sensitive.'
-tocOpen: true
+description: 'My people-pleasing brain demands smooth sailing waters, often at the cost of the emotionally sensitive.'
+showTableOfContents: true
+weight: 2
 ---
 
 # Easy Doesn't Equal Right

content/tils/_index.md

@@ -0,0 +1,10 @@
+---
+title: "Today I Learned"
+type: "til"
+---
+
+Anyday I learn something cool, I will write up a brief TIL (Today I Learned) post.
+
+If they help you, great! But I think having a collection of my learnings will be pretty neat just for myself!
+
+# My TILs

content/tils/hammock-driven-development.md

@@ -0,0 +1,29 @@
+---
+date: 2025-03-03T09:19:07-07:00
+description: "I learned the importance of taking time away from the computer in software development"
+lastmod: 2025-03-03T09:19:07-07:00
+showTableOfContents: true
+type: "tils"
+title: "TIL: Hammock Driven Development"
+image: "images/hammock.jpg"
+alt: "hammock with a cat"
+tags: ["clojure", "practices", "rich hickey"]
+---
+
+# Context
+
+I started learning Clojure recently with the [Clojure for the Brave](https://www.braveclojure.com/) book, and found online a mention of [Rich Hickey's Greatest Hits](https://changelog.com/posts/rich-hickeys-greatest-hits).
+Curious, I listened to his [Hammock Driven Development](https://www.youtube.com/watch?v=f84n5oFoZBc) talk and had my mind changed about planning in software.
+
+In essence, hammock driven development emphasizes thinking through the problem, uninterrupted and consistently, thus creating agenda notes for our background mind to mull over the problem.
+
+Done correctly, you experience what Rich Hickey describes as a "delicious cake"[^1] of a solution.
+
+[^1]: Quote from [his talk](https://www.youtube.com/watch?v=f84n5oFoZBc)
+
+# Reflection
+
+I think in the 90's / early 2000's the sun started to set on the big boom of software planning, epitomized in the [waterfall methodology](https://en.wikipedia.org/wiki/Waterfall_model).
+But in my opinion, we may have thrown the baby out with the bath water here. I may be too Primegen-pilled, but I've shared his opinion that the best way to learn is to charge forward, 
+spewing out code, breaking things, only dipping my toes into docs long enough to cobble together what I need. Then, once I understand the problem space, I can really start to design my
+software for the space.