diff --git a/site/link-log.yaml b/site/link-log.yaml
index cef49fa..94984b3 100644
--- a/site/link-log.yaml
+++ b/site/link-log.yaml
@@ -1,3 +1,27 @@
+- url: https://maggieappleton.com/home-cooked-software
+  name: "Maggie Appleton: Home-Cooked Software and Barefoot Developers"
+  summary: |
+    I love so much about this presentation. I believe in the power of writing simple, rough software
+    for small communities, or even for communities of one (e.g. yourself). I've done a lot of that.
+    I also have been feeling the pull of local-first software with really simple tech stacks. That
+    might be my disillusionment with the complexity of modern DevOps.
+
+    That said, I don't buy that LLMs are going to suddenly allow a lot of people who have never coded
+    before to start coding. Every LLM-based coding tool I've tried has been basically IntelliSense, but
+    with more variance (plus and minus). To say that people without any other assistance can use
+    IntelliSense to develop whole applications would be nonsense, and so far, I think it's the same
+    for LLMs. Now, does richer developer tooling lower the barrier to entry? Certainly.
+
+- url: https://jeffhuang.com/productivity_text_file/
+  name: "Jeff Huang: My productivity app is a never-ending .txt file"
+  summary: |
+    My system is pretty similar to this, though I'm still living the one-file-per-day life. I've tried
+    just about all the options out there, and for me, the one that has the lowest friction and highest
+    interoperability is text files.
+
+    It also reminds me of the adage I've heard repeated many times about David Allen's Getting Things Done system: "if you
+    can't do GTD with a pen and paper, you aren't really doing GTD."
+
 - url: https://pcalv.es/mosh-pit-rules-applied-to-social-media/
   name: "Mosh pit rules applied to social media"
   summary: |