Cleanup

DandyLyons · DandyLyons · commit 3e589e8ca61e · 2025-02-17T18:42:30.000-07:00
diff --git a/content/en/posts/post-14/index.md b/content/en/posts/post-14/index.md
@@ -6,8 +6,6 @@ description:
 topics: ["Swift", "Benchmarking", "Data Structures and Algorithms"]
 ---
 
-# Benchmarking in Swift with `swift-collections-benchmark`
-
 There is an age-old adage of programming which states *"Make it work, then make it right, then make it fast."* Today we will be focusing on how to *make it fast*, with the help of a valuable technique called Benchmarking. 
 
 When developing software, especially when working with algorithms and data structures, performance is often a key concern. You may have experienced a piece of code that behaves well in your tests, but when it's exposed to real-world data, performance degrades. This is where **benchmarking** comes in. Benchmarking allows developers to measure how long a piece of code takes to run, helping to identify bottlenecks and areas for optimization.
diff --git a/content/en/posts/post-15/index.md b/content/en/posts/post-15/index.md
@@ -7,8 +7,6 @@ description: Learn the subtle differences between native Mac apps, Mac Catalyst
 topics: [macOS, SwiftUI, Catalyst, Swift]
 ---
 
-# Demystifying Modern macOS Development
-
 ## Introduction
 
 For many years Apple, arguably left the Mac to languish for years while it focused on iOS and the iPhone. The Mac repeatedly got features years later than its mobile cousins, and the hardware was often behind and underpowered. But now, Mac app development is currently in the best state that it has been in a very long time, thanks to three major developments: 
diff --git a/content/en/posts/post-16/index.md b/content/en/posts/post-16/index.md
@@ -7,8 +7,6 @@ description: Learn about retroactive protocol conformance, and why you probably
 topics: [Swift]
 ---
 
-# Swift 6's New `@retroactive` Attribute
-
 Swift 6.0 introduced the `@retroactive` attribute to address a specific issue with protocol conformances. Here's what you need to know:
 
 ## The Problem
diff --git a/content/en/posts/post-17/index.md b/content/en/posts/post-17/index.md
@@ -6,7 +6,6 @@ images: [""]
 description: Ranges in Swift exlained, plain and simple.
 topics: [Swift, Ranges, Cheatsheet]
 ---
-# Swift Ranges Cheatsheet
 Ranges are fantastic for when we want to work with a range of sorted values that contain no duplicates. 
 
 ## Core Concepts:
diff --git a/content/en/posts/post-18/index.md b/content/en/posts/post-18/index.md
@@ -6,7 +6,6 @@ images: ["pexels-googledeepmind-17484975.jpg"]
 description: Has another technology broken your heart when it promised to make things simpler? Abstractions don't reduce complexity, they delegate it. 
 topics: ["Software Development", "Abstractions"]
 ---
-# Abstractions Increase Complexity: Here's Why That's Not A Bad Thing
 I'm starting to see a pattern that seems to replay again and again. A shiny new technology comes out that solves a problem. A bunch of developers flock to it, evangelizing it to everyone else. Eventually the tech disappoints. The developers complain that the new solution is so complicated, and they long for the next shiny new thing. 
 
 Surely this pattern has existed for a long time, and will continue to repeat. But why does it happen? I think it's because we have fallen for a fallacy. The fallacy is this: 
diff --git a/content/en/posts/post-19/index.md b/content/en/posts/post-19/index.md
@@ -6,7 +6,6 @@ images: [""]
 description: 
 topics: ["Swift", "SPM"]
 ---
-# How to Visualize a Dependency Graph of Swift Dependencies
 As projects grow in complexity, it is common to use two techniques: 
 
 1. Depend on external libraries. 
diff --git a/content/en/posts/post-20/index.md b/content/en/posts/post-20/index.md
@@ -7,8 +7,6 @@ description: Learn how to get a compile-time guarantee that you have handled eve
 topics: ["Swift", "Swift 6", "Error Handling"]
 ---
 
-# Exhaustive, Flexible, Multi-Typed Error Handling in Swift
-
 Swift has long had fantastic error handling! Errors are simple value types that conform to the `Error` protocol. 
 
 ```swift
diff --git a/content/en/posts/post-21/index.md b/content/en/posts/post-21/index.md
@@ -6,8 +6,6 @@ images: ["https://i.imgflip.com/96ybn9.jpg"]
 description: Should you use assert(), precondition(), or maybe fatalError()? Let's learn how to decide. 
 topics: ["Swift", "Cheatsheet"]
 ---
-
-# Swift Assertions Cheatsheet: How, Why, and When to Crash
 <center>
 <img src="https://i.imgflip.com/96ybn9.jpg" alt="Chaos Girl Meme: Swift watches while a house labeled `fatalError()` burns.">
 </center>
diff --git a/content/en/posts/post-22/value and reference types.md b/content/en/posts/post-22/value and reference types.md
@@ -7,8 +7,6 @@ description:
 topics: ["Swift", "C", "Pointers"]
 ---
 
-# A Deep Dive into Value and Reference Types in Swift
-
 Understanding how Swift handles memory and data is key to writing efficient, bug-free code. In this post, we'll explore the differences between value and reference types, and more importantly, what value and reference **semantics** mean in Swift. By the end, you'll know how to think about these concepts when designing your own Swift code.
 
 ## Value vs. Reference Types
diff --git a/content/en/posts/post-23/Unordered Equality Checking in Swift.md b/content/en/posts/post-23/Unordered Equality Checking in Swift.md
@@ -7,7 +7,6 @@ topics: ["Swift", "Equatable Protocol"]
 images: 
 description: Learn how to ignore ordering when checking equality in Swift. 
 ---
-# Unordered Equality Checking in Swift
 
 Have you ever needed to compare two arrays in Swift, but the order of elements doesn't matter? I find this often happens to me when convert between an ordered type such as `Array` and an unordered type such as `Set` or `Dictionary`.  Today, we'll explore how to implement **unordered equality checking** in Swift, starting with the basics and working our way up to a flexible, protocol-based solution.
 
diff --git a/content/en/posts/post-27/Introducing SelectiveEquatable.md b/content/en/posts/post-27/Introducing SelectiveEquatable.md
@@ -8,8 +8,6 @@ images: ["SelectiveEquatable.png"]
 description: Quickly and easily check for equality on specific properties in Swift with the new SelectiveEquatable protocol.
 ---
 
-# Introducing SelectiveEquatable
-
 A few weeks ago, I released a blog post named ["Selective Equality Checking in Swift"](https://dandylyons.net/posts/post-24/selective-equality-checking-in-swift/). In that post, I designed and implemented an API to check for equality on specific properties of a type. Today, I am excited to announce a new Swift protocol named `SelectiveEquatable`, that makes all of this even easier. Let's see it in action.
 
 ## Using SelectiveEquatable
diff --git a/content/en/posts/post-28/Easy Deep Cloning in Swift.md b/content/en/posts/post-28/Easy Deep Cloning in Swift.md
@@ -6,8 +6,6 @@ tags: ["Swift", "Value Semantics", "Reference Types", "Cloning", "Codable", "Val
 slug: easy-deep-copy-cloning-in-swift
 ---
 
-# Easy Deep Copy Cloning in Swift
-
 In most programming languages, there is some concept of value and reference types. In Swift, we prefer to use value types and value semantics whenever possible. This is because value types are easier to reason about since they cannot be mutated by other parts of the code.[^1] However there are some times when we must use reference types. Is there a way to get our reference types to behave like value types? Yes, there is.
 
 [^1]: To be clear, value types are not better or worse than reference types. They both have very valid use cases.
diff --git a/content/en/posts/post-29/What's the difference between class and class_name in Godot?.md b/content/en/posts/post-29/What's the difference between class and class_name in Godot?.md
@@ -7,8 +7,6 @@ description: Discover how inner classes and class names work in Godot's GDScript
 series: ["GDScript Fundamentals"]
 ---
 
-# What's the difference between class and class_name in Godot?
-
 When you're writing scripts in Godot, you might have noticed that some scripts use `class` and others use `class_name`. What's the difference between these two keywords? Let's find out.
 
 ## `class_name` keyword
diff --git a/content/en/posts/post-30/index.md b/content/en/posts/post-30/index.md
@@ -8,8 +8,6 @@ series: ["Actually Useful Obsidian"]
 postNumber: 30
 ---
 
-# Actually Useful Obsidian: Formatting
-
 Today we start a new series on one of my favorite note-taking apps, [Obsidian](https://obsidian.md/). In this series, we'll cover the basics of Obsidian. Here we will intentionally NOT be doing anything particularly fancy. We won't be using strange plugins or custom CSS. Instead we'll be focusing on the most helpul, core features that I use every day. Beginners will be able to finally overcome the initial learning curve and start using Obsidian effectively. And experienced users will find helpful tools to simplify their setup! 
 
 ## What is Obsidian?
diff --git a/content/en/posts/post-31/Actually Useful Obsidian: Links.md b/content/en/posts/post-31/Actually Useful Obsidian: Links.md
@@ -1,11 +1,12 @@
 ---
-title: "Actually Useful Obsidian - Links"
+title: "Actually Useful Obsidian: Links"
 date: 2025-02-25
 tags: ["Obsidian"]
 series: ["Actually Useful Obsidian"]
 image: 
 description: 
 slug: actually-useful-obsidian-links
+draft: true
 ---
 The following is my very rough draft outline of the blog that I am writing below. 
 ### The Power of Links
