Merge pull request #339 from lrug/july-2024-coverage-and-update

Add coverage for July 2024, and update talks list

data/coverage/2024.yml

@@ -72,3 +72,12 @@ june:
     - type: video
       title: "LRUG June 2024 - Yevhenii Kurtov - LiveView: Stateful, server-rendered HTML"
       url: https://assets.lrug.org/videos/2024/june/yevhenii-kurtov-liveview-stateful-server-rendered-html-lrug-jun-2024.mp4
+july:
+  that-smells-like-time:
+    - type: video
+      title: "LRUG July 2024 - fell sunderland - That smells like time"
+      url: https://assets.lrug.org/videos/2024/july/fell-sunderland-that-smells-like-time-lrug-jul-2024.mp4
+  finding-unused-ruby-methods:
+    - type: video
+      title: "LRUG July 2024 - Joel Biffin - Finding unused Ruby methods"
+      url: https://assets.lrug.org/videos/2024/july/joel-biffin-finding-unused-ruby-methods-lrug-jul-2024.mp4

source/meetings/2024/july/index.html.md

@@ -32,13 +32,20 @@ below](#july24registration).
 > How does an experienced programmer solve problems? It's simpler (and more
 > complicated) than you might think!
 
-## From Spaghetti to Lasagna: Layering your code with DDD
+{::coverage year="2024" month="july" talk="that-smells-like-time" /}
 
-[Lily Stoney](https://github.com/LilyStoney)
+## Finding unused Ruby methods
 
-> How to apply DDD to a monolithic codebase, the benefits and reasons why it can
-> be beneficial, and how the event storming process can make the process of
-> defining domain boundaries a simpler task!
+[Joel Biffin](https://github.com/joelbiffin) says:
+
+> Whether code is safe to delete or not is a bit of a murky question in
+> Ruby - especially in untyped Ruby. Fear not though, as dangling unused
+> methods are a pretty safe place to start deleting things. Let's start there
+> and see where we get to.  Introducing [the Thanatos
+> gem](https://github.com/joelbiffin/thanatos) to help you find those unused
+> methods lurking in your code.
+
+{::coverage year="2024" month="july" talk="finding-unused-ruby-methods" /}
 
 ## Afterwards