diff --git a/src/content/posts/computational-thinking.md b/src/content/posts/computational-thinking.md
index 0d7a400..06b2a64 100644
--- a/src/content/posts/computational-thinking.md
+++ b/src/content/posts/computational-thinking.md
@@ -11,7 +11,7 @@ In a curriculum dedicated to the "Ways of Thinking in Informatics," the chapter
 
 Here is the reality check: That assumption is partially false.
 
-Computer Science is only conditionally about computers. The legendary computer scientist Edsger W. Dijkstra is famously attributed with the aphorism: "Computer science is no more about computers than astronomy is about telescopes." While the provenance of this quote is debated—Wikiquote marks it as disputed—the underlying sentiment remains structurally sound. Astronomy involves the development of high-performance instruments, yes, but the goal of the astronomer is not to build a telescope; it is to gain knowledge about the universe _using_ that telescope.
+Computer Science is only conditionally about computers. The legendary computer scientist Edsger W. Dijkstra is famously attributed with the aphorism: "Computer science is no more about computers than astronomy is about telescopes." While the provenance of this quote is debated — Wikiquote marks it as disputed — the underlying sentiment remains structurally sound. Astronomy involves the development of high-performance instruments, yes, but the goal of the astronomer is not to build a telescope; it is to gain knowledge about the universe _using_ that telescope.
 
 Similarly, Informatics does not have the sole objective of building powerful machines. We certainly have sub-disciplines dedicated to hardware and architecture, but the soul of the field lies elsewhere. Computational Thinking is indeed a core concern, but we must be careful not to elevate it to a mythical "silver bullet" status. It is essential, but it is nuanced. To understand it, we have to look at how we solve problems _with_ these machines, rather than just how the machines work. As Stephen Wolfram (the physicist behind WolframAlpha) once noted, the act of actually programming something inevitably allows one to do more exploration of the concept itself. It is a tool for thought, not just calculation.
 
@@ -23,7 +23,7 @@ Wing’s definition is precise: It involves the thought processes required to fo
 
 ### The True Origin: Ada Lovelace’s Vision
 
-To truly understand the depth of this concept, we have to look much further back than 2006—all the way to the 19th century. Augusta Ada King, Countess of Lovelace (born 1815), provides the first historical evidence of Computational Thinking. At the age of 17, she witnessed a demonstration of a partially finished automatic calculating machine and was immediately captivated. She met its creator, Charles Babbage, and wrote about seeing the "thinking machine" (or so it seemed) raising numbers to the 2nd and 3rd powers and extracting roots of quadratic equations.
+To truly understand the depth of this concept, we have to look much further back than 2006 — all the way to the 19th century. Augusta Ada King, Countess of Lovelace (born 1815), provides the first historical evidence of Computational Thinking. At the age of 17, she witnessed a demonstration of a partially finished automatic calculating machine and was immediately captivated. She met its creator, Charles Babbage, and wrote about seeing the "thinking machine" (or so it seemed) raising numbers to the 2nd and 3rd powers and extracting roots of quadratic equations.
 
 Babbage and Lovelace began a collaboration that would define the pre-history of computing. Babbage focused on a machine far more complex than his previous "Difference Engine." He called it the **Analytical Engine**. Today, we can legitimately call this device the first concept of a "general-purpose computer." However, there was a massive gap in understanding between the inventor and the collaborator. Babbage viewed his projects essentially as increasingly complex calculators; his primary goal was to print mathematical tables quickly and precisely to avoid human error.
 
@@ -39,7 +39,7 @@ Lovelace predicted that the mere act of automating mathematical processes would
 
 ### The 20th Century Pillars: Papert and Wilson
 
-Fast forward to 1980, and we meet Seymour Papert, a pioneer who linked this thinking to education. Papert argued that everyone uses procedures in everyday life—like giving directions to a lost motorist—but these are rarely reflected upon. In a computational environment (like his LOGO programming language), a procedure becomes a distinct "thing" that is named, manipulated, and recognized. Papert famously called **debugging** "the essence of intellectual activity," a perspective that reframes failure not as an error, but as the primary mechanism of learning.
+Fast forward to 1980, and we meet Seymour Papert, a pioneer who linked this thinking to education. Papert argued that everyone uses procedures in everyday life — like giving directions to a lost motorist — but these are rarely reflected upon. In a computational environment (like his LOGO programming language), a procedure becomes a distinct "thing" that is named, manipulated, and recognized. Papert famously called **debugging** "the essence of intellectual activity," a perspective that reframes failure not as an error, but as the primary mechanism of learning.
 
 Shortly after, in 1982, physicist Ken Wilson won the Nobel Prize. His contribution was the computational modeling of phase transitions in matter. Wikipedia’s entry on Wilson is telling; it lists his status as a "pioneer in using computers" _before_ his physical discoveries. Peter Denning, writing in 2017, noted that Wilson and his contemporaries used the term "Computational Science" to describe a new paradigm of science. They viewed computation not just as a tool, but as a third pillar of scientific inquiry, standing equal alongside Theory and Experiment.
 
@@ -67,7 +67,7 @@ Crucially, she placed these three elements into a cycle.
 2.  **Automation:** We let the "information processing agent" execute the solution.
 3.  **Analysis:** We examine the results of that execution.
 
-This analysis then feeds back into the Abstraction phase. The insights gained from the automation allow us to refine the model, fix the bugs, and improve the logic. We iterate. This cyclic view acknowledges that we often don't truly understand a problem until we have tried (and perhaps failed) to simulate or solve it computationally. This loop—Abstraction, Automation, Analysis—is the modern, robust definition of Computational Thinking.
+This analysis then feeds back into the Abstraction phase. The insights gained from the automation allow us to refine the model, fix the bugs, and improve the logic. We iterate. This cyclic view acknowledges that we often don't truly understand a problem until we have tried (and perhaps failed) to simulate or solve it computationally. This loop — Abstraction, Automation, Analysis — is the modern, robust definition of Computational Thinking.
 
 ---
 
@@ -91,7 +91,7 @@ Here, we start doing things that were previously impossible, not just slow. The
 
 #### 3. The Epistemological Revolution
 
-This is where it gets heavy. **Epistemology** is the branch of philosophy concerned with knowledge—"What can we know?"
+This is where it gets heavy. **Epistemology** is the branch of philosophy concerned with knowledge — "What can we know?"
 Tedre argues that computation gives us a new way to interpret the world. Simulation becomes a valid path to knowledge. Previously, we observed the world or theorized about it. Now, we simulate it. If a simulation accurately predicts a phenomenon, we accept the simulation's rules as a form of truth. This is a **Representational Shift**, equivalent in human history to the invention of writing, the printing press, or the moving image. Code is now a valid way to represent knowledge.
 
 #### 4. The Ontological Revolution
@@ -136,7 +136,7 @@ A 500kg crate of hard drives moving via airplane represents a data transfer rate
 Finally, we have the Monty Hall problem. You have three boxes (or doors). One has a prize (a pearl), two have nothing (peas). You pick a box. The host opens one of the _other_ boxes to reveal a pea. He asks: "Do you want to switch your guess to the remaining closed box?"
 
 Intuitively, most people say it doesn't matter. It feels like a 50/50 split.
-But if you write a simple simulation—a script that runs this scenario 10,000 times—you see the truth immediately. Switching wins 2/3 of the time. The simulation forces you to accept a mathematical reality that your intuition rejects.
+But if you write a simple simulation — a script that runs this scenario 10,000 times — you see the truth immediately. Switching wins 2/3 of the time. The simulation forces you to accept a mathematical reality that your intuition rejects.
 However, as we will discuss later, the goal isn't just to trust the simulation. The ultimate goal is "Code as a way of understanding." By writing the code, you can actually see the logic: The variable determining which box the host opens becomes irrelevant to your winning chances if you stay, but crucial if you switch. The code reveals the structure of the logic itself.
 
 ### The New Scientist: The Research Software Engineer
@@ -148,23 +148,23 @@ Jeannette Wing noted that this transformation is happening everywhere. Computati
 
 ---
 
-_Next, we dive into the history of the "Act" of programming itself—how we went from "Writing" poetry for machines to the industrial "Engineering" of the NATO conference, and why the Waterfall model was doomed from the start._
+_Next, we dive into the history of the "Act" of programming itself — how we went from "Writing" poetry for machines to the industrial "Engineering" of the NATO conference, and why the Waterfall model was doomed from the start._
 
 ## Part 3: A History of "The Act": From Writing to Engineering
 
 ### The Great Gap & The War Machines
 
-After the visionary work of Charles Babbage and Ada Lovelace, the history of computing hit a pause button. Babbage was a brilliant inventor but a terrible communicator, and Lovelace died tragically young at 34, likely from cancer. Their ideas—the "Analytical Engine" and the first "program"—were largely lost to time, misunderstood by their Victorian contemporaries who only saw fancy calculators. It took nearly a century for the train to leave the station again, and unfortunately, it was war that fueled the engine.
+After the visionary work of Charles Babbage and Ada Lovelace, the history of computing hit a pause button. Babbage was a brilliant inventor but a terrible communicator, and Lovelace died tragically young at 34, likely from cancer. Their ideas — the "Analytical Engine" and the first "program" — were largely lost to time, misunderstood by their Victorian contemporaries who only saw fancy calculators. It took nearly a century for the train to leave the station again, and unfortunately, it was war that fueled the engine.
 
 The catalyst was the **Enigma**, a German machine used during World War II to encrypt communications. While not a computer in the modern sense (it was a highly specialized electromechanical cipher device), the Allied effort to break it birthed the modern computing era. This happened at **Bletchley Park**, where a team of British mathematicians and "computers" (the job title for humans who did calculations) worked to decrypt messages.
 
-The "Bomb" (or Bombe) was the machine designed to crack Enigma. It wasn't a general-purpose computer; it was a beast built for one specific task: finding the daily settings of the Enigma machines. This project was critical—it is estimated that the work at Bletchley Park shortened the war by two to four years.
+The "Bomb" (or Bombe) was the machine designed to crack Enigma. It wasn't a general-purpose computer; it was a beast built for one specific task: finding the daily settings of the Enigma machines. This project was critical — it is estimated that the work at Bletchley Park shortened the war by two to four years.
 
 #### The Hidden Figures of Bletchley
 
 The most famous figure here is **Alan Turing**, the father of theoretical computer science. He formalized the concept of the "General Purpose Computer" (the Turing Machine) and later laid the groundwork for AI with the Turing Test. But the history books often gloss over his team. **Joan Clarke** was a pivotal figure who worked alongside Turing on the Bomb. Because the job of "crypto-analyst" wasn't technically open to women, she was hired as a "Linguist," despite speaking no foreign languages. Her pay and rank reflected this bureaucratic fiction, not her actual contributions.
 
-This is a recurring theme we need to address: The history of informatics is often told through a male lens, erasing the women who were foundational to the field. Just as we saw in _Scientific Thinking_ with the Viking warrior leader (who turned out to be a woman upon modern DNA analysis), computing history is full of "forgotten" women. Turing himself was later persecuted for his homosexuality, driven to suicide by state-mandated hormone "therapy"—a tragedy that highlights how society treated the architects of its own salvation.
+This is a recurring theme we need to address: The history of informatics is often told through a male lens, erasing the women who were foundational to the field. Just as we saw in _Scientific Thinking_ with the Viking warrior leader (who turned out to be a woman upon modern DNA analysis), computing history is full of "forgotten" women. Turing himself was later persecuted for his homosexuality, driven to suicide by state-mandated hormone "therapy" — a tragedy that highlights how society treated the architects of its own salvation.
 
 ### ENIAC: The First "Real" Computer
 
@@ -172,13 +172,13 @@ The shift from specialized machines like the Bomb to true "General Purpose Compu
 
 But who programmed it?
 
-The hardware was built by men, but the **ENIAC Six**—the first professional programming team in history—were women. In 1944, there were nearly 50 women working on the project, but six of them became the core operators. At the time, they were often dismissed as "refrigerator ladies" (models posing with appliances), but in reality, they were inventing the discipline of software engineering from scratch. They didn't have a manual. They had wiring diagrams.
+The hardware was built by men, but the **ENIAC Six** — the first professional programming team in history — were women. In 1944, there were nearly 50 women working on the project, but six of them became the core operators. At the time, they were often dismissed as "refrigerator ladies" (models posing with appliances), but in reality, they were inventing the discipline of software engineering from scratch. They didn't have a manual. They had wiring diagrams.
 
 ### Phase 1: Programming as "Writing"
 
 To understand the mindset of this era (1940s-1950s), you have to realize that **programming languages didn't exist**. There was no Python, no C, not even Assembly.
 
-Programming the ENIAC meant physically connecting cables and setting switches. It was "operating at the open heart of the patient." The machine was completely exposed. To "program," you had to describe a narrative of what the electricity should do. The programmers wrote this narrative down as text—prose descriptions of the logic—and then translated that text into physical connections.
+Programming the ENIAC meant physically connecting cables and setting switches. It was "operating at the open heart of the patient." The machine was completely exposed. To "program," you had to describe a narrative of what the electricity should do. The programmers wrote this narrative down as text — prose descriptions of the logic — and then translated that text into physical connections.
 
 This era defined programming as **"Writing."**
 Code was seen as a literary form, a story told to the machine. This philosophy persisted even as early languages emerged. Donald Knuth’s magnum opus, _The Art of Computer Programming_, enshrines this view: Code is a form of art, meant to be beautiful and elegant.
@@ -187,7 +187,7 @@ However, this "artistic" approach has a fatal flaw. It works great for calculati
 
 ### Phase 2: The Software Crisis
 
-By the 1960s, computers had evolved from room-sized calculators to mainframes like the **IBM 360**. These machines were powerful, and they were everywhere—banks, airlines, governments.
+By the 1960s, computers had evolved from room-sized calculators to mainframes like the **IBM 360**. These machines were powerful, and they were everywhere — banks, airlines, governments.
 
 Suddenly, the industry faced a terrifying reality: **Software was becoming more expensive than hardware.**
 The programs required to run these mainframes were so complex that a single "artist" couldn't write them. They couldn't even be fully mathematically described or tested. Projects ran over budget, missed deadlines, and were full of bugs.
@@ -221,7 +221,7 @@ There was just one problem: **It doesn't work.**
 
 Winston Royce, the man often credited with inventing the Waterfall model in his 1970 paper, actually wrote the paper to say it was a bad idea! He included a diagram of the linear process and explicitly stated: "I believe in this concept, but the implementation described above is risky and invites failure."
 
-He argued that software is inherently iterative. You discover new things about the problem _while_ you are coding the solution. A strict linear process forbids this learning. If you find a design flaw during implementation in a Waterfall model, it’s too late—you’ve already signed off on the Design phase.
+He argued that software is inherently iterative. You discover new things about the problem _while_ you are coding the solution. A strict linear process forbids this learning. If you find a design flaw during implementation in a Waterfall model, it’s too late — you’ve already signed off on the Design phase.
 
 ### The Mythical Man-Month
 
@@ -233,7 +233,7 @@ Brooks wrote _The Mythical Man-Month_, a book that remains the bible of software
 Why? Because software isn't digging a ditch. If you have a ditch to dig, adding more people helps. In software, adding people increases the **communication overhead** quadratically. New people need to be trained, and they interrupt the work of the experienced people.
 Brooks also described "Software Entropy": As time passes, a system becomes less and less well-ordered. Eventually, fixing bugs creates more bugs. The system wears out, not physically, but logically.
 
-This realization—that you cannot "construct" software like a building—led us to the modern era. We had to abandon the idea of "Building" and embrace a new metaphor: "Growing."
+This realization — that you cannot "construct" software like a building — led us to the modern era. We had to abandon the idea of "Building" and embrace a new metaphor: "Growing."
 
 ---
 
@@ -243,11 +243,11 @@ _Next, we explore "Code as a Garden," why your codebase is likely a sick patient
 
 ### From Construction to Cultivation
 
-If the "Waterfall" model was an attempt to treat software like a construction site—rigid, planned, and architectural—the modern era is defined by a realization that this model is fundamentally broken. We have moved from the metaphor of **Building** to the metaphor of **Growing**.
+If the "Waterfall" model was an attempt to treat software like a construction site — rigid, planned, and architectural — the modern era is defined by a realization that this model is fundamentally broken. We have moved from the metaphor of **Building** to the metaphor of **Growing**.
 
 Software development is not about stacking bricks according to a blueprint that was finalized months ago. It is an organic process. The "Standish Group Chaos Report" (2015), which analyzed 50,000 projects, made this brutally clear: Linear processes fail. Iterative processes succeed.
 
-This shift changes the definition of "Programming" again. It is no longer about "Writing" a story or "Constructing" a bridge. It is about **Gardening**. You plant a seed (a prototype), you water it (add features), you prune it (refactor), and sometimes you have to rip out weeds (debugging). As you move pieces on the board—Concept, Design, Model, Code—everything evolves simultaneously. You don't know exactly what the final tree looks like until it has grown.
+This shift changes the definition of "Programming" again. It is no longer about "Writing" a story or "Constructing" a bridge. It is about **Gardening**. You plant a seed (a prototype), you water it (add features), you prune it (refactor), and sometimes you have to rip out weeds (debugging). As you move pieces on the board — Concept, Design, Model, Code — everything evolves simultaneously. You don't know exactly what the final tree looks like until it has grown.
 
 ### The Codebase as an Organism
 
@@ -325,7 +325,7 @@ Code is our new way of talking.
 
 ---
 
-_Next, in the final part, we will demystify the "Algorithm"—separating the media's "Dark Side" fear-mongering from the mathematical "Light Side"—and break down the 5 Principles of Algorithmic Thinking._
+_Next, in the final part, we will demystify the "Algorithm" — separating the media's "Dark Side" fear-mongering from the mathematical "Light Side" — and break down the 5 Principles of Algorithmic Thinking._
 
 ## Part 5: Algorithmic Thinking: The Light, The Dark, and The Logic
 
@@ -367,7 +367,7 @@ Because algorithms must be "unambiguous" and handle all edge cases, humans are t
 
 In 1983, researcher R. Lesuisse conducted a study on Binary Search. He examined 20 implementations of the algorithm found in published educational articles.
 **The result:** Only 5 out of 20 were correct.
-15 of them contained subtle bugs—usually "off-by-one" errors (e.g., excluding the middle item incorrectly) or failing to handle empty lists. This proves that high-level conceptual understanding (Abstraction) is not enough; you need rigorous precision (Specification) to make it work.
+15 of them contained subtle bugs — usually "off-by-one" errors (e.g., excluding the middle item incorrectly) or failing to handle empty lists. This proves that high-level conceptual understanding (Abstraction) is not enough; you need rigorous precision (Specification) to make it work.
 
 ### The PR Problem: The "Dark Side" of Algorithms
 
diff --git a/src/content/posts/creative-thinking.md b/src/content/posts/creative-thinking.md
index 1a1a7fb..d1c400d 100644
--- a/src/content/posts/creative-thinking.md
+++ b/src/content/posts/creative-thinking.md
@@ -11,7 +11,7 @@ In fact, when we look at the monumental leaps in Computer Science, they weren’
 
 The list goes on. Linus Torvalds didn’t just write a better version of SVN; he invented **Git**, a distributed version control system that fundamentally changed how humans collaborate on code. Alan Kay gave us **Object-Oriented Programming**, changing the paradigm of how we model software. Douglas Engelbart gave us the **computer mouse** and the concept of direct manipulation. These weren't inevitable logical conclusions; they were creative sparks that became foundational technologies.
 
-A massive aspect of creative problem-solving in our field is **Computational Thinking**. This mindset allows us to forge completely new paths to solutions that were previously invisible. Consequently, your role—whether you are a developer, a Research Software Engineer, or an architect—is not just to write syntax. Your job is to utilize Computational Thinking to discover creative new solutions.
+A massive aspect of creative problem-solving in our field is **Computational Thinking**. This mindset allows us to forge completely new paths to solutions that were previously invisible. Consequently, your role — whether you are a developer, a Research Software Engineer, or an architect — is not just to write syntax. Your job is to utilize Computational Thinking to discover creative new solutions.
 
 ### Defining the Undefinable (and the AI Problem)
 
@@ -19,7 +19,7 @@ However, pinning down exactly what "creativity" means is notoriously difficult.
 
 The standard definitions we often cite, like those found on Wikipedia, don't really answer the hard questions posed by Generative AI. We know for a fact that AI systems can generate ideas that are convincing, original, surprising, and even useful. However, we usually view the _selection_ of those generated ideas by humans as the actual contribution. This is where the distinction gets blurry.
 
-To solve this, Mark Runco proposes a critical update to our definition. He suggests we need to add two specific criteria: **Authenticity** and **Intentionality**. These are two aspects of creativity that we cannot—at least at this moment—truly ascribe to Artificial Intelligence. An AI might generate a beautiful image or a working code snippet, but it lacks the internal _intent_ to solve a problem or express a state, and it lacks the _authenticity_ of lived experience behind the creation.
+To solve this, Mark Runco proposes a critical update to our definition. He suggests we need to add two specific criteria: **Authenticity** and **Intentionality**. These are two aspects of creativity that we cannot — at least at this moment — truly ascribe to Artificial Intelligence. An AI might generate a beautiful image or a working code snippet, but it lacks the internal _intent_ to solve a problem or express a state, and it lacks the _authenticity_ of lived experience behind the creation.
 
 This leads us to a cascade of complex questions. Is creativity a purely individual quality, or does it emerge from groups? Does it require an entire society, backed by history, art, and culture, to manifest? Is it a genetic lottery ticket, or is it a muscle that can be trained? Finally, should we judge creativity by the **product** (the thing created) or the **process** (how it was made)?
 
@@ -27,9 +27,9 @@ This leads us to a cascade of complex questions. Is creativity a purely individu
 
 Despite the evidence that engineering is inherently creative, many people in technical disciplines genuinely believe they possess zero creativity. This belief system can be traced back to a romanticized tradition of how we view "creatives," which manifests in two specific phenomena that damage our self-image as engineers.
 
-The first phenomenon is the distortion of creativity by popular media. In movies, TV series, books, and graphic novels, "creative people" are depicted as fundamentally different from the rest of the species. To make them easily identifiable to audiences, they are forced into rigid stereotypes. They work in "creative professions"—usually creating cultural artifacts like paintings or fashion—and are portrayed as eccentric, unusual characters. They have exaggerated traits: they are inattentive, easily distracted, messy, perhaps introverted and brooding, or wildly extroverted and manic.
+The first phenomenon is the distortion of creativity by popular media. In movies, TV series, books, and graphic novels, "creative people" are depicted as fundamentally different from the rest of the species. To make them easily identifiable to audiences, they are forced into rigid stereotypes. They work in "creative professions" — usually creating cultural artifacts like paintings or fashion — and are portrayed as eccentric, unusual characters. They have exaggerated traits: they are inattentive, easily distracted, messy, perhaps introverted and brooding, or wildly extroverted and manic.
 
-This creates a role model for creativity that most engineers cannot—and do not want to—identify with. This idea that creativity is the exclusive domain of art and design is called the **Art Bias**. It is a cognitive distortion. Unlike some biases that have evolutionary biological roots, the Art Bias is socially constructed. It is essentially a societal misunderstanding, but one with damaging consequences.
+This creates a role model for creativity that most engineers cannot — and do not want to — identify with. This idea that creativity is the exclusive domain of art and design is called the **Art Bias**. It is a cognitive distortion. Unlike some biases that have evolutionary biological roots, the Art Bias is socially constructed. It is essentially a societal misunderstanding, but one with damaging consequences.
 
 There are even studies showing that we subconsciously rate the work of creative people as "better" or "more valuable" if the artist acts eccentrically. This is a direct result of this misrepresentation. We have turned a stereotype into a prejudice. If you are a tidy, logical, punctual engineer, society tells you that you don't fit the "creative" costume.
 
@@ -55,7 +55,7 @@ But if we look behind the curtain, the truth is undeniable: **Analytics and Logi
 
 ---
 
-_Now that we’ve established that you are, in fact, creative, we need to look at how your brain actually handles—and blocks—new ideas. In the next part, we’ll deconstruct the "Thinking Canyon," destroy the myth of the "Right Brain," and solve a puzzle that proves how your own implicit assumptions are holding you back._
+_Now that we’ve established that you are, in fact, creative, we need to look at how your brain actually handles — and blocks — new ideas. In the next part, we’ll deconstruct the "Thinking Canyon," destroy the myth of the "Right Brain," and solve a puzzle that proves how your own implicit assumptions are holding you back._
 
 ## Part 2: Breaking the Box: Implicit Constraints, Neuro-Myths, and the Reality of Insight
 
@@ -67,7 +67,7 @@ We’ve established that you are creative, whether you like it or not. But if th
 
 Picture a grid of dots arranged in three rows of three (a 3x3 matrix). The challenge is simple: Connect all nine dots using a single continuous path of four straight lines, without lifting your pen from the paper.
 
-If you’ve never seen this before, it is surprisingly difficult. Most people fail because they instinctively try to draw lines that stay within the square perimeter formed by the outer dots. But here is the catch: it is geometrically impossible to solve this puzzle if you stay strictly inside that square. To solve it, at least one of the "vertices"—the point where your line changes direction—must fall in the empty white space _outside_ the grid of dots.
+If you’ve never seen this before, it is surprisingly difficult. Most people fail because they instinctively try to draw lines that stay within the square perimeter formed by the outer dots. But here is the catch: it is geometrically impossible to solve this puzzle if you stay strictly inside that square. To solve it, at least one of the "vertices" — the point where your line changes direction — must fall in the empty white space _outside_ the grid of dots.
 
 This reveals a fascinating glitch in human cognition. The puzzle instructions never said, "Stay inside the square." They never said, "Turn only on the dots." Yet, almost everyone creates these rules in their head. This is the concept of **Affordance**: the dots _suggest_ themselves as turning points. We see a grid, so our brain constructs an implicit "box" and locks us inside it. We are seduced by the narrative implied by the visual data.
 
@@ -77,9 +77,9 @@ Researchers Kershaw and Ohlsson explore this in their paper "The Fallacy of Sing
 
 But we can go deeper. The standard solution (extending the line past the grid) is just the first layer of "outside the box" thinking. If we truly scrutinize our implicit assumptions, we can break the puzzle wide open.
 
-Consider the physical nature of the dots. In a math textbook, a point has no dimension. But on paper, the dots are actually small ink circles—they have width. If we reject the implicit assumption that "these are mathematical points," we can realize that a line can pass through the _top edge_ of one dot and the _bottom edge_ of another. With sufficient precision, you can solve the puzzle with just **three lines** by zigzagging through the dots at extremely shallow angles.
+Consider the physical nature of the dots. In a math textbook, a point has no dimension. But on paper, the dots are actually small ink circles — they have width. If we reject the implicit assumption that "these are mathematical points," we can realize that a line can pass through the _top edge_ of one dot and the _bottom edge_ of another. With sufficient precision, you can solve the puzzle with just **three lines** by zigzagging through the dots at extremely shallow angles.
 
-Let's go further. Who said the dots are on a flat 2D plane? That is another implicit assumption. If you imagine the dots on a sphere (or realize the paper itself rests on the curvature of the Earth), you could theoretically connect them with a single line that circumnavigates the globe. Or, even simpler: who said you cannot manipulate the medium? If you fold the paper effectively—aligning the dots into a single row—you can stab a pencil through all nine dots at once. **One line.**
+Let's go further. Who said the dots are on a flat 2D plane? That is another implicit assumption. If you imagine the dots on a sphere (or realize the paper itself rests on the curvature of the Earth), you could theoretically connect them with a single line that circumnavigates the globe. Or, even simpler: who said you cannot manipulate the medium? If you fold the paper effectively — aligning the dots into a single row — you can stab a pencil through all nine dots at once. **One line.**
 
 This is the superpower of creative thinking: identifying **Implicit Assumptions**. These are the rules you are following that nobody actually gave you.
 
@@ -99,11 +99,11 @@ Neuroscience actually highlights the **plasticity** of the brain. Functions are
 
 ### Myth 2: The "Flash of Genius"
 
-Another destructive myth is the idea of the "Flash of Genius"—the lightning bolt of inspiration that strikes out of nowhere. We love this story. We picture Newton and the apple, or Archimedes in the bathtub. It suggests that creativity is magic, reserved for the chosen few.
+Another destructive myth is the idea of the "Flash of Genius" — the lightning bolt of inspiration that strikes out of nowhere. We love this story. We picture Newton and the apple, or Archimedes in the bathtub. It suggests that creativity is magic, reserved for the chosen few.
 
 Here is the reality: The "Flash" is real, but it does **not** come from nowhere.
 
-The "Flash" is actually the final step of a long, invisible labor. It happens only after a period of intense **Preparation**. You have to load your brain with data, struggle with the problem, and hit wall after wall. Then, you need **Incubation**—a period where your conscious mind steps away (the "idle time" we mentioned). During this downtime, the subconscious (or rather, non-conscious processing networks) continues to churn through the data, making connections that your focused, stressed-out conscious mind blocked.
+The "Flash" is actually the final step of a long, invisible labor. It happens only after a period of intense **Preparation**. You have to load your brain with data, struggle with the problem, and hit wall after wall. Then, you need **Incubation** — a period where your conscious mind steps away (the "idle time" we mentioned). During this downtime, the subconscious (or rather, non-conscious processing networks) continues to churn through the data, making connections that your focused, stressed-out conscious mind blocked.
 
 Bill Buxton, a computer scientist and designer, wrote about this regarding Wolfgang Amadeus Mozart. We see Mozart as a vessel of divine talent who just "heard" the music. We ignore the fact that he was drilled in music theory and performance from the time he was a toddler. His "genius" was the result of massive, sustained cognitive loading.
 
@@ -120,11 +120,11 @@ _We’ve debunked the biology and the magic. Now we need to look at the environm
 
 ## Part 3: The Social & Emotional Code: Teams, Stress, and the Psychology of Safety
 
-We have talked about the individual brain—the "software" and the "hardware." But unless you are coding in a cave on Mars, you do not work in a vacuum. You work in a team. And this brings us to the most critical environment for creativity: the social dynamic.
+We have talked about the individual brain — the "software" and the "hardware." But unless you are coding in a cave on Mars, you do not work in a vacuum. You work in a team. And this brings us to the most critical environment for creativity: the social dynamic.
 
 ### Myth 3: The Lonely Genius
 
-There is a persistent romantic image of the "Lonely Genius"—the brilliant recluse who locks themselves in a tower and emerges with a finished masterpiece. In reality, innovation is statistically a **team sport**.
+There is a persistent romantic image of the "Lonely Genius" — the brilliant recluse who locks themselves in a tower and emerges with a finished masterpiece. In reality, innovation is statistically a **team sport**.
 
 Research on "Distributed Intelligence" provides overwhelming evidence that the power of the unaided individual mind is highly overrated. Most of our intelligence and creativity results from interaction: collaborating with other individuals, using shared tools, and building upon existing artifacts. Cities with higher densities of "creative industries" produce significantly more patents, suggesting that proximity and collision of ideas drive innovation.
 
@@ -132,17 +132,17 @@ However, there is a fascinating contradiction in the expert opinions here. Steph
 
 How can both be true? The answer lies in the **atmosphere**.
 
-Creativity is a team sport **only if the team is safe**. If the atmosphere is open to "outside the box" thinking, the team amplifies intelligence. But if every new idea is met with the "social guillotine"—comments like _"Don't be stupid"_ or _"Let's be realistic"_—then the team becomes a creativity graveyard. Under those conditions, the individual is better off working alone.
+Creativity is a team sport **only if the team is safe**. If the atmosphere is open to "outside the box" thinking, the team amplifies intelligence. But if every new idea is met with the "social guillotine" — comments like _"Don't be stupid"_ or _"Let's be realistic"_ — then the team becomes a creativity graveyard. Under those conditions, the individual is better off working alone.
 
 Furthermore, group creativity techniques like **Brainstorming** only work if the individuals have done the work beforehand. A group of unprepared people shouting at a whiteboard is just noise. The most effective workflow is individual preparation (loading the brain) followed by group collision (sparking connections).
 
 ### The "First Validator" and the Onion of Context
 
-Imagine your working life as a series of concentric circles—like an onion.
+Imagine your working life as a series of concentric circles — like an onion.
 
 - The outer layer is Society.
 - The middle layer is your Company/Institution.
-- The innermost layer—the one touching you—is your **Immediate Team**.
+- The innermost layer — the one touching you — is your **Immediate Team**.
 
 This inner layer acts as the **First Validator**. When you have a fragile, new idea, you are vulnerable. You expose yourself to judgment. If this First Validator layer is toxic or dismissive, your brain learns a very fast lesson: _Do not share ideas here._ You shut down.
 
@@ -152,9 +152,9 @@ Therefore, the primary job of a team lead (or a senior engineer) is to protect t
 
 We often hear managers say, "I need to put some pressure on the team to get the creative juices flowing." This is scientifically backward. **Stress and Creativity are biologically incompatible.**
 
-When you are under stress (duress, fear of deadlines, angry bosses), your brain shifts gears. It shuts down higher-order functions and hands the reins to the **Limbic System**—the primal, emotional center focused on survival.
+When you are under stress (duress, fear of deadlines, angry bosses), your brain shifts gears. It shuts down higher-order functions and hands the reins to the **Limbic System** — the primal, emotional center focused on survival.
 
-This creates a **Cognitive Tunnel Vision**. Your brain’s only goal is to escape the stress. To do that, it craves certainty. It reaches for what it _knows_ works: established patterns, safe code, standard procedures. It blocks out anything risky, new, or unproven—i.e., it blocks out Creativity. You literally cannot "think outside the box" when your brain is screaming that the box is on fire.
+This creates a **Cognitive Tunnel Vision**. Your brain’s only goal is to escape the stress. To do that, it craves certainty. It reaches for what it _knows_ works: established patterns, safe code, standard procedures. It blocks out anything risky, new, or unproven — i.e., it blocks out Creativity. You literally cannot "think outside the box" when your brain is screaming that the box is on fire.
 
 ### The Four Fears
 
@@ -196,7 +196,7 @@ This is the "loading" phase. You cannot have an idea about nothing. In this phas
 
 **2. Incubation**
 This is the phase most managers hate because it looks like you aren't working. In medical terms, "incubation" is the time between infection and symptoms. In creativity, it is the time where you consciously put the problem aside. You stop staring at the IDE. You go for a walk, sleep, or work on something trivial.
-Crucially, this is not "doing nothing." It is a hand-off. You are passing the data from your limited, linear conscious mind to your massive, parallel-processing non-conscious mind. This is similar to the "Inner Game of Tennis": you have to get your ego out of the way to let the specialized parts of your brain do the heavy lifting. But for this to happen, you need **idle time**—a rare commodity in the age of the smartphone.
+Crucially, this is not "doing nothing." It is a hand-off. You are passing the data from your limited, linear conscious mind to your massive, parallel-processing non-conscious mind. This is similar to the "Inner Game of Tennis": you have to get your ego out of the way to let the specialized parts of your brain do the heavy lifting. But for this to happen, you need **idle time** — a rare commodity in the age of the smartphone.
 
 **3. Illumination (The Flash)**
 This is the "Eureka" moment. It defines the Illumination phase. Wallas observed that this moment almost always happens when you are _not_ thinking about the problem. It happens when you are in the shower, driving, or waking up. Why? Because you created the necessary "white space" or "freewheeling" mental state during Incubation that allowed the signal from the subconscious to break through to the conscious surface.
@@ -217,7 +217,7 @@ Each "ball" represents a cycle of **Exploration** (widening the scope, generatin
 
 This brings us to a controversial question: Does alcohol make you more creative? The "Ballmer Peak" (referenced in the famous xkcd comic) suggests there is a specific blood-alcohol concentration where coding ability peaks before plummeting.
 
-The science actually supports a nuanced version of this. Alcohol acts as a depressant that inhibits certain brain functions. Specifically, it dampens the **"Feasibility Censor"**—the part of your brain (often the prefrontal cortex) that constantly whispers, "That won't work," or "That's a stupid idea."
+The science actually supports a nuanced version of this. Alcohol acts as a depressant that inhibits certain brain functions. Specifically, it dampens the **"Feasibility Censor"** — the part of your brain (often the prefrontal cortex) that constantly whispers, "That won't work," or "That's a stupid idea."
 
 In engineering, we have a very strong Feasibility Censor. We kill ideas before we even speak them because we instantly judge them as impossible or inefficient. Alcohol lowers this barrier. It allows you to speak the "stupid" idea, which might turn out to be the breakthrough.
 
@@ -242,7 +242,7 @@ Every "Big Idea" in history (the computer, the printing press) required climbing
 
 Finally, we must distinguish between "cool new tech" and actual change. Bill Buxton argues we confuse **Invention** (making something new) with **Innovation** (getting it adopted).
 
-He coined the term **"The Long Nose of Innovation."** We tend to focus on the "short tail" of recent success, but innovation actually has a massive, long lead-up—the "Long Nose."
+He coined the term **"The Long Nose of Innovation."** We tend to focus on the "short tail" of recent success, but innovation actually has a massive, long lead-up — the "Long Nose."
 
 **The Example: The Mouse**
 
@@ -272,7 +272,7 @@ If you want to upgrade your ability to solve complex problems, you need to integ
 **1. Transfer Your Talents (Cross-Pollination)**
 Look for habits or skills you possess in completely unrelated areas and force a transfer to your engineering work.
 
-- _Example:_ If you are a photographer, you are used to framing a shot, looking for lighting, and changing your angle to get a better composition. Apply this to your code. "Photograph" your architecture—create a visual "Research Wall" of your current project components.
+- _Example:_ If you are a photographer, you are used to framing a shot, looking for lighting, and changing your angle to get a better composition. Apply this to your code. "Photograph" your architecture — create a visual "Research Wall" of your current project components.
 - _Example:_ If you do high-intensity interval training (HIIT) or disciplined sports, you understand structure, intervals, and recovery. Apply that rhythm to your coding sprints. Use the discipline of your body to discipline your mind.
 
 **2. The "Streak" Challenge**
@@ -280,7 +280,7 @@ Gamify your output. The internet is full of "30-day creativity challenges." Thes
 
 **3. Aggressive Input Diversity**
 Your brain is an association machine. It connects Dot A to Dot B. If you only feed it computer science textbooks, it can only make connections within computer science. You must widen the pool of "dots."
-Read wildly. Read history, biology, architecture, or fiction. The broader your knowledge base, the more exotic the connections your subconscious can forge. This is the secret sauce of the "Genius"—they are usually just people with a very strange, very wide library of mental references.
+Read wildly. Read history, biology, architecture, or fiction. The broader your knowledge base, the more exotic the connections your subconscious can forge. This is the secret sauce of the "Genius" — they are usually just people with a very strange, very wide library of mental references.
 
 **4. Operationalize Curiosity**
 As we discussed in Part 3, the social environment is critical. You must actively build a workspace where "Why" and "How" are the most valuable words. If you are a lead, you need to incentivize these questions. Remember: **Curiosity breeds creativity.** If you stop asking how things work, you stop inventing ways to make them work better.
@@ -324,14 +324,14 @@ IDEO is the heavyweight champion of Design Thinking. Their deck is a mix of a Cr
 - _The Value:_ If you run a traditional engineering process, it focuses purely on "Problem Solving." This is efficient but sterile. If you focus only on "Creativity," you get chaos. The IDEO cards bridge the gap. They give you specific methods (like "Shadowing" a user or "Bodystorming") to visualize invisible aspects of the problem. They force you to leave your desk.
 
 **5. Collective Action Toolkit (frog design)**
-This is one of the most comprehensive kits available. It goes beyond the single "spark" and helps manage the entire lifecycle of a project. It balances the "Snake Swallowing Tennis Balls" concept—helping you manage the expansion (creativity) and the reduction (selection) phases so the team doesn't burn out or get lost in the weeds.
+This is one of the most comprehensive kits available. It goes beyond the single "spark" and helps manage the entire lifecycle of a project. It balances the "Snake Swallowing Tennis Balls" concept — helping you manage the expansion (creativity) and the reduction (selection) phases so the team doesn't burn out or get lost in the weeds.
 
 ### The Final Paradox
 
 We end this series with the central paradox of your career.
 
 **The more experience you gain, the deeper your "Thinking Canyon" becomes.**
-Your expertise is what makes you valuable—it allows you to solve known problems quickly and safely. But that same expertise is what builds the walls that block innovation. You "know" what works, so you stop looking for what _could_ work.
+Your expertise is what makes you valuable — it allows you to solve known problems quickly and safely. But that same expertise is what builds the walls that block innovation. You "know" what works, so you stop looking for what _could_ work.
 
 Creativity, for a senior engineer, is the **productive overcoming of experience.** It is the ability to look at a problem you have seen a thousand times and choose to see it as if it were the first time.
 
diff --git a/src/content/posts/criminal-thinking.md b/src/content/posts/criminal-thinking.md
index 6c39c9a..5bd0bc7 100644
--- a/src/content/posts/criminal-thinking.md
+++ b/src/content/posts/criminal-thinking.md
@@ -15,13 +15,13 @@ These mental models act as the bridge between a "builder" and a "breaker." Build
 
 ### The ATM: A Public Vault with a Weak Interface
 
-Let's ground this philosophy in a tangible example that has evolved over decades: the ATM. Fundamentally, an ATM is just a safe sitting in public. Physically "cracking" the safe itself is incredibly difficult. It usually requires heavy machinery, explosives, or ripping the entire unit out of the wall with a truck—methods that are loud, dangerous, and conspicuous. Because the vault is hard to break, criminal thinkers target the interface instead. It is significantly easier to intercept the data flow between the customer and the bank than it is to steal the physical cash.
+Let's ground this philosophy in a tangible example that has evolved over decades: the ATM. Fundamentally, an ATM is just a safe sitting in public. Physically "cracking" the safe itself is incredibly difficult. It usually requires heavy machinery, explosives, or ripping the entire unit out of the wall with a truck — methods that are loud, dangerous, and conspicuous. Because the vault is hard to break, criminal thinkers target the interface instead. It is significantly easier to intercept the data flow between the customer and the bank than it is to steal the physical cash.
 
-This is where **Skimmers** come into play. A skimmer is a device added to the existing interaction hardware—the card reader and the keypad—to capture user data.
+This is where **Skimmers** come into play. A skimmer is a device added to the existing interaction hardware — the card reader and the keypad — to capture user data.
 
 There is a fascinating nuance in how we design these interfaces that actually aids the attacker. Have you ever wondered why ATMs force you to type your PIN on a physical, rubberized keypad rather than a sleek touchscreen? It’s a security feature. If you used a touchscreen, software could log the coordinates of your tap (a software keylogger). Even more simply, the grease from your fingers would leave residual smudges on the screen, allowing a thief to shine a light on the glass and see exactly which numbers you pressed. By using a physical keypad, the system offloads authentication to the card itself without storing the PIN in an easily accessible software layer.
 
-However, this physical separation creates a new vulnerability. Because the keypad is a distinct physical component, it can be manipulated. Attackers have developed overlay keypads—thin, realistic-looking plastic shells that sit directly on top of the real keypad. When you type your PIN, you are actually pressing the attacker’s buttons, which record the keystrokes and pass the pressure down to the real buttons below. The transaction works perfectly, but your PIN has been compromised.
+However, this physical separation creates a new vulnerability. Because the keypad is a distinct physical component, it can be manipulated. Attackers have developed overlay keypads — thin, realistic-looking plastic shells that sit directly on top of the real keypad. When you type your PIN, you are actually pressing the attacker’s buttons, which record the keystrokes and pass the pressure down to the real buttons below. The transaction works perfectly, but your PIN has been compromised.
 
 We can see this vulnerability even without high-tech overlays. If you look closely at older keypads, you can sometimes see the PIN simply by observing the wear and tear. If the "1," "2," "3," and "4" keys are rubbed smooth while the rest are dusty, the PIN is almost certainly a permutation of those digits. This is the "Smoker’s Finger" effect: the physical evidence of digital secrets.
 
@@ -29,7 +29,7 @@ We can see this vulnerability even without high-tech overlays. If you look close
 
 A few years ago, a security researcher named Ben Tedesco uploaded a video that went viral. He was visiting St. Stephen’s Cathedral (Stephansplatz) in Vienna and spotted something off about an ATM. In the video, he grabs the green plastic housing surrounding the card slot and gives it a firm wiggle. With a bit of force, the entire plastic molding pops off. It was a 3D-printed replica containing magnetic read heads and a battery, designed to sit over the real slot and skim the magnetic stripe data as the card was inserted.
 
-It was a great catch, but here is the terrifying detail that most people—including Tedesco at the moment—missed. He found the card skimmer, but he missed the second half of the apparatus.
+It was a great catch, but here is the terrifying detail that most people — including Tedesco at the moment — missed. He found the card skimmer, but he missed the second half of the apparatus.
 
 To steal money, you need two things: the card data (PAN) and the PIN. The plastic overlay he removed only captured the card data. To get the PIN, the attackers had installed a micro-camera hidden in a molding strip directly above the keypad. This camera was angled perfectly to record the user's fingers as they typed. The attackers had covered all bases, and the hardware was designed to blend seamlessly into the machine's aesthetic. It is a perfect example of criminal competence: they didn't just hack the machine; they engineered a physical overlay that mimicked the industrial design of the bank's hardware.
 
@@ -37,7 +37,7 @@ To steal money, you need two things: the card data (PAN) and the PIN. The plasti
 
 The relationship between security engineers and criminals is a perpetual arms race. Every time we introduce a new defense, the "criminal thinker" finds a workaround.
 
-When skimming became an epidemic, the industry moved from magnetic stripes to **EMV Chips**. The logic was that chips couldn't be cloned as easily as a magnetic stripe. Did this stop the criminals? No. It just changed their vector. We started seeing "Shimmers"—incredibly thin, flexible circuit boards that slide into the card slot _with_ the card, sitting between the chip and the reader to intercept the communication.
+When skimming became an epidemic, the industry moved from magnetic stripes to **EMV Chips**. The logic was that chips couldn't be cloned as easily as a magnetic stripe. Did this stop the criminals? No. It just changed their vector. We started seeing "Shimmers" — incredibly thin, flexible circuit boards that slide into the card slot _with_ the card, sitting between the chip and the reader to intercept the communication.
 
 Then came "Deep Insert" skimmers. These are wafer-thin devices that are shoved deep inside the machine, completely invisible from the outside, utilizing tiny batteries and storage to harvest data for weeks.
 
@@ -53,11 +53,11 @@ A chilling example of a hybrid attack was discovered in the credit card terminal
 
 Every day, these devices would wake up, bundle the captured credit card numbers, and transmit them via the mobile network to a phone number in Lahore, Pakistan. The sophistication here is high: the attack was hardware-based, but the exfiltration was purely telecommunications.
 
-The only reason this was discovered wasn't because of a software audit or a firewall alert. It was discovered because a security guard at the store noticed that his own cell phone was making that rhythmic "buzzing" interference noise you hear when a device is transmitting data nearby. He heard the interference near the checkout counter when no one was using a phone, realized something was broadcasting, and called the police. This incident underscores that criminal thinking is global, hardware-agnostic, and often invisible until a side channel—like audio interference—gives it away.
+The only reason this was discovered wasn't because of a software audit or a firewall alert. It was discovered because a security guard at the store noticed that his own cell phone was making that rhythmic "buzzing" interference noise you hear when a device is transmitting data nearby. He heard the interference near the checkout counter when no one was using a phone, realized something was broadcasting, and called the police. This incident underscores that criminal thinking is global, hardware-agnostic, and often invisible until a side channel — like audio interference — gives it away.
 
 ---
 
-_Coming up in Part 2: We leave the hardware behind to profile the "Black Hat"—tracing their evolution from curious pranksters to the ruthless architects of the malware economy._
+_Coming up in Part 2: We leave the hardware behind to profile the "Black Hat" — tracing their evolution from curious pranksters to the ruthless architects of the malware economy._
 
 ## Part 2: Profiling the Adversary – Motivations & The Malware Economy
 
@@ -73,13 +73,13 @@ It is also worth debunking a persistent stereotype right now: the image of the h
 
 If we trace the timeline of cyber threats, we see a distinct shift in motivation. In the early days, hacking was largely driven by curiosity, intellectual challenge, and a bit of ego. It was about seeing if you could get into a system just to prove it was possible. But as the internet matured, the "why" changed dramatically.
 
-Today, malware is a business model. We often talk about "Internet Background Radiation"—the constant, low-level hum of automated attacks hitting every public IP address. This isn't personal; it's capitalism. Hackers make money by aggregating massive fleets of compromised home computers—bots—and leasing them out. They earn commissions for every piece of spyware or adware they successfully plant on an infected machine. As discussed in a 2021 TWiT podcast segment, this commercialization is the primary engine driving modern threats. The romantic idea of the lone genius has been replaced by the reality of the supply chain manager.
+Today, malware is a business model. We often talk about "Internet Background Radiation" — the constant, low-level hum of automated attacks hitting every public IP address. This isn't personal; it's capitalism. Hackers make money by aggregating massive fleets of compromised home computers — bots — and leasing them out. They earn commissions for every piece of spyware or adware they successfully plant on an infected machine. As discussed in a 2021 TWiT podcast segment, this commercialization is the primary engine driving modern threats. The romantic idea of the lone genius has been replaced by the reality of the supply chain manager.
 
 ### The DDoS Timeline: From Pranks to Politics
 
-A perfect illustration of this evolution is the history of Distributed Denial of Service (DDoS) attacks. Fifteen years ago, if you looked at a timeline of DDoS incidents, the motivations were chaotic. They were often "for the lulz"—kids testing scripts to knock a game server offline or just to see what would break. The attacks were characterized by a lack of clear purpose.
+A perfect illustration of this evolution is the history of Distributed Denial of Service (DDoS) attacks. Fifteen years ago, if you looked at a timeline of DDoS incidents, the motivations were chaotic. They were often "for the lulz" — kids testing scripts to knock a game server offline or just to see what would break. The attacks were characterized by a lack of clear purpose.
 
-Over the last decade and a half, that randomness has hardened into strategy. The motivation shifted first to extortion—"pay us 5 Bitcoin or your e-commerce site stays down"—and then to political warfare. We now see massive spikes in traffic directed against gaming companies or media outlets that appear to be retaliation for sociopolitical stances. While it’s hard to prove attribution in real-time, the correlation between controversial public statements and massive packet floods is undeniable.
+Over the last decade and a half, that randomness has hardened into strategy. The motivation shifted first to extortion — "pay us 5 Bitcoin or your e-commerce site stays down" — and then to political warfare. We now see massive spikes in traffic directed against gaming companies or media outlets that appear to be retaliation for sociopolitical stances. While it’s hard to prove attribution in real-time, the correlation between controversial public statements and massive packet floods is undeniable.
 
 The scale has also become terrifying. Since 2008, the sheer volume of DDoS attacks has increased roughly 30-fold. We don't measure these campaigns in "attacks per day" anymore; we measure them in "attacks per hour." And thanks to the efficiency of modern tools, attackers can do more with less. A few years ago, you might have needed a botnet of 1,000,000 infected devices to cripple a target. Today, with smarter application-layer attacks and the assistance of generative AI to script complex attack vectors, you might achieve the same result with only 50,000 bots. The barrier to entry has lowered, but the destructive potential has skyrocketed.
 
@@ -87,7 +87,7 @@ The scale has also become terrifying. Since 2008, the sheer volume of DDoS attac
 
 The profit motive has reshaped entire economies. As reported by the Guardian in October 2025, we are witnessing the rise of "cybercrime villages" in places like rural India. As traditional agricultural jobs vanish, entire regions are pivoting to call centers dedicated to global fraud.
 
-This is "scamming as farming." The goal is to harvest capital from victims on the other side of the planet—stealing identities, draining bank accounts, and installing remote access trojans. This is a global information system with no corresponding global justice system. A scammer in a jurisdiction with lax enforcement faces almost zero risk of prosecution for defrauding a grandmother in Ohio. This accountability vacuum leads to bizarre outcomes, such as the rise of "glitterbombing" vigilantes like Mark Rober, who use engineering to exact the only form of justice available: pranking the scammers back. It’s entertaining, but it highlights a systemic failure of law enforcement to adapt to a borderless crime wave.
+This is "scamming as farming." The goal is to harvest capital from victims on the other side of the planet — stealing identities, draining bank accounts, and installing remote access trojans. This is a global information system with no corresponding global justice system. A scammer in a jurisdiction with lax enforcement faces almost zero risk of prosecution for defrauding a grandmother in Ohio. This accountability vacuum leads to bizarre outcomes, such as the rise of "glitterbombing" vigilantes like Mark Rober, who use engineering to exact the only form of justice available: pranking the scammers back. It’s entertaining, but it highlights a systemic failure of law enforcement to adapt to a borderless crime wave.
 
 ### Ransomware: The Predator of Infrastructure
 
@@ -103,7 +103,7 @@ The human cost of this is not theoretical. In 2020, a patient in Germany died af
 
 ---
 
-_Coming up in Part 3: We examine the "Opportunity" that lets these attacks happen—from the persistence of "Zero Day" vulnerabilities and bad code to the looming threat of AI-generated exploits._
+_Coming up in Part 3: We examine the "Opportunity" that lets these attacks happen — from the persistence of "Zero Day" vulnerabilities and bad code to the looming threat of AI-generated exploits._
 
 ## Part 3: The Opportunity Landscape – Zero Days, Policy Failures, and AI
 
@@ -129,9 +129,9 @@ On the other side, Black Hats are using the same tools to sharpen their attacks.
 
 ### The Admin Gap
 
-We often blame the "end-user" for security failures—the receptionist who clicked a link or the grandfather who shared his password. But we need to turn that scrutiny toward the professionals. System administrators and IT staff are often assumed to be the "strong link," but research challenges this.
+We often blame the "end-user" for security failures — the receptionist who clicked a link or the grandfather who shared his password. But we need to turn that scrutiny toward the professionals. System administrators and IT staff are often assumed to be the "strong link," but research challenges this.
 
-Two scientific studies from the environment of TU Wien investigated how well system administrators actually understand the security measures they deploy. The titles alone—_On the Usability of Deploying HTTPS_ and _If HTTPS Were Secure, I Wouldn’t Need 2FA_—point to the problem. The findings were concerning: not only were there significant knowledge gaps among the professionals, but the security products themselves suffered from massive usability issues.
+Two scientific studies from the environment of TU Wien investigated how well system administrators actually understand the security measures they deploy. The titles alone — _On the Usability of Deploying HTTPS_ and _If HTTPS Were Secure, I Wouldn’t Need 2FA_ — point to the problem. The findings were concerning: not only were there significant knowledge gaps among the professionals, but the security products themselves suffered from massive usability issues.
 
 If the tool for configuring a secure server is confusing, the administrator will likely misconfigure it. This is a "System 2" failure. It’s not just that people are lazy; it’s that the complexity of modern infrastructure has outpaced the usability of our management tools. When we say "humans are the weakest link," we must include the architects and administrators in that statement. A poorly designed interface for a firewall is just as dangerous as a weak password.
 
@@ -145,7 +145,7 @@ _Coming up in Part 4: We dive into the psychology of the "Human Factor," explori
 
 One of the most powerful enablers of criminal thinking is a concept that predates the internet entirely: distance. It is a well-documented psychological phenomenon that it is easier to be cruel, aggressive, or destructive when you don't have to look your victim in the eye. We see this in the toxicity of anonymous online comment sections, but in the realm of cybersecurity, this distance transforms crime into a game.
 
-Hackers operate remotely, far removed from the tangible consequences of their code. A chilling demonstration of this was the famous remote hacking of a Jeep Cherokee by researchers Charlie Miller and Chris Valasek. In their demonstration, they didn't just tamper with the radio; they killed the engine while the car was driving down a highway. In the video documentation of the hack, you can hear the researchers laughing as the driver struggles with a dead vehicle. To them, sitting comfortably miles away with their laptops, it was an intellectual triumph—a successful execution of code. To the driver, it was a terrifying loss of physical control. This emotional disconnect allows attackers to perform dangerous acts with the casual demeanor of someone playing a video game, making the threat landscape far more volatile than traditional physical crime.
+Hackers operate remotely, far removed from the tangible consequences of their code. A chilling demonstration of this was the famous remote hacking of a Jeep Cherokee by researchers Charlie Miller and Chris Valasek. In their demonstration, they didn't just tamper with the radio; they killed the engine while the car was driving down a highway. In the video documentation of the hack, you can hear the researchers laughing as the driver struggles with a dead vehicle. To them, sitting comfortably miles away with their laptops, it was an intellectual triumph — a successful execution of code. To the driver, it was a terrifying loss of physical control. This emotional disconnect allows attackers to perform dangerous acts with the casual demeanor of someone playing a video game, making the threat landscape far more volatile than traditional physical crime.
 
 ### Professionals Target People
 
@@ -177,7 +177,7 @@ The worker made the transfer. It was only later that he discovered the truth: ev
 
 ---
 
-_Coming up in Part 5: The final frontier—how billions of cheap, unsecure IoT devices are creating a zombie army, and why we might need a "Center for Disease Control" for the internet._
+_Coming up in Part 5: The final frontier — how billions of cheap, unsecure IoT devices are creating a zombie army, and why we might need a "Center for Disease Control" for the internet._
 
 ## Part 5: The IoT Apocalypse & A New Defense Paradigm
 
@@ -187,13 +187,13 @@ While the security industry loves to hyperventilate about Artificial Intelligenc
 
 We need to make a sharp distinction here. When you buy a high-end "always-on" device like a Google Home or Amazon Echo, you are generally buying into a managed ecosystem. These companies have security teams, and crucially, they push firmware updates. If a vulnerability is found, it gets patched.
 
-The danger lies in the "long tail" of cheap electronics. The market is flooded with white-label "smart" devices produced by manufacturers that act like mayflies—they exist for a year or two to flood the market with cheap hardware, and then they vanish. These devices are sold with no plan for software maintenance. They have hardcoded passwords (often just "admin/admin"), open Telnet ports, and unpatchable firmware. Once a vulnerability is discovered in one of these "zombie" devices, it is there forever.
+The danger lies in the "long tail" of cheap electronics. The market is flooded with white-label "smart" devices produced by manufacturers that act like mayflies — they exist for a year or two to flood the market with cheap hardware, and then they vanish. These devices are sold with no plan for software maintenance. They have hardcoded passwords (often just "admin/admin"), open Telnet ports, and unpatchable firmware. Once a vulnerability is discovered in one of these "zombie" devices, it is there forever.
 
 This creates a terrifying dynamic: we are filling our homes and offices with millions of tiny, powerful computers that are permanently vulnerable. And because the people buying them are regular consumers, not sysadmins, these devices are almost never monitored. They just sit there, connected to the internet, waiting to be conscripted.
 
 ### Mirai and the Million-Bot Army
 
-The wake-up call for this threat was the **Mirai Botnet** in 2016. Mirai didn't attack sophisticated servers; it scanned the internet for those cheap IoT devices—digital video recorders (DVRs) and IP cameras—and tried default usernames and passwords. It worked terrifyingly well.
+The wake-up call for this threat was the **Mirai Botnet** in 2016. Mirai didn't attack sophisticated servers; it scanned the internet for those cheap IoT devices — digital video recorders (DVRs) and IP cameras — and tried default usernames and passwords. It worked terrifyingly well.
 
 Mirai amassed an army of hundreds of thousands of hijacked devices. When the controllers gave the order, this swarm launched a Distributed Denial of Service (DDoS) attack of unprecedented scale against Dyn, a major DNS provider. The result? Huge chunks of the internet, including Twitter, Netflix, and Reddit, simply vanished for users across the US and Europe.
 
@@ -231,7 +231,7 @@ Instead of blaming the user, this institution would operate at a systemic level.
 - **Public Warnings:** Issuing authoritative alerts about specific dangerous products (e.g., "Do not buy Brand X Baby Monitor").
 - **Hygiene Education:** Moving beyond "make a strong password" to teaching genuine digital literacy and resilience.
 
-We cannot "firewall" our way out of this individually. Resilience comes from systemic changes—automated backups, incident response protocols, and diversity in software ecosystems to prevent monoculture failures. We need to stop treating security as a feature and start treating it as a prerequisite for civilization, backed by policy, law, and robust institutions.
+We cannot "firewall" our way out of this individually. Resilience comes from systemic changes — automated backups, incident response protocols, and diversity in software ecosystems to prevent monoculture failures. We need to stop treating security as a feature and start treating it as a prerequisite for civilization, backed by policy, law, and robust institutions.
 
 This brings us to the edge of technology and into the realm of governance. But that is a story for the next chapter: **Policy Thinking**.
 
diff --git a/src/content/posts/critical-thinking.md b/src/content/posts/critical-thinking.md
index b5996d5..c756caa 100644
--- a/src/content/posts/critical-thinking.md
+++ b/src/content/posts/critical-thinking.md
@@ -15,10 +15,10 @@ That sounds like a solid definition, but it’s a bit of a "list of ingredients"
 
 To make this concrete, let's look at the framework provided by Otto Kruse, a psychologist and writing researcher who led the Centre for Academic Writing at the University of Zurich. He breaks it down into four distinct buckets:
 
-1.  **Self-directed and self-aligned thinking:** This refers to metacognitive abilities—thinking about your thinking. It involves maintaining intellectual autonomy and adhering to quality criteria for your own thoughts.
+1.  **Self-directed and self-aligned thinking:** This refers to metacognitive abilities — thinking about your thinking. It involves maintaining intellectual autonomy and adhering to quality criteria for your own thoughts.
 2.  **Rational procedure:** This is crucial when things get messy. How do you handle ill-defined problems or genuine ignorance? You need reflected, methodical thinking, not just guessing.
 3.  **Skeptical thinking:** This is the critical reflection and testing of all knowledge assumptions. It implies a high awareness of error and deception. You have to assume you could be wrong.
-4.  **Habits of thought:** This treats critical thinking as a personality feature—a careful, deliberate handling of facts and knowledge as a default mode of operation.
+4.  **Habits of thought:** This treats critical thinking as a personality feature — a careful, deliberate handling of facts and knowledge as a default mode of operation.
 
 While one might not agree with every single point Kruse makes, his positioning of critical thinking as a central educational goal is vital. He argues that this is the core of higher education and a service universities provide to society. Kruse also dropped a line that is incredibly relevant for us: "Writing is the royal road to learning to think." As computer scientists, we write a staggering amount. We just happen to write in languages designed to give instructions to machines rather than communicate with humans. Despite that difference, the ability to read with deep comprehension (reading skills) correlates strongly with programming performance.
 
@@ -57,7 +57,7 @@ Practicing this list is incredibly difficult. It is worth noting that in today's
 
 ### The Model of Thinking
 
-To understand why we fail at the standards listed above, we need a model. We aren't trying to build a biological model of the brain here—we are building a conceptual model of _thinking_.
+To understand why we fail at the standards listed above, we need a model. We aren't trying to build a biological model of the brain here — we are building a conceptual model of _thinking_.
 
 Models are simplified summaries and reflections of what we observe. They aren't necessarily "true" or "false" in a binary sense; they are useful or not useful. If a model explains our observations without breaking established knowledge, it works. It gives us a vocabulary. However, models are always incomplete. We need to know where the model ends. Our model here does not distinguish much between perception and thinking. The moment light hits the retina and stimulates sensory cells, we are "thinking" in this framework.
 
@@ -70,7 +70,7 @@ Thinking consists of many interacting parts. Some are fast, some are slow. Some
 
 Imagine someone throws a ball at you unexpectedly. You react. You throw your hands up to deflect or catch it. This is a stunning computational feat. If you tried to use your "rational thinking" (the conscious component) to calculate the trajectory, solve the differential equations, and move your muscles, you would get hit in the face long before you finished the first calculation. Even for robots, catching a ball is an extraordinary task.
 
-In that split second, your rational thinking steps aside and lets other components—fast, automated, physical components—take the lead. Whether you catch it depends on your practice, but the reaction happens without "you" (your conscious self) doing it.
+In that split second, your rational thinking steps aside and lets other components — fast, automated, physical components — take the lead. Whether you catch it depends on your practice, but the reaction happens without "you" (your conscious self) doing it.
 
 We see this interference in other areas. Have you ever tried to carry a glass of water filled to the very brim? If you stare at the water and consciously try not to spill it, it becomes incredibly difficult. Your hand shakes. But if you look away and let your body handle it, you often spill less. When the conscious, rational mind gets involved in tasks it isn't suited for, it becomes a bottleneck.
 
@@ -80,7 +80,7 @@ There is a fascinating example of this in Timothy Gallwey’s book, _The Inner G
 
 In 1973, Harry Reasoner, a TV host, invited Gallwey to prove this on _The Reasoner Report_. Gallwey took a woman who was completely unathletic and had never played tennis. In **20 minutes**, he had her playing decent tennis.
 
-How? He kept her conscious mind busy with trivial tasks (like saying "bounce" when the ball hit the ground and "hit" when it hit the racket) so it couldn't critique her form. By distracting the "over-critical" component, the other components of her thinking—the ones that handle spatial awareness and motor control—could work without interference.
+How? He kept her conscious mind busy with trivial tasks (like saying "bounce" when the ball hit the ground and "hit" when it hit the racket) so it couldn't critique her form. By distracting the "over-critical" component, the other components of her thinking — the ones that handle spatial awareness and motor control — could work without interference.
 
 The participant described it perfectly: _"Every time I did start to think, things went wrong. But if I just stop thinking, the body seems to know what to do... All of a sudden, everything became effortless."_
 
@@ -88,7 +88,7 @@ This reveals a critical flaw in our architecture: **The components of our thinki
 
 ### The Cognitive Miser
 
-Neurologically, we know that conscious thinking is a tiny fraction of brain activity—estimates range from 1% to 10%. We have a "Fast System" (the choir of fast components) and a "Slow System" (the conscious, rational mind).
+Neurologically, we know that conscious thinking is a tiny fraction of brain activity — estimates range from 1% to 10%. We have a "Fast System" (the choir of fast components) and a "Slow System" (the conscious, rational mind).
 
 Here is the problem: The slow components require a tremendous amount of energy. The fast components are cheap and efficient.
 
@@ -106,7 +106,7 @@ _In the next part, we will open up the "Cognitive Bias Cheat Sheet" and systemat
 
 ## Part 2: The Cognitive Miser & The Bias Cheat Sheet
 
-We established in the previous section that the human brain operates on a dual-system architecture. You have the fast, automated components that handle ball-catching and instant reactions, and you have the slow, deliberate conscious mind that handles complex logic. The critical insight here is that your brain is fundamentally lazy. In evolutionary biology, we call this being a cognitive miser. The slow, conscious system is metabolically expensive to run, so the brain constantly tries to outsource cognitive load to the cheaper, faster system. It uses heuristics—mental shortcuts—to solve complex problems with minimal energy. When these shortcuts work, we call it intuition. When they fail, we call them cognitive biases.
+We established in the previous section that the human brain operates on a dual-system architecture. You have the fast, automated components that handle ball-catching and instant reactions, and you have the slow, deliberate conscious mind that handles complex logic. The critical insight here is that your brain is fundamentally lazy. In evolutionary biology, we call this being a cognitive miser. The slow, conscious system is metabolically expensive to run, so the brain constantly tries to outsource cognitive load to the cheaper, faster system. It uses heuristics — mental shortcuts — to solve complex problems with minimal energy. When these shortcuts work, we call it intuition. When they fail, we call them cognitive biases.
 
 This isn't a random glitch; it is a feature. We are under stringent selection pressure to be only as smart as we need to be to survive. The result is that we don't make rational decisions based on all available data; we make pragmatic decisions based on what is available and easy to process. To understand exactly how this breaks down, we can look at the taxonomy created by John Manoogian and Buster Benson, often called the Cognitive Bias Cheat Sheet. They categorized hundreds of biases into four distinct problems the brain is trying to solve: dealing with too much information, lack of meaning, the need to act fast, and the limits of memory.
 
@@ -118,7 +118,7 @@ A classic example here is the availability heuristic. We judge the frequency or
 
 This filtering mechanism also leads to the confirmation bias, perhaps the most dangerous of them all. Once we adopt an opinion, we act like a filter that only lets in supporting evidence. We accept confirming data as high-quality facts and dismiss contradictory data as noise or exceptions. Francis Bacon identified this back in 1620, noting that human understanding forces everything else to add support and agreement to its adopted opinions. This is the engine behind modern "filter bubbles." We are not just passively receiving information; we are actively constructing a reality that reinforces what we already believe.
 
-We also see this in how we perceive value and choices. The anchoring effect describes how we use the first piece of information we see as a reference point for everything that follows. If you see a price tag of $2000 crossed out next to a price of $1000, the TV seems cheap. If you just saw $1000, it might seem expensive. Similarly, the framing effect changes our decision based on how the data is presented. We prefer a product labeled "95% fat-free" over one labeled "5% fat," even though they are identical. We are also subject to inattentional blindness. When we focus hard on one thing—like counting passes in a basketball game—we can completely miss massive, obvious anomalies, like a person in a gorilla suit walking through the frame. This is known as the Monkey Business Illusion.
+We also see this in how we perceive value and choices. The anchoring effect describes how we use the first piece of information we see as a reference point for everything that follows. If you see a price tag of $2000 crossed out next to a price of $1000, the TV seems cheap. If you just saw $1000, it might seem expensive. Similarly, the framing effect changes our decision based on how the data is presented. We prefer a product labeled "95% fat-free" over one labeled "5% fat," even though they are identical. We are also subject to inattentional blindness. When we focus hard on one thing — like counting passes in a basketball game — we can completely miss massive, obvious anomalies, like a person in a gorilla suit walking through the frame. This is known as the Monkey Business Illusion.
 
 ### Problem 2: Not Enough Meaning
 
@@ -255,7 +255,7 @@ _In the next part, we will crack open the "Black Box" of decision-making algorit
 
 ## Part 4: The Black Box (Manipulation, Decisions, & Snake Oil)
 
-We have looked at how human bias infects data and how that data infects algorithms. But there is a darker layer to this stack. What happens when these systems are not just biased by accident, but manipulated by design? And worse, what happens when we hand over life-altering decisions—who goes to jail, who gets a loan, who gets a job—to "Black Box" systems that we are legally forbidden from auditing?
+We have looked at how human bias infects data and how that data infects algorithms. But there is a darker layer to this stack. What happens when these systems are not just biased by accident, but manipulated by design? And worse, what happens when we hand over life-altering decisions — who goes to jail, who gets a loan, who gets a job — to "Black Box" systems that we are legally forbidden from auditing?
 
 ### The Architecture of Manipulation
 
@@ -271,7 +271,7 @@ I tracked this personally:
 - **2021:** It finally moved to the first entry on **Page 5**.
 - **November 2022:** It dropped to **Page 11**.
 
-This timeline reveals two things. First, the "truth" on the internet is malleable and subject to gaming by motivated interest groups. Second, Google _can_ fix it, but usually only after manual intervention or algorithm updates that take years to propagate. We are relying on a single technology—"Googling" has become a verb—that cannot reliably protect itself from being hijacked by bad actors.
+This timeline reveals two things. First, the "truth" on the internet is malleable and subject to gaming by motivated interest groups. Second, Google _can_ fix it, but usually only after manual intervention or algorithm updates that take years to propagate. We are relying on a single technology — "Googling" has become a verb — that cannot reliably protect itself from being hijacked by bad actors.
 
 **Adversarial Attacks & Russian Propaganda**
 It’s not just search rankings. AI systems are now being poisoned. We have seen instances where well-funded disinformation networks (e.g., Russian propaganda) actively infect the training data of Western AI tools. Since LLMs (Large Language Models) ingest the internet to learn, if you flood the internet with specific narratives, the AI learns those narratives as fact.
@@ -363,7 +363,7 @@ Accepting that second option requires us to live with uncertainty. It requires u
 
 This is where the "Probabilistic Worldview" comes in. Instead of asking "Is this true?", you should ask "How likely is this to be true?" You treat knowledge not as a binary switch (True/False), but as a confidence slider (0% to 100%).
 
-A good argument is simply a process that moves that slider. It provides premises that make the conclusion _more likely_ to be true. You will never reach 100% certainty—that doesn't exist outside of pure mathematics—but you can reach a level of confidence high enough to act upon.
+A good argument is simply a process that moves that slider. It provides premises that make the conclusion _more likely_ to be true. You will never reach 100% certainty — that doesn't exist outside of pure mathematics — but you can reach a level of confidence high enough to act upon.
 
 ### The Doubt Factory and The "One Study" Fallacy
 
@@ -371,7 +371,7 @@ One of the biggest enemies of this probabilistic approach is the modern media cy
 
 We have a cognitive bias (Confirmation Bias) that makes us latch onto any piece of evidence that supports our existing view. The media ecosystem exploits this by pumping out headlines based on single, often flawed, studies. You will see a headline: "New Study Proves Chocolate Cures Cancer."
 
-In the scientific community, a single study proves almost nothing. It is a data point. It might be an outlier; it might be p-hacked; it might be poorly designed. Real knowledge comes from **consensus**—the aggregation of many studies over time pointing in the same direction.
+In the scientific community, a single study proves almost nothing. It is a data point. It might be an outlier; it might be p-hacked; it might be poorly designed. Real knowledge comes from **consensus** — the aggregation of many studies over time pointing in the same direction.
 
 However, the "Doubt Factory" operates by funding or highlighting studies that cast doubt on the consensus. This was the strategy of the tobacco industry (casting doubt on the lung cancer link) and the fossil fuel industry (casting doubt on climate change). They don't need to prove they are right; they just need to introduce enough noise to keep your probability slider stuck in the middle, preventing you from taking action.
 
@@ -383,7 +383,7 @@ To defend against this, you need a mental firewall. When you see a claim, run a
 
 ### Debugging Arguments: Logical Fallacies
 
-Just as we debug code for syntax errors, we must debug arguments for logical errors. These are known as **Logical Fallacies**. There are dozens of them, and learning to spot them is like learning to read a stack trace—it tells you exactly where the logic crashed.
+Just as we debug code for syntax errors, we must debug arguments for logical errors. These are known as **Logical Fallacies**. There are dozens of them, and learning to spot them is like learning to read a stack trace — it tells you exactly where the logic crashed.
 
 For example, the **Strawman Fallacy** is when someone attacks a distorted, weaker version of your argument rather than the argument itself. The **Ad Hominem** is attacking the person rather than the point. The **Slippery Slope** assumes that step A necessarily leads to extreme step Z.
 
@@ -405,7 +405,7 @@ The goal is to guide the person to realize, on their own, that their methodology
 
 We have covered a lot of ground, from the neurons firing in your amygdala to the SQL queries in a recidivism algorithm.
 
-If there is one takeaway, it is this: **You are not a neutral observer.** You are a machine built to jump to conclusions, protect your ego, and save energy. The systems you build—the software, the AI, the data pipelines—will inherit those flaws unless you actively fight against them.
+If there is one takeaway, it is this: **You are not a neutral observer.** You are a machine built to jump to conclusions, protect your ego, and save energy. The systems you build — the software, the AI, the data pipelines — will inherit those flaws unless you actively fight against them.
 
 As computer scientists and engineers, we have a unique power. We are the ones building the digital infrastructure of reality. We decide how the search algorithm ranks truth. We decide which data features matter for a loan application. We decide whether a chatbot optimizes for engagement or accuracy.
 
@@ -413,7 +413,7 @@ This is why "Human-Centered Computing" and ethics are now core parts of the comp
 
 Critical thinking is not a certificate you hang on the wall. It is a runtime process. It is the constant, exhausting background job of asking: "Why do I believe this? What if I'm wrong? And who is being left out of this dataset?"
 
-It is hard work. It feels unnatural. But as we move into an age of automated decisions and AI-generated reality, it is the only thing that keeps us—and our technology—sane.
+It is hard work. It feels unnatural. But as we move into an age of automated decisions and AI-generated reality, it is the only thing that keeps us — and our technology — sane.
 
 ---
 
diff --git a/src/content/posts/design-thinking.md b/src/content/posts/design-thinking.md
index 4a41e4f..b69f55f 100644
--- a/src/content/posts/design-thinking.md
+++ b/src/content/posts/design-thinking.md
@@ -9,7 +9,7 @@ To understand why modern software often frustrates us, we have to look at the fa
 
 ### The Functionality Monster and the Context Switch
 
-Consider the classic "Bulk Rename Utility." This type of software attempts to solve a very specific, annoying problem: renaming a massive number of files in a file manager. For those comfortable with a Command Line Interface (CLI), this is trivial—provided you remember the correct regex or syntax for the Linux `rename` command. But for the average user, the CLI is a barrier. Early GUI developers saw this and decided to build visual tools. The result, however, is often a "monster" dialog box. Imagine a single window where a developer has attempted to cram every possible permutation of renaming logic—timestamps, numbering, extension handling, replacement strings—into one view.
+Consider the classic "Bulk Rename Utility." This type of software attempts to solve a very specific, annoying problem: renaming a massive number of files in a file manager. For those comfortable with a Command Line Interface (CLI), this is trivial — provided you remember the correct regex or syntax for the Linux `rename` command. But for the average user, the CLI is a barrier. Early GUI developers saw this and decided to build visual tools. The result, however, is often a "monster" dialog box. Imagine a single window where a developer has attempted to cram every possible permutation of renaming logic — timestamps, numbering, extension handling, replacement strings — into one view.
 
 The issue with these utilities isn't that they lack functionality; it’s that they prioritize the _existence_ of the function over the _human_ who uses it. This is the archetype of "Function Follows Function." The developer assumes that as long as the code can technically perform the task, the job is done. The layout, hierarchy, and clarity are afterthoughts, often decided by where a button happens to fit on the grid rather than where it makes cognitive sense. This points to a deeper issue in engineering culture: the technical capability and ease of implementation are valued higher than the cognitive cost paid by the user.
 
@@ -25,7 +25,7 @@ This tragedy highlights a critical paradox in automation. We build systems to au
 
 In Computer Science and engineering, we love the "Problem-Based" approach. It feels rigorous. We define a problem, we analyze it, and then we solve it. It aligns with the "Feynman Algorithm" of thinking: write down the problem, think very hard, write down the solution. This is deeply embedded in how we teach programming and project management. The classic Waterfall model is built on this foundation: you create a massive Requirements Document (often called a _Pflichtenheft_) that defines the problem in exhaustive detail. The assumption is that if we work hard enough on this document, we will arrive at a single, immutable, "true" definition of the problem.
 
-The industry has historically relied on this document to answer all future questions during implementation. It assumes the problem exists independently of us, sitting there like a rock waiting to be measured. But reality disagrees. The Standish Group’s Chaos Report (2015) analyzed 50,000 projects and found that this problem-based, "define it first" approach doesn't just fail to guarantee success—it actually increases the risk of failure.
+The industry has historically relied on this document to answer all future questions during implementation. It assumes the problem exists independently of us, sitting there like a rock waiting to be measured. But reality disagrees. The Standish Group’s Chaos Report (2015) analyzed 50,000 projects and found that this problem-based, "define it first" approach doesn't just fail to guarantee success — it actually increases the risk of failure.
 
 This is where the distinction between "Problem-Based" and "Solution-Based" (Agile) becomes critical. In a solution-based approach, we accept that we don't fully know the problem yet. We create iterations of solutions not just to fix the problem, but to _find_ the problem. The problem definition changes as we try to solve it.
 
@@ -41,7 +41,7 @@ We have known this for decades. In their seminal 1986 paper, _A Rational Design
 
 If most problems aren't "Tame," what are they? In the late 1960s and early 70s, Horst Rittel and Melvin Webber coined the term **"Wicked Problems."** They were looking at social planning, but their findings map perfectly to modern software engineering.
 
-A Wicked Problem is a problem you cannot understand until you have developed a concept of the solution. You cannot gather information meaningfully unless you understand the problem, but you can't understand the problem without information. It is a circular paradox. Unlike Tame Problems, Wicked Problems have no "stopping rule"—you don't stop because you solved it; you stop because you ran out of money, time, or patience.
+A Wicked Problem is a problem you cannot understand until you have developed a concept of the solution. You cannot gather information meaningfully unless you understand the problem, but you can't understand the problem without information. It is a circular paradox. Unlike Tame Problems, Wicked Problems have no "stopping rule" — you don't stop because you solved it; you stop because you ran out of money, time, or patience.
 
 Here is the deal with Wicked Problems:
 
@@ -58,7 +58,7 @@ This brings us to the core realization: **If humans are involved, every problem
 
 Mathematical thinking works for Tame Problems. It relies on reduction and abstraction to create proofs. If we can model a phenomenon mathematically, we can wield the superpower of the "Proof." But this only covers a tiny fraction of the world. The rest of the world is messy, human, and wicked.
 
-When we treat Wicked Problems as if they were Tame Problems—when we force them into a rigid Waterfall process or a strict Requirements Document—we fail. We see this in "Smart City" diagrams that depict traffic and energy flow but contain no actual humans. We are taming the problem by ignoring the variables that make it difficult. But those variables always come back to bite us. Requirement volatility is consistently cited as the core problem of software engineering. This volatility isn't a bug; it’s a feature of Wicked Problems.
+When we treat Wicked Problems as if they were Tame Problems — when we force them into a rigid Waterfall process or a strict Requirements Document — we fail. We see this in "Smart City" diagrams that depict traffic and energy flow but contain no actual humans. We are taming the problem by ignoring the variables that make it difficult. But those variables always come back to bite us. Requirement volatility is consistently cited as the core problem of software engineering. This volatility isn't a bug; it’s a feature of Wicked Problems.
 
 Design Thinking, therefore, is not about making things pretty. It is the methodology we use to tame the wicked. It is the recognition that problem definition and problem solution must happen simultaneously.
 
@@ -70,7 +70,7 @@ _Coming Up in Part 2: We dive into the history of HCI, why "feature creep" is de
 
 If Part 1 established that "Wicked Problems" are the true final boss of engineering, then Part 2 is about the weapon we chose to fight them. That weapon is Human-Computer Interaction (HCI). We can lay down a fundamental axiom right here, right now: **If humans are involved, every problem becomes a Wicked Problem.**
 
-This isn't just a philosophical stance; it is a practical reality. Human needs are not independent variables. They are deeply entangled with context. If the context changes—say, a user moves from a quiet office to a noisy train—their needs change instantly. This volatility makes it impossible to create those "true" a priori problem formulations we love in engineering. The discipline that emerged around 1980 to tackle this volatility is HCI. It is effectively the scientific application of Design Thinking within computer science.
+This isn't just a philosophical stance; it is a practical reality. Human needs are not independent variables. They are deeply entangled with context. If the context changes — say, a user moves from a quiet office to a noisy train — their needs change instantly. This volatility makes it impossible to create those "true" a priori problem formulations we love in engineering. The discipline that emerged around 1980 to tackle this volatility is HCI. It is effectively the scientific application of Design Thinking within computer science.
 
 Andrea Bianci, a researcher in the field, once framed it perfectly: HCI focuses on designing interactive systems that are both productive and _pleasurable_. This is a massive expansion of the old "Form Follows Function" doctrine. It acknowledges that productivity isn't the only metric; the human experience of using the tool matters. The Association for Computing Machinery (SIGCHI) defines it as the discipline concerned with the design, evaluation, and implementation of interactive computing systems for human use. But even that definition is starting to creak under the weight of reality. As Ben Shneiderman noted back in 2011, HCI has grown from a small, rebellious group of researchers fighting for recognition into a community that impacts the daily lives of every human on earth.
 
@@ -78,7 +78,7 @@ Andrea Bianci, a researcher in the field, once framed it perfectly: HCI focuses
 
 Why is this focus on the human so critical right now? Because of a little thing called "Buxton’s Law." We all know Moore’s Law, which predicts the exponential growth of computing power and capacity. Buxton’s Law acts as the counterweight: while technology’s complexity and capacity skyrocket, **human capacity does not.** Our cognitive bandwidth is roughly the same as it was 50 years ago.
 
-Technological artifacts—software, gadgets, and the "hidden" computers inside everything from washing machines to sex toys—have utilized Moore's Law to pack in more and more functions. This leads to an explosion of complexity in the User Interface. If the machine gets twice as complex every 18 months, but the user doesn't, you have a usability crisis. This necessitates a shift from "Can we build it?" to "Should we build it, and how?"
+Technological artifacts — software, gadgets, and the "hidden" computers inside everything from washing machines to sex toys — have utilized Moore's Law to pack in more and more functions. This leads to an explosion of complexity in the User Interface. If the machine gets twice as complex every 18 months, but the user doesn't, you have a usability crisis. This necessitates a shift from "Can we build it?" to "Should we build it, and how?"
 
 This perspective shifts the center of gravity from the technology to the life of the person using it. Historically, we called this "User-Centered Design," but even that term is problematic. "User" implies a person pressing buttons. But what about the person whose career is decided by an automated HR algorithm? They aren't "using" the software, but they are definitely affected by it. "Human-Centered Design" is better, but "Life-Centered Design" or "Humanity-Centered Design" might be where we need to land, acknowledging that our systems impact the environment and society at large.
 
@@ -109,13 +109,13 @@ Honeywell was horrified. How could a startup outclass them in their own domain?
 
 ### The ROI of Design
 
-This isn't just about feeling good. There is hard data backing the "vibe." The Design Management Institute (DMI) tracks the "Design Value Index," a portfolio of design-centric companies. These companies—who treat design as a core strategy rather than a cost center—consistently outperform the S&P 500 by significant margins (often over 200%).
+This isn't just about feeling good. There is hard data backing the "vibe." The Design Management Institute (DMI) tracks the "Design Value Index," a portfolio of design-centric companies. These companies — who treat design as a core strategy rather than a cost center — consistently outperform the S&P 500 by significant margins (often over 200%).
 
-Design is not a luxury. It is not a coat of paint you apply at the end of the engineering process. It is a core component of business strategy. If you ignore it, you end up like the old Honeywell—rich, established, and waiting to be disrupted by a thermostat that actually knows what it feels like to be human.
+Design is not a luxury. It is not a coat of paint you apply at the end of the engineering process. It is a core component of business strategy. If you ignore it, you end up like the old Honeywell — rich, established, and waiting to be disrupted by a thermostat that actually knows what it feels like to be human.
 
 ---
 
-_Coming Up in Part 3: We get into the gritty theory of "Inquiry"—why you have to build things to understand them—and the specific Heuristics you need to memorize to stop building garbage interfaces._
+_Coming Up in Part 3: We get into the gritty theory of "Inquiry" — why you have to build things to understand them — and the specific Heuristics you need to memorize to stop building garbage interfaces._
 
 ## Part 3: The Theory of Inquiry & Core Heuristics
 
@@ -135,7 +135,7 @@ To succeed, a product must stop being a distorting mirror and start reflecting t
 
 ### The Theory of Inquiry
 
-The theoretical core of how we navigate this uncertainty comes from the concept of "Inquiry." The traditional "Feynman Algorithm"—write down the problem, think hard, write down the solution—fails spectacularly when applied to Wicked Problems. Instead, we look to John Dewey’s "Theory of Inquiry" and Donald Schön’s concept of the "Reflective Practitioner." Schön distinguishes between "reflection-in-action," which is the act of thinking while doing—tweaking the code as you write it because it just feels wrong—and "reflection-on-action," which is the analysis that happens after the fact.
+The theoretical core of how we navigate this uncertainty comes from the concept of "Inquiry." The traditional "Feynman Algorithm" — write down the problem, think hard, write down the solution — fails spectacularly when applied to Wicked Problems. Instead, we look to John Dewey’s "Theory of Inquiry" and Donald Schön’s concept of the "Reflective Practitioner." Schön distinguishes between "reflection-in-action," which is the act of thinking while doing — tweaking the code as you write it because it just feels wrong — and "reflection-on-action," which is the analysis that happens after the fact.
 
 This leads us to the concept of "doing for the sake of knowing." Consider how you solve a mechanical puzzle like a Rubik’s Cube. You rarely solve it by placing it on a table, staring at it, and calculating the algorithmic path in your head. You solve it by picking it up and twisting it. The physical action generates information. You try a move, observe the result, and that result informs your next move. In Design Thinking, the process of creating a prototype is not just about implementing a solution; it is a tool for understanding the problem itself. Every prototype is a hypothesis, and every failure is a data point.
 
@@ -143,15 +143,15 @@ This chaotic journey is famously visualized as the "Design Squiggle" by Damien N
 
 ### Heuristics for Interactive Systems
 
-With the theory established, we must turn to the hard rules—the "Heuristics"—that govern good interactive systems. These are the operational commandments for creating sanity in software.
+With the theory established, we must turn to the hard rules — the "Heuristics" — that govern good interactive systems. These are the operational commandments for creating sanity in software.
 
 The first and most critical heuristic is **Communication and Feedback**. The system must constantly talk to the user. This happens passively through "Affordance," where elements visually describe how they should be used, but also actively through feedback loops. If a user clicks something, the system must respond immediately. For short actions, a change in cursor or button state suffices; for longer actions, a progress bar is mandatory. The rule is absolute: never leave the user guessing "Did it work?"
 
 This ties directly into the concept of **Affordance**, a term borrowed from industrial design. A physical door handle "affords" pulling, while a flat plate "affords" pushing. If you have to put a sign on a door saying "PUSH," the design has failed. In the digital realm, we simulate this. We use shadows and gradients to make buttons look raised, inviting a push. We use ridges on scrollbars to metaphorically suggest the grip of a bottle cap. If a non-clickable element looks like a button, you are effectively lying to your user.
 
-**Structure and Consistency** form the backbone of a navigable system. We call this Information Architecture. Similar things must look similar, and different things must look different. The user should always be able to answer three questions: Where am I? Where did I come from? How do I get back? This requires internal consistency—if "Save" is a blue button on one page, it cannot be a red link on another—and external consistency, which means adhering to platform standards. Do not reinvent the wheel; if `Ctrl+C` means copy in every other application, making it "Clear All" in yours is an act of hostility.
+**Structure and Consistency** form the backbone of a navigable system. We call this Information Architecture. Similar things must look similar, and different things must look different. The user should always be able to answer three questions: Where am I? Where did I come from? How do I get back? This requires internal consistency — if "Save" is a blue button on one page, it cannot be a red link on another — and external consistency, which means adhering to platform standards. Do not reinvent the wheel; if `Ctrl+C` means copy in every other application, making it "Clear All" in yours is an act of hostility.
 
-We must also respect the limits of **Human Perception**. Humans are excellent at Recognition—seeing an icon and knowing what it is—but terrible at Recall—remembering a specific command name from memory. Good design relies on recognition, minimizing the cognitive load required to use the tool. This extends to readability, ensuring font sizes, contrast ratios, and color choices accommodate human biology.
+We must also respect the limits of **Human Perception**. Humans are excellent at Recognition — seeing an icon and knowing what it is — but terrible at Recall — remembering a specific command name from memory. Good design relies on recognition, minimizing the cognitive load required to use the tool. This extends to readability, ensuring font sizes, contrast ratios, and color choices accommodate human biology.
 
 Efficiency is governed by the **80:20 Rule**. You should identify the 20% of features that users engage with 80% of the time and make those immediate, one-click actions. The remaining 80% of features, which are rarely used, should be tucked away in menus or secondary screens. The goal is to provide accelerators for power users while maintaining clear, uncluttered paths for beginners.
 
@@ -159,11 +159,11 @@ Finally, we must prioritize **Clarity and Control**. Every action needs a define
 
 ### The Product Experience
 
-Beyond the functional mechanics, we must address the "Product Experience," or the feel of the system. This is not just visual aesthetics; it is **Interaction Aesthetics**. Paul Hekkert defines this as the "gratification of senses," but in software, we often refer to it as "Pliability." Pliability describes the user's sense of shaping a malleable material. When you drag a file on a smartphone and the icons shift out of the way fluidly, that is pliability. It feels responsive, tight, and alive. This creates an emotional bond. If a tool makes a user feel smart and capable, they will love it. If it makes them feel stupid by throwing constant errors, they will hate it. The goal is to achieve a sense of joy and excitement—a feeling that the system is not just a tool, but an extension of the user's own intent.
+Beyond the functional mechanics, we must address the "Product Experience," or the feel of the system. This is not just visual aesthetics; it is **Interaction Aesthetics**. Paul Hekkert defines this as the "gratification of senses," but in software, we often refer to it as "Pliability." Pliability describes the user's sense of shaping a malleable material. When you drag a file on a smartphone and the icons shift out of the way fluidly, that is pliability. It feels responsive, tight, and alive. This creates an emotional bond. If a tool makes a user feel smart and capable, they will love it. If it makes them feel stupid by throwing constant errors, they will hate it. The goal is to achieve a sense of joy and excitement — a feeling that the system is not just a tool, but an extension of the user's own intent.
 
 ---
 
-_Coming Up in Part 4: The Practitioner’s Toolkit—Why you need to sketch (not prototype) 2,500 times, the difference between "Opportunity Seeking" and "Decision Making," and why your first idea is probably your worst._
+_Coming Up in Part 4: The Practitioner’s Toolkit — Why you need to sketch (not prototype) 2,500 times, the difference between "Opportunity Seeking" and "Decision Making," and why your first idea is probably your worst._
 
 ## Part 4: The Practitioner’s Toolkit
 
@@ -171,11 +171,11 @@ We have spent a lot of time on the philosophy of the "Wicked Problem" and the hi
 
 The first hurdle you will face is your own brain. In design theory, we talk about the concept of the **Primary Generator**. This is the technical term for that first, lightning-bolt idea you get when you hear a problem description. You know the feeling: a client describes a need, and immediately, a solution pops into your head. It feels like intuition, or experience, or even genius. But in the context of Wicked Problems, this primary generator is dangerous. These early ideas act as blinders, creating a tunnel vision that forces you toward a specific solution before you have actually understood the problem.
 
-To truly embrace an open design process, you have to learn to "kill your darlings." A great example of this comes from a group of students who created the game _And Yet It Moves_. The initial concept relied on a specific mechanic where the player would "fling" the mouse to rotate the world 90 degrees. It was their primary generator, the core hook they were excited about. But during prototyping, it became clear that this mechanic turned the game into a test of dexterity rather than a puzzle platformer. It was only by discarding their original "genius" idea that they were able to uncover the better game underneath—a game that eventually launched on the Nintendo Wii. You must actively seek uncertainty at the beginning of the process. You have to climb the hill of ambiguity rather than rushing for the first comfortable solution.
+To truly embrace an open design process, you have to learn to "kill your darlings." A great example of this comes from a group of students who created the game _And Yet It Moves_. The initial concept relied on a specific mechanic where the player would "fling" the mouse to rotate the world 90 degrees. It was their primary generator, the core hook they were excited about. But during prototyping, it became clear that this mechanic turned the game into a test of dexterity rather than a puzzle platformer. It was only by discarding their original "genius" idea that they were able to uncover the better game underneath — a game that eventually launched on the Nintendo Wii. You must actively seek uncertainty at the beginning of the process. You have to climb the hill of ambiguity rather than rushing for the first comfortable solution.
 
 This approach is exemplified by Graham Whiteley’s work on the "Sheffield Arm." Whiteley started with a whimsical goal: he wanted to build a better mechanical arm for an animatronic drinking robot in his favorite pub. His first thought was to use existing medical prosthetics, but he quickly found them totally unsuitable. Instead of trying to force the existing solution to fit, he embarked on a process of **Research through Design**. He didn't write a specification; he built sketches. He built prototype after prototype, creating physical objects that he could put into the hands of surgeons and osteopaths.
 
-What happened next is key: the experts didn't just look at diagrams; they manipulated the physical prototypes with their hands, using their tacit, embodied knowledge to give feedback like "this joint is too stiff" or "this needs more resistance." By "moving all horses at once"—building, testing, and analyzing simultaneously—Whiteley ended up creating a breakthrough in bionics that went far beyond a pub robot. He didn't solve the problem by defining it first; he defined the problem by trying to solve it.
+What happened next is key: the experts didn't just look at diagrams; they manipulated the physical prototypes with their hands, using their tacit, embodied knowledge to give feedback like "this joint is too stiff" or "this needs more resistance." By "moving all horses at once" — building, testing, and analyzing simultaneously — Whiteley ended up creating a breakthrough in bionics that went far beyond a pub robot. He didn't solve the problem by defining it first; he defined the problem by trying to solve it.
 
 ### The Blur of Analysis and Synthesis
 
@@ -189,7 +189,7 @@ The most potent tool for this simultaneous analysis and synthesis is **Sketching
 
 Crucially, sketching is distinct from prototyping. The difference lies in the intent. You sketch to explore; you prototype to decide. A sketch is cheap, fast, and disposable. It is low-fidelity by design. The "roughness" of a sketch is a feature, not a bug, because it invites interpretation. If you show someone a polished, pixel-perfect mockup, they will critique the font choice. If you show them a rough pencil sketch, they will critique the concept.
 
-Consider the case of the software _ProfCast_. The creators generated over **2,500 sketches** before they settled on the final design. That number seems absurd until you realize that sketching is fast. It is a volume game. You sketch to get the bad ideas out of your system, to explore the impossible, and to find the unexpected connections. If you are precious about your sketches, you are doing it wrong. You should be willing to throw them away instantly. This is where modern "Vibe Coding"—using AI to generate throwaway interactive snippets—can actually be useful. If you treat the code as disposable as a napkin sketch, it becomes a powerful tool for inquiry. But if you start trying to ship that code, you have moved from sketching to bad engineering.
+Consider the case of the software _ProfCast_. The creators generated over **2,500 sketches** before they settled on the final design. That number seems absurd until you realize that sketching is fast. It is a volume game. You sketch to get the bad ideas out of your system, to explore the impossible, and to find the unexpected connections. If you are precious about your sketches, you are doing it wrong. You should be willing to throw them away instantly. This is where modern "Vibe Coding" — using AI to generate throwaway interactive snippets — can actually be useful. If you treat the code as disposable as a napkin sketch, it becomes a powerful tool for inquiry. But if you start trying to ship that code, you have moved from sketching to bad engineering.
 
 Sketching is not limited to paper. One of the most famous sketches in tech history was a block of wood. Jeff Hawkins, the creator of the Palm Pilot, walked around for weeks carrying a piece of wood cut to the size of his proposed device. He would pull it out of his pocket to "check his schedule." He would tap on the wood with a "stylus" (a chopstick). He used this physical roleplay to understand the form factor. He discovered that people interacted with the device differently depending on whether he handed it to them vertically or horizontally. He learned about the ergonomics and the social acceptability of the device before writing a single line of code or soldering a single circuit. This is the essence of a sketch: it costs nothing, but it generates massive insight.
 
@@ -205,7 +205,7 @@ Your job as a designer is to create a system that helps the user build a correct
 
 ---
 
-_Coming Up in Part 5: The traps that ruin everything—Featuritis, Solutionism, and the dark world of Deceptive Patterns._
+_Coming Up in Part 5: The traps that ruin everything — Featuritis, Solutionism, and the dark world of Deceptive Patterns._
 
 ## Part 5: The Traps of Modern Design
 
@@ -241,7 +241,7 @@ Krisztina Szerovay’s "UX Knowledge Base" visually documents these patterns, sh
 
 Finally, we need to address the language we use. Throughout this series, we have used the word "User." But as the old industry joke goes, only two professions refer to their customers as "users": drug dealers and IT professionals. The term is problematic because it implies passivity. A "user" is someone who takes what is given to them. It strips the human of their agency and complexity.
 
-When we view people as "users," we start to treat them like the dog in the famous "IT Crowd" style cartoons—stupid, inept, and needing to be heralded through the process. We create error messages that treat them like children. We assume they read every word of our instructional text (they don't). We assume they care about our database schema (they don't).
+When we view people as "users," we start to treat them like the dog in the famous "IT Crowd" style cartoons — stupid, inept, and needing to be heralded through the process. We create error messages that treat them like children. We assume they read every word of our instructional text (they don't). We assume they care about our database schema (they don't).
 
 Jonathan Nightingale from Mozilla once satirized this attitude by rewriting a browser error message to say: "You have hurt the internet's feelings." It was a joke, but it highlighted how ridiculous our communication often is. We bombard people with technical jargon and meaningless choices because we forget there is a human on the other side of the screen.
 
diff --git a/src/content/posts/policy-thinking.md b/src/content/posts/policy-thinking.md
index 1b85bac..1f334f1 100644
--- a/src/content/posts/policy-thinking.md
+++ b/src/content/posts/policy-thinking.md
@@ -5,14 +5,14 @@ pubDate: 2025-10-25
 
 ## Part 1: The Landscape of Control & Why Code is Law
 
-Here’s the deal: Computer Science is the unruly teenager of the academic and professional world. Unlike medicine, where doctors have operated under strict ethical codes and confidentiality oaths for centuries, the tech industry has spent most of its existence in a "move fast and break things" wild west. We are only just now seeing the emergence of serious regulatory frameworks, such as the GDPR in Europe, attempting to impose order on a chaotic system. This friction between society’s need for stability and the industry’s drive for unbridled innovation is defining the current era of technology. It is a massive problem, and as we saw with the EU’s recent AI Directive, the regulators are often one step behind—publishing rules that were already obsolete because they failed to account for generative AI.
+Here’s the deal: Computer Science is the unruly teenager of the academic and professional world. Unlike medicine, where doctors have operated under strict ethical codes and confidentiality oaths for centuries, the tech industry has spent most of its existence in a "move fast and break things" wild west. We are only just now seeing the emergence of serious regulatory frameworks, such as the GDPR in Europe, attempting to impose order on a chaotic system. This friction between society’s need for stability and the industry’s drive for unbridled innovation is defining the current era of technology. It is a massive problem, and as we saw with the EU’s recent AI Directive, the regulators are often one step behind — publishing rules that were already obsolete because they failed to account for generative AI.
 
 ### The Policy Stack
 
 When we talk about "policies" in IT, we aren't just talking about government laws. We are talking about a multi-layered stack of rules that come in vastly different flavors. You interact with these every day, often without realizing the power dynamics at play.
 
 **1. The Regulatory Hammer: GDPR**
-The General Data Protection Regulation (GDPR) is arguably the most famous piece of IT policy in existence. It regulates the fundamental rights of EU citizens regarding data protection. It gets a lot of hate, mostly because people associate it with annoying cookie banners (which, for the record, were mandatory before GDPR). But looking past the UI annoyance, it ushered in a massive shift in how we handle data. It forced companies to actually care about what they store and why. It is a "hard" policy—ignoring it costs millions.
+The General Data Protection Regulation (GDPR) is arguably the most famous piece of IT policy in existence. It regulates the fundamental rights of EU citizens regarding data protection. It gets a lot of hate, mostly because people associate it with annoying cookie banners (which, for the record, were mandatory before GDPR). But looking past the UI annoyance, it ushered in a massive shift in how we handle data. It forced companies to actually care about what they store and why. It is a "hard" policy — ignoring it costs millions.
 
 **2. The Financial Lever: Technology Funding**
 This is a subtler form of policy. Governments use funding programs to shape the local technology landscape. It’s a way to counter the influence of powerful corporate lobbies by injecting cash into specific areas society deems valuable. However, this is a double-edged sword; sometimes these programs achieve the exact opposite of their intent, distorting the market rather than fixing it.
@@ -27,7 +27,7 @@ This is a unique beast because it is a policy that can be **programmatically enf
 These regulate the flow of free software. If you use OSS in your company, you have obligations. If you contribute to a project, you face quality assurance policies. It’s the bureaucracy of the free web, ensuring that "free" doesn't mean "chaos."
 
 **6. The Hardware Consensus: Standards (e.g., USB-C)**
-Standards are policies defined by massive, cross-company committees. They are great for consumers because they ensure interoperability (your charger works with your laptop). But don't be naive—industries often rush to standardize voluntarily specifically to _prevent_ the government from stepping in with stricter laws. It’s regulation as a defense mechanism.
+Standards are policies defined by massive, cross-company committees. They are great for consumers because they ensure interoperability (your charger works with your laptop). But don't be naive — industries often rush to standardize voluntarily specifically to _prevent_ the government from stepping in with stricter laws. It’s regulation as a defense mechanism.
 
 ### The Discrepancy of Speed
 
@@ -63,7 +63,7 @@ The most aggressive implementation of this is in **Copyright and DRM (Digital Ri
 
 We see the absurdity of this with works that have entered the **Public Domain**. Take the original Mickey Mouse animation, _Steamboat Willie_, or the classic film _Man with a Movie Camera_. These works belong to the public now. Legally, you can do whatever you want with them. However, if you buy a modern disc or file of these works, it will likely still be wrapped in encryption or copy protection.
 
-To exercise your legal right to copy this public domain work, you would have to break the copy protection. But—and here is the trap—breaking copy protection is illegal under a _different_ set of laws (like the DMCA in the US or similar EU directives).
+To exercise your legal right to copy this public domain work, you would have to break the copy protection. But — and here is the trap — breaking copy protection is illegal under a _different_ set of laws (like the DMCA in the US or similar EU directives).
 
 So, the technology effectively overrides the public domain status. The "policy" coded into the disc renders your legal rights null and void. This is dangerous territory. We are moving from a world where laws are social agreements enforced by courts, to a world where usage concepts are enforced by impartial, unyielding code. Code doesn't care about nuance, fair use, or expiration dates. It just executes.
 
@@ -79,7 +79,7 @@ To understand why we even bother with policy thinking in computer science, we ha
 
 The first thesis is widely known as Kranzberg's First Law of Technology. It states quite simply: **Technology is neither good nor bad; nor is it neutral.**
 
-This destroys the comfortable idea that tools are just tools. Engineers love to claim that a system is neutral and that responsibility lies solely with the user—the classic "guns don't kill people" argument. But Kranzberg argues that this is fundamentally false. Every piece of technology forces a specific way of doing things. It inevitably changes the distribution of power. By its very design, a system facilitates certain actions and hinders others; it empowers certain groups of people while disenfranchising others.
+This destroys the comfortable idea that tools are just tools. Engineers love to claim that a system is neutral and that responsibility lies solely with the user — the classic "guns don't kill people" argument. But Kranzberg argues that this is fundamentally false. Every piece of technology forces a specific way of doing things. It inevitably changes the distribution of power. By its very design, a system facilitates certain actions and hinders others; it empowers certain groups of people while disenfranchising others.
 
 When we implement a mathematical concept into a concrete system in the real world, it ceases to be an abstract neutral entity. It becomes an active agent that intervenes in the flow of history. It accelerates some developments and brakes others. Because of this inherent bias in function and access, no technology can ever be truly neutral. Therefore, claiming that "responsibility lies not with the technology, but with the human" is a logical fallacy. The technology itself carries a moral and political weight.
 
@@ -95,11 +95,11 @@ This connects back to the concept of Critical Thinking and Algorithmic Bias. You
 
 The third thesis explains the current friction: The IT industry has a long history of deflecting, ignoring, and bypassing regulation.
 
-This is a defense mechanism. The industry frequently argues that politicians lack the competence to regulate tech—a point that, painfully, is often true. But they also weaponize the neutrality myth (Thesis 1) to argue that regulation is unnecessary. This creates a culture where bypassing rules is seen as a virtue, a necessary step for innovation, rather than a violation of the social contract.
+This is a defense mechanism. The industry frequently argues that politicians lack the competence to regulate tech — a point that, painfully, is often true. But they also weaponize the neutrality myth (Thesis 1) to argue that regulation is unnecessary. This creates a culture where bypassing rules is seen as a virtue, a necessary step for innovation, rather than a violation of the social contract.
 
 ### Defining "Policy Thinking" vs. Technology Policy
 
-So what is this field we are discussing? Wikipedia defines **Technology Policy** as the sum of all political activities regarding the planning, development, deployment, and evaluation of technology. It is a massive field that includes fostering research and development (R&D), managing the diffusion of new tech, and—crucially—handling the fallout and problems caused by that tech.
+So what is this field we are discussing? Wikipedia defines **Technology Policy** as the sum of all political activities regarding the planning, development, deployment, and evaluation of technology. It is a massive field that includes fostering research and development (R&D), managing the diffusion of new tech, and — crucially — handling the fallout and problems caused by that tech.
 
 The state has a wide arsenal of instruments here. There is institutional funding, where the state supports heavy hitters like the Max Planck Society or Fraunhofer Society. There are financial incentives, such as risk capital and innovation programs. There is the provision of infrastructure and support for technology transfer. But it goes deeper into the "soft" power of the state: organizing the public discourse through technology assessment studies, creating educational paths to train new experts, and regulatory politics like antitrust laws.
 
@@ -122,7 +122,7 @@ This struggle is complicated by a paradox known as the Collingridge Dilemma. It
 1.  **The Information Problem:** When a technology is at an early stage, we cannot predict its harmful consequences. We don't know enough to regulate it effectively.
 2.  **The Power Problem:** By the time the technology has spread widely enough that we _can_ see the harmful consequences, it has become so entrenched in society that controlling or changing it is nearly impossible.
 
-This dilemma is often used as a "get out of jail free" card by the industry. They shrug and say, "Well, we couldn't have known, and now it's too late." But this is often an excuse to avoid basic responsibility. Many of the problems we face today—surveillance, bias, polarization—were systematically predictable. We just chose not to look because looking would have slowed down the deployment.
+This dilemma is often used as a "get out of jail free" card by the industry. They shrug and say, "Well, we couldn't have known, and now it's too late." But this is often an excuse to avoid basic responsibility. Many of the problems we face today — surveillance, bias, polarization — were systematically predictable. We just chose not to look because looking would have slowed down the deployment.
 
 ### From Nurturing to Reining In
 
@@ -132,7 +132,7 @@ Today, the conversation is entirely different. We are no longer asking how to nu
 
 This parallels the oil industry and the climate crisis. Both problems arose from a lack of early regulation and a refusal to acknowledge negative externalities. The industry fought regulation every step of the way, dating back to the 19th-century railroad barons who had to be forced by law to consider the public good.
 
-It is now clear that "self-regulation" and "technical innovation" alone will not fix these problems. We need political solutions. And contrary to the Silicon Valley narrative, regulation does not kill innovation—it improves it. As Paul Nemitz, a key advisor to the EU Commission, puts it: there must be a **primacy of democracy over technology and business models**.
+It is now clear that "self-regulation" and "technical innovation" alone will not fix these problems. We need political solutions. And contrary to the Silicon Valley narrative, regulation does not kill innovation — it improves it. As Paul Nemitz, a key advisor to the EU Commission, puts it: there must be a **primacy of democracy over technology and business models**.
 
 The tech scene loves to argue that laws should just adapt to the principles of technology (i.e., code). But the purpose of legislation is not to secure a specific business model. The purpose of legislation is to shape the life of the human being and society as a whole. If a business model relies on destroying the fabric of democracy, the law has a duty to destroy that business model.
 
@@ -146,11 +146,11 @@ We often talk about "privacy" in the abstract, but to understand the true weight
 
 ### The Precision of Influence: A Case Study
 
-Let’s start with a story that sounds like a joke but reveals the terrifying granularity of modern targeting. A while back, a writer decided to pull a prank on his roommate. The roommate was becoming paranoid, so the writer used Facebook’s ad targeting tools to feed him incredibly specific "dark" ads. He didn't cast a wide net; he created a "custom audience" that consisted of exactly one person—his roommate.
+Let’s start with a story that sounds like a joke but reveals the terrifying granularity of modern targeting. A while back, a writer decided to pull a prank on his roommate. The roommate was becoming paranoid, so the writer used Facebook’s ad targeting tools to feed him incredibly specific "dark" ads. He didn't cast a wide net; he created a "custom audience" that consisted of exactly one person — his roommate.
 
 Now, Facebook’s policy technically forbids target audiences of size one. To bypass this, the writer created a target group consisting of "all women" plus "his roommate," and then in a separate setting, specified that the ads should only be shown to _men_. The intersection of those sets was exactly one person. He then bombarded his roommate with ads that referenced specific things they had just talked about or personal insecurities, driving the poor guy to the brink of a nervous breakdown. The writer eventually had to stop because he feared he was going to send his friend to a psychiatric ward.
 
-This anecdote is funny, but the implications are catastrophic. If a random guy can use off-the-shelf tools to manipulate a friend into a mental crisis, what can a state actor do? What can a corporation do? We are talking about the ability to influence elections, shift cultural narratives, or incite violence (like the storming of a parliament) by targeting specific triggers in specific people. This is the realization of "Surveillance Capitalism"—a term coined by Shoshana Zuboff. It’s the business of harvesting human experience as raw material for behavioral data.
+This anecdote is funny, but the implications are catastrophic. If a random guy can use off-the-shelf tools to manipulate a friend into a mental crisis, what can a state actor do? What can a corporation do? We are talking about the ability to influence elections, shift cultural narratives, or incite violence (like the storming of a parliament) by targeting specific triggers in specific people. This is the realization of "Surveillance Capitalism" — a term coined by Shoshana Zuboff. It’s the business of harvesting human experience as raw material for behavioral data.
 
 ### The Great Boycott and the "Pay or Okay" Trap
 
@@ -164,13 +164,13 @@ Legal activists (like those at _noyb_ and _epicenter.works_) are currently suing
 
 To grasp the scale of this industry, look at the "MarTech" (Marketing Technology) landscape. In 2011, there were about 150 companies in this space. By 2020, there were 8,000. By 2025, fueled by the AI boom, that number hit approximately **15,000 companies**. That is a 100x growth (10,000%) in just over a decade.
 
-There are thousands of companies you have never heard of that know more about your habits than your spouse does. Interestingly, the growth rate of this industry actually slowed down after the introduction of GDPR—proof that regulation _does_ have a tangible impact on the market.
+There are thousands of companies you have never heard of that know more about your habits than your spouse does. Interestingly, the growth rate of this industry actually slowed down after the introduction of GDPR — proof that regulation _does_ have a tangible impact on the market.
 
 ### The Race to the Bottom of the Brainstem
 
 The core mechanism of this industry is what experts call the "Race to the Bottom of the Brainstem."
 
-This concept describes how AI backend systems are optimized to keep you on a platform for as long as possible (Engagement). To do this, the algorithms have learned that the most effective way to grab your attention is not to appeal to your higher reasoning or your prefrontal cortex. That part of your brain is slow, lazy, and energy-intensive. Instead, the algorithms target the brainstem—the primal "lizard brain" responsible for survival instincts like fight-or-flight, fear, and outrage.
+This concept describes how AI backend systems are optimized to keep you on a platform for as long as possible (Engagement). To do this, the algorithms have learned that the most effective way to grab your attention is not to appeal to your higher reasoning or your prefrontal cortex. That part of your brain is slow, lazy, and energy-intensive. Instead, the algorithms target the brainstem — the primal "lizard brain" responsible for survival instincts like fight-or-flight, fear, and outrage.
 
 Scott Galloway, a Professor of Marketing at NYU, puts it bluntly: "Social media is nicotine... The thing that gives you cancer is the ad model." The ad model necessitates algorithms that identify your political leaning and then enrage you with content from the "other side" to keep you clicking. This is **"Escalating En-rage-ment."**
 
@@ -192,11 +192,11 @@ The results were devastating. **Falsehoods dominated truth on every metric.** Fa
 
 The study found that this wasn't just because of bots. It’s human nature. Lies are often engineered to be more novel, more shocking, and more emotionally stimulating than the boring, nuanced truth. The algorithms, detecting this high engagement, prioritize the lies and push them to the top of everyone’s feed.
 
-This creates **Quasi-Cults**—small, isolated pockets of society that operate on a completely different version of reality. These "echo chambers" are reinforced by the platform. If you click on one conspiracy video, the "Paperclip Maximizer" realizes you like that flavor of dopamine and feeds you 50 more videos that are increasingly extreme.
+This creates **Quasi-Cults** — small, isolated pockets of society that operate on a completely different version of reality. These "echo chambers" are reinforced by the platform. If you click on one conspiracy video, the "Paperclip Maximizer" realizes you like that flavor of dopamine and feeds you 50 more videos that are increasingly extreme.
 
 ### Conclusion: It's Not a Bug, It's the Product
 
-We used to think these issues—radicalization, misinformation, fragmentation—were unfortunate side effects. Bugs in the code. We now know that the Social Media giants have been aware of these problems for years. They choose not to fix them because fixing them would break the business model. You cannot solve the problem of "En-rage-ment" if your stock price depends on selling ads against that rage.
+We used to think these issues — radicalization, misinformation, fragmentation — were unfortunate side effects. Bugs in the code. We now know that the Social Media giants have been aware of these problems for years. They choose not to fix them because fixing them would break the business model. You cannot solve the problem of "En-rage-ment" if your stock price depends on selling ads against that rage.
 
 This leads us to the inevitable conclusion of the MIT study: We need a new information ecosystem. Since the companies are too profitable to change themselves, this change must be imposed from the outside through **Policy**. We have to intervene in the business model itself.
 
@@ -206,7 +206,7 @@ _Coming Up in Part 4: We explore the fight for "Digital Sovereignty," the death
 
 ## Part 4: Digital Sovereignty & The Death of the Libertarian Web
 
-We have established that the current internet ecosystem is built on surveillance and behavioral modification. But how do we fix it? The immediate answer from the design and legal world brings us to the concept of **Dark Patterns**. These are user interface design choices meticulously crafted to trick you into doing things you didn't intend to do—like buying insurance you don't need, or, more relevantly here, agreeing to tracking you don't want.
+We have established that the current internet ecosystem is built on surveillance and behavioral modification. But how do we fix it? The immediate answer from the design and legal world brings us to the concept of **Dark Patterns**. These are user interface design choices meticulously crafted to trick you into doing things you didn't intend to do — like buying insurance you don't need, or, more relevantly here, agreeing to tracking you don't want.
 
 ### The Design of Deception
 
@@ -226,9 +226,9 @@ This regulatory vacuum in the US forces Europe to lean into **Digital Sovereignt
 
 1.  **State Sovereignty:** The ability of a country to control its own digital infrastructure and enforce its laws (cybersecurity, critical infra).
 2.  **Economic Sovereignty:** The ability of local tech companies to compete and innovate without being crushed or bought by US giants.
-3.  **Individual Sovereignty:** Your personal right to digital self-determination—the ability to act freely online without being manipulated by a black-box system.
+3.  **Individual Sovereignty:** Your personal right to digital self-determination — the ability to act freely online without being manipulated by a black-box system.
 
-The hard truth is that **none** of these three forms of sovereignty are compatible with using the services of the big US hyperscalers (Microsoft, Amazon, Google). Why? Because of the legal frameworks. In the US, the Foreign Intelligence Surveillance Act (FISA) and the CLOUD Act allow US intelligence agencies to force US companies to hand over data, even if that data is stored on servers in Europe. And—this is the kicker—the companies are often forbidden by law from telling you they handed it over.
+The hard truth is that **none** of these three forms of sovereignty are compatible with using the services of the big US hyperscalers (Microsoft, Amazon, Google). Why? Because of the legal frameworks. In the US, the Foreign Intelligence Surveillance Act (FISA) and the CLOUD Act allow US intelligence agencies to force US companies to hand over data, even if that data is stored on servers in Europe. And — this is the kicker — the companies are often forbidden by law from telling you they handed it over.
 
 This is why institutions like the International Criminal Court (ICC) have moved away from Microsoft products, and why the Austrian Armed Forces migrated to LibreOffice. You cannot be sovereign if your digital infrastructure has a legal backdoor to a foreign intelligence agency.
 
@@ -250,25 +250,25 @@ We traded the tyranny of the state (which is at least theoretically democratic a
 
 ### The End of Laissez-Faire
 
-Geert Lovink, a prominent net theorist, argues that the era of "Internet Laissez-Faire" is dead. The "multi-stakeholder" model—where a loose coalition of engineers, NGOs, and nice corporations governed the web—has collapsed. The libertarian bubble burst.
+Geert Lovink, a prominent net theorist, argues that the era of "Internet Laissez-Faire" is dead. The "multi-stakeholder" model — where a loose coalition of engineers, NGOs, and nice corporations governed the web — has collapsed. The libertarian bubble burst.
 
 We are now in a phase where societies have realized that the internet is not an "exceptional" space that exists outside the law. It is the central nervous system of society, and allowing it to be run by ad-tech companies is destroying the host. We are witnessing the **"Enshittification"** of the internet (a term coined by Cory Doctorow). Platforms start by being good to users; then they abuse users to make things better for business customers; finally, they abuse those business customers to claw back all the value for themselves, leaving a dying platform filled with spam, scams, and algorithmic sludge.
 
-The friction we feel right now—the lawsuits, the new EU acts, the privacy wars—is the sound of society trying to reassert control over a system that was left to rot for twenty years.
+The friction we feel right now — the lawsuits, the new EU acts, the privacy wars — is the sound of society trying to reassert control over a system that was left to rot for twenty years.
 
 ---
 
-_Coming Up in Part 5: The Grand Finale. We take everything we have learned—policy, bias, sovereignty—and apply it to the ultimate case study: Self-Driving Cars. We will cover the "Trolley Problem" distraction, the "Irony of Automation," and the security nightmare of driving a computer at 130km/h._
+_Coming Up in Part 5: The Grand Finale. We take everything we have learned — policy, bias, sovereignty — and apply it to the ultimate case study: Self-Driving Cars. We will cover the "Trolley Problem" distraction, the "Irony of Automation," and the security nightmare of driving a computer at 130km/h._
 
 ## Part 5: The Autonomy Trap & The Way Forward
 
 We have spent the last four parts discussing the theory of policy, the history of the web, and the mechanisms of surveillance. Now, we are going to apply all of that to a single, concrete case study that embodies every single one of these tensions: **Self-Driving Cars**.
 
-This is not a discussion about the technology of LIDAR or neural networks. This is a discussion about the societal impact of deploying robots into public spaces. And before we start, let’s clear the deck: We are not going to talk about the Trolley Problem. You know the one—should the car swerve to hit the nun or the baby? That is a philosophical parlor game that distracts us from the actual, systemic problems we are facing right now. It takes up 90% of the oxygen in the room but represents 0.001% of the reality. The real issues are economic, legal, and structural.
+This is not a discussion about the technology of LIDAR or neural networks. This is a discussion about the societal impact of deploying robots into public spaces. And before we start, let’s clear the deck: We are not going to talk about the Trolley Problem. You know the one — should the car swerve to hit the nun or the baby? That is a philosophical parlor game that distracts us from the actual, systemic problems we are facing right now. It takes up 90% of the oxygen in the room but represents 0.001% of the reality. The real issues are economic, legal, and structural.
 
 ### The Labor Displacement Crisis
 
-The first massive policy challenge is labor. Millions of people work as drivers—truck drivers, taxi drivers, delivery personnel. Automation is a direct threat to their livelihood. We are currently in a predictable race: "Who can do it cheaper, the human or the machine?"
+The first massive policy challenge is labor. Millions of people work as drivers — truck drivers, taxi drivers, delivery personnel. Automation is a direct threat to their livelihood. We are currently in a predictable race: "Who can do it cheaper, the human or the machine?"
 
 The industry narrative is that machines will take over the boring parts, leaving humans to do "higher value" work. But the reality looks different. We are seeing a future where trucks drive themselves on the highway, but human drivers are still needed for the complex "last mile" in cities or bad weather. What does that job look like? A driver might only be paid for the 20% of the time they are actually driving, turning a solid middle-class job into precarious gig work.
 
@@ -296,7 +296,7 @@ Ethicist Blay Whitby proposes a policy trade-off: We should treat autonomous veh
 
 ### The Framing Problem & Techno-Solutionism
 
-We also need to zoom out and ask: Are we solving the right problem? This is the trap of **Techno-Solutionism**—the belief that every societal issue has a technical fix.
+We also need to zoom out and ask: Are we solving the right problem? This is the trap of **Techno-Solutionism** — the belief that every societal issue has a technical fix.
 
 We are spending billions to make cars drive themselves, assuming that "better cars" is the goal. But self-driving cars do not solve the problem of space. A self-driving car takes up just as much room in a crowded city as a normal car. It still requires massive asphalt infrastructure, leading to soil sealing. It still produces microplastics from tire wear (a huge environmental issue).
 
@@ -308,7 +308,7 @@ Finally, we have to talk about security. A modern car is a computer on wheels. A
 
 Imagine a ransomware attack on a highway. A message pops up on your dashboard: _"Send 1 Bitcoin to this wallet in the next 10 minutes, or we disable the brakes."_
 
-This is not science fiction. The internal architecture of most cars relies on the **CAN bus** (Controller Area Network). This is an ancient standard from the 80s that connects everything in the car—the engine, the brakes, the radio, the wipers. Crucially, the CAN bus traditionally has no internal security. If a hacker gets into the radio (via Bluetooth or WiFi), they are on the same network as the brakes. They can send a "brake now" command, and the car obeys. We are putting insecure, hackable networks on the highway and hoping for the best.
+This is not science fiction. The internal architecture of most cars relies on the **CAN bus** (Controller Area Network). This is an ancient standard from the 80s that connects everything in the car — the engine, the brakes, the radio, the wipers. Crucially, the CAN bus traditionally has no internal security. If a hacker gets into the radio (via Bluetooth or WiFi), they are on the same network as the brakes. They can send a "brake now" command, and the car obeys. We are putting insecure, hackable networks on the highway and hoping for the best.
 
 ### Conclusion: Returning to the Three Theses
 
@@ -318,7 +318,7 @@ We can look at initiatives like the "Contract for the Web" by Tim Berners-Lee, w
 
 Ultimately, we circle back to the **Three Theses** we started with:
 
-1.  **Technology is not neutral.** A self-driving car, a social media feed, or a privacy policy—these are not neutral tools. They actively shape who has power and who has agency in our world.
+1.  **Technology is not neutral.** A self-driving car, a social media feed, or a privacy policy — these are not neutral tools. They actively shape who has power and who has agency in our world.
 2.  **We have privatized a political arena.** We let tech companies decide the rules of speech, the rules of the road, and the rules of privacy. We treated these as business decisions rather than political ones.
 3.  **The industry will not regulate itself.** History shows that the tech industry will deflect, ignore, and bypass regulation to protect its business model.
 
diff --git a/src/content/posts/responsible-thinking.md b/src/content/posts/responsible-thinking.md
index ae93a4e..956ae9c 100644
--- a/src/content/posts/responsible-thinking.md
+++ b/src/content/posts/responsible-thinking.md
@@ -5,25 +5,25 @@ pubDate: 2025-10-04
 
 ## Part 1: The Blood-Stained Origins of Research Ethics
 
-We need to set the stage before we start writing code or designing systems. This entire domain of "Responsible Thinking" is essentially divided into two massive pillars. First, there is the immediate responsibility we have as researchers when we involve actual human beings in our work—that is the realm of **Science Ethics**. Second, there is the broader responsibility we bear when we unleash digital technologies into the wild, affecting society and the environment at scale—this is often termed **Responsible Research & Innovation (RRI)**. In this first part, we are going to look strictly at the first pillar: how we treat the people we study. And straight up, the history here is dark. The rules we follow today didn't appear out of thin air; they were written in blood after the scientific community witnessed horrific abuses of power.
+We need to set the stage before we start writing code or designing systems. This entire domain of "Responsible Thinking" is essentially divided into two massive pillars. First, there is the immediate responsibility we have as researchers when we involve actual human beings in our work — that is the realm of **Science Ethics**. Second, there is the broader responsibility we bear when we unleash digital technologies into the wild, affecting society and the environment at scale — this is often termed **Responsible Research & Innovation (RRI)**. In this first part, we are going to look strictly at the first pillar: how we treat the people we study. And straight up, the history here is dark. The rules we follow today didn't appear out of thin air; they were written in blood after the scientific community witnessed horrific abuses of power.
 
 ### The Tuskegee Betrayal
 
 To understand why modern ethics boards are so strict, you have to look at the Tuskegee Syphilis Experiment. This wasn't a brief lapse in judgment; it was a systematic, forty-year betrayal of trust orchestrated by the US Public Health Service (USPHS). Starting in 1932, the government recruited 400 African American men from Tuskegee, Alabama, to study the "natural progression" of syphilis. The study was predicated on deception from day one. The researchers lured these men in with offers that, in the context of the Great Depression, were hard to refuse: free medical examinations, meals, and burial insurance.
 
-The cruelty lies in the fact that these men were never treated for the disease they were harboring. Even when Penicillin became the standard, effective cure for syphilis and was widely available, the researchers deliberately withheld it from the participants. They needed the men to remain infected so the study could document the ravages of the disease until death. The "science" was prioritized over human life. By the time the study was finally shut down in 1972—a staggering 40 years later—between 28 and 100 participants had died as a direct result of the untreated syphilis or related complications. This timeline illustrates a complete failure of moral compass, leading to a profound and justified distrust of medical institutions that persists today.
+The cruelty lies in the fact that these men were never treated for the disease they were harboring. Even when Penicillin became the standard, effective cure for syphilis and was widely available, the researchers deliberately withheld it from the participants. They needed the men to remain infected so the study could document the ravages of the disease until death. The "science" was prioritized over human life. By the time the study was finally shut down in 1972 — a staggering 40 years later — between 28 and 100 participants had died as a direct result of the untreated syphilis or related complications. This timeline illustrates a complete failure of moral compass, leading to a profound and justified distrust of medical institutions that persists today.
 
 ### The Nazi Atrocities and the Nuremberg Code
 
 While Tuskegee was happening in the US, an even more industrial scale of horror was taking place in Europe. During the Nazi regime, concentration camps became sites for gruesome "medical" experiments where human beings were treated as disposable biological material. In Dachau, for instance, doctors murdered between 280 and 300 prisoners in freezing experiments designed solely to test new clothing for the Luftwaffe. They wanted to know how long a pilot could survive in freezing water, so they forced prisoners into tanks of ice water until they died, monitoring their vitals the entire time.
 
-The aftermath of these horrors brought the world to a standstill. On August 20, 1947, during the Nuremberg Trials, Nazi physicians were convicted for these crimes against humanity—crimes that also included the forced sterilization of 3.5 million Germans. Out of this trial emerged the **Nuremberg Code**, a set of ten ethical principles that remains the absolute bedrock of human research ethics today. The Code established that scientific advancement, no matter how potentially valuable, can never justify the violation of basic human rights. It forces us to ask a difficult retrospective question: If we possess data obtained through torture and murder (like the hypothermia data from Dachau), is it ethical to use that knowledge to save lives today, or does using the data validate the atrocity?
+The aftermath of these horrors brought the world to a standstill. On August 20, 1947, during the Nuremberg Trials, Nazi physicians were convicted for these crimes against humanity — crimes that also included the forced sterilization of 3.5 million Germans. Out of this trial emerged the **Nuremberg Code**, a set of ten ethical principles that remains the absolute bedrock of human research ethics today. The Code established that scientific advancement, no matter how potentially valuable, can never justify the violation of basic human rights. It forces us to ask a difficult retrospective question: If we possess data obtained through torture and murder (like the hypothermia data from Dachau), is it ethical to use that knowledge to save lives today, or does using the data validate the atrocity?
 
 ### The Milgram Experiment: Anatomy of Obedience
 
 In the wake of the Nuremberg trials, the world was left asking _why_. How could so many ordinary citizens and doctors participate in such mass extermination? In 1962, Stanley Milgram attempted to answer this by testing the limits of human obedience to authority. The setup was ingenious and terrifying. Participants were told they were part of a learning study. They were assigned the role of "Teacher," while another person (actually an actor) was the "Learner." The Teacher was instructed to ask questions, and for every wrong answer, they had to administer an electric shock to the Learner.
 
-The shock generator was clearly marked, escalating from slight shocks up to a terrifying 450 Volts. As the experiment progressed and the Learner began to scream, plead for their life, and eventually fall silent, the Teacher would often hesitate. However, a researcher in a white lab coat would simply stand behind them and calmly command, "The experiment requires that you continue." The results were shocking to the American public. Out of 40 subjects, not a single person stopped before reaching 300 Volts. Even more disturbing, 26 of the subjects—well over half—continued all the way to the maximum 450 Volts, a level that would likely be lethal in reality.
+The shock generator was clearly marked, escalating from slight shocks up to a terrifying 450 Volts. As the experiment progressed and the Learner began to scream, plead for their life, and eventually fall silent, the Teacher would often hesitate. However, a researcher in a white lab coat would simply stand behind them and calmly command, "The experiment requires that you continue." The results were shocking to the American public. Out of 40 subjects, not a single person stopped before reaching 300 Volts. Even more disturbing, 26 of the subjects — well over half — continued all the way to the maximum 450 Volts, a level that would likely be lethal in reality.
 
 The Milgram experiment proved that average people could be coerced into torturing others simply by the presence of a perceived authority figure. However, it also sparked a massive debate on the ethics of the experiment itself. Was it ethical to deceive the participants so profoundly? Was it right to put them in a position where they believed they were killing someone? Years later, interviews revealed that many participants were deeply traumatized by the realization of what they were capable of; there are even reports of suicides linked to the guilt associated with the experiment.
 
@@ -31,13 +31,13 @@ The Milgram experiment proved that average people could be coerced into torturin
 
 Fast forward to 2006, and researchers attempted to replicate Milgram's work using Virtual Reality. The theory was that by using a virtual avatar as the "Learner" rather than a human actor, they could bypass the ethical issues of the original study. The results were fascinating: the behavioral dynamics in the virtual environment mirrored the original 1962 findings. People still obeyed the authority figure and "shocked" the virtual avatar.
 
-However, this created a logical paradox regarding the ethics of the simulation. The researchers argued that the study was ethical because the participants were exposed to "no risk"—after all, it was just a simulation. But this argument inadvertently undermines their own scientific conclusions. If the participants experienced _no_ real stress or conflict because they knew it was fake, then the results are scientifically invalid. If the results _are_ valid—meaning the participants reacted as if the situation were real—then they must have experienced real psychological stress, bringing us right back to the original ethical violation. You cannot have it both ways; either the stress is real and the ethics are questionable, or the stress is fake and the science is useless.
+However, this created a logical paradox regarding the ethics of the simulation. The researchers argued that the study was ethical because the participants were exposed to "no risk" — after all, it was just a simulation. But this argument inadvertently undermines their own scientific conclusions. If the participants experienced _no_ real stress or conflict because they knew it was fake, then the results are scientifically invalid. If the results _are_ valid — meaning the participants reacted as if the situation were real — then they must have experienced real psychological stress, bringing us right back to the original ethical violation. You cannot have it both ways; either the stress is real and the ethics are questionable, or the stress is fake and the science is useless.
 
 ### The Central Calculation: Risk vs. Knowledge
 
 Ultimately, all science ethics boils down to a single, critical trade-off: **The balance between Scientific Knowledge Gain and Potential Risk to the Participant.**
 
-In an ideal scenario, the knowledge we gain is massive, and the risk to the participant is non-existent. However, we have to navigate the grey areas. There are hard lines we cannot cross. If there is even a minuscule "residual risk" of death—if there is the slightest chance a participant could die for your study—the potential knowledge gain is irrelevant. It is ethically unacceptable, period.
+In an ideal scenario, the knowledge we gain is massive, and the risk to the participant is non-existent. However, we have to navigate the grey areas. There are hard lines we cannot cross. If there is even a minuscule "residual risk" of death — if there is the slightest chance a participant could die for your study — the potential knowledge gain is irrelevant. It is ethically unacceptable, period.
 
 Conversely, this principle works in the other direction as well. Even if the risk is very low (e.g., just boredom), the study can still be deemed unethical if there is **zero expected knowledge gain**. Wasting a human being's time for a study that yields no new information is, in itself, an ethical violation. We are required to justify that the imposition we place on a participant is outweighed by the value the research brings to the world.
 
@@ -47,13 +47,13 @@ _In the next part, we will break down the specific rules that keep us on the rig
 
 ## Part 2: The Rules of Engagement – Consent, Deception, and Privacy
 
-Now that we have looked at the historical horrors that necessitate strict oversight, we need to break down the actual operational framework we use today. This isn't just about filling out forms to make a university legal department happy; it is about the fundamental agreement between the researcher and the participant. The central calculation we discussed in Part 1—weighing knowledge against risk—is the foundation, but the pillars that hold it up are specific, actionable principles. If you are running a study, you are responsible for ensuring these are not just met on paper, but in spirit.
+Now that we have looked at the historical horrors that necessitate strict oversight, we need to break down the actual operational framework we use today. This isn't just about filling out forms to make a university legal department happy; it is about the fundamental agreement between the researcher and the participant. The central calculation we discussed in Part 1 — weighing knowledge against risk — is the foundation, but the pillars that hold it up are specific, actionable principles. If you are running a study, you are responsible for ensuring these are not just met on paper, but in spirit.
 
 ### The Illusion of Voluntariness
 
 The first and most non-negotiable principle is **Voluntariness**. This sounds simple: the participant must say "yes" without a gun to their head. But in practice, coercion is rarely that obvious. Voluntariness means that a participant cannot be persuaded, pressured, or manipulated into joining. More importantly, it includes the absolute right to withdraw from the study at any time, without providing a reason, and without facing negative consequences. If a participant gets halfway through your survey or experiment and says "I'm done," the data collection stops immediately, and you thank them for their time.
 
-A classic "grey zone" you will likely encounter in academia involves the recruitment of students. It is very common for professors to use their own students as guinea pigs for their research. This is an ethical minefield. The power dynamic here is inherently unbalanced. If participation is tied to the grading of a course—for example, if a student gets "extra credit" for participating that cannot be earned any other way—then voluntariness is dead. The student is effectively being coerced by their GPA. To navigate this, institutions like the University of Waterloo have developed strict guidelines: if research credits are offered, there must be an alternative, non-research way to earn those same credits with equal effort. If a student feels they _have_ to participate to pass, you have failed the ethics check.
+A classic "grey zone" you will likely encounter in academia involves the recruitment of students. It is very common for professors to use their own students as guinea pigs for their research. This is an ethical minefield. The power dynamic here is inherently unbalanced. If participation is tied to the grading of a course — for example, if a student gets "extra credit" for participating that cannot be earned any other way — then voluntariness is dead. The student is effectively being coerced by their GPA. To navigate this, institutions like the University of Waterloo have developed strict guidelines: if research credits are offered, there must be an alternative, non-research way to earn those same credits with equal effort. If a student feels they _have_ to participate to pass, you have failed the ethics check.
 
 ### Informed Consent and The Art of Deception
 
@@ -88,15 +88,15 @@ Finally, we have to talk about **Compensation**. It is good practice to thank pa
 ### In-Action Ethics
 
 We wrap up this section with a concept that bridges the gap between theory and reality: **In-Action Ethics**.
-We have legal frameworks (like the GDPR) that tell us what is _allowed_. We have anticipatory ethics (Ethical Codes) that describe what we _should_ do. But the real world is messy. Often, you will face situations in the lab or the field that the rulebook didn't predict. This is where In-Action Ethics comes into play. It requires critical, reflexive action in the moment. It demands that you develop a personal ethos—a "sense" for what is right—so that when the unexpected happens, you can make a moral decision instantly, rather than just looking for a clause in a contract.
+We have legal frameworks (like the GDPR) that tell us what is _allowed_. We have anticipatory ethics (Ethical Codes) that describe what we _should_ do. But the real world is messy. Often, you will face situations in the lab or the field that the rulebook didn't predict. This is where In-Action Ethics comes into play. It requires critical, reflexive action in the moment. It demands that you develop a personal ethos — a "sense" for what is right — so that when the unexpected happens, you can make a moral decision instantly, rather than just looking for a clause in a contract.
 
 ---
 
-_In the next part, we leave the lab and step into the wider world, examining the "Oppenheimer" moment of technology, where we face the responsibility of building systems that can reshape—or destroy—society._
+_In the next part, we leave the lab and step into the wider world, examining the "Oppenheimer" moment of technology, where we face the responsibility of building systems that can reshape — or destroy — society._
 
 ## Part 3: The "Oppenheimer" Moment – Bias, Power, and the Responsibility Gap
 
-In Part 2, we discussed the ethics of the laboratory—how we treat the few dozen people we invite into our studies. Now, we shift gears to **Responsible Research & Innovation (RRI)**. This is the "macro" view. It’s no longer about the participant signing a consent form; it is about the millions of people who will live in the world reshaped by the code we ship. We are moving from the responsibility of the _researcher_ to the responsibility of the _creator_.
+In Part 2, we discussed the ethics of the laboratory — how we treat the few dozen people we invite into our studies. Now, we shift gears to **Responsible Research & Innovation (RRI)**. This is the "macro" view. It’s no longer about the participant signing a consent form; it is about the millions of people who will live in the world reshaped by the code we ship. We are moving from the responsibility of the _researcher_ to the responsibility of the _creator_.
 
 ### The Oppenheimer Dilemma
 
@@ -110,13 +110,13 @@ A common defense in engineering is that "technology is neutral." A bridge is jus
 
 To understand this, we look at Robert Moses, the "Master Builder" of New York City in the mid-20th century. Moses designed the parkways that connected NYC to the beautiful public beaches of Long Island. But he designed the overpasses on the Southern State Parkway with a specific, hidden constraint: they were built unusually low.
 
-To the casual observer, it was just a low bridge. But functionally, the clearance was too low for public buses to pass underneath. At that time, wealthy (mostly white) people owned cars; poor (mostly black) people relied on buses. By setting the clearance of a concrete arch, Moses effectively engineered social segregation. He filtered the population of the beach without ever putting up a "Whites Only" sign. His prejudices were baked into the physical infrastructure of the city. This proves that artifacts—whether concrete or code—enforce politics.
+To the casual observer, it was just a low bridge. But functionally, the clearance was too low for public buses to pass underneath. At that time, wealthy (mostly white) people owned cars; poor (mostly black) people relied on buses. By setting the clearance of a concrete arch, Moses effectively engineered social segregation. He filtered the population of the beach without ever putting up a "Whites Only" sign. His prejudices were baked into the physical infrastructure of the city. This proves that artifacts — whether concrete or code — enforce politics.
 
 ### Algorithmic Segregation: The Self-Driving Car
 
 Today, we are building the digital equivalent of Robert Moses’ bridges. A glaring example is the object detection algorithms used in autonomous vehicles. These systems are trained on massive datasets to identify pedestrians so the car knows to brake. However, studies have revealed a terrifying predictive inequity.
 
-The algorithms were significantly better at identifying white men than they were at identifying dark-skinned women. Because the training data was skewed toward white faces, the "vision" of the car was racially biased. In a real-world scenario, this means the probability of being recognized—and therefore _not run over_—is dependent on your skin color and gender. This isn't a "glitch"; it is life-or-death discrimination encoded into a safety feature. The technology is not neutral; it is actively replicating the biases of its creators.
+The algorithms were significantly better at identifying white men than they were at identifying dark-skinned women. Because the training data was skewed toward white faces, the "vision" of the car was racially biased. In a real-world scenario, this means the probability of being recognized — and therefore _not run over_ — is dependent on your skin color and gender. This isn't a "glitch"; it is life-or-death discrimination encoded into a safety feature. The technology is not neutral; it is actively replicating the biases of its creators.
 
 ### The Proteus Effect
 
@@ -129,7 +129,7 @@ We even see this carrying over into the real world with children and Voice Assis
 Given these stakes, the field of RRI has zero tolerance for the standard engineering excuses. We need to dismantle three of the most common ones:
 
 **1. "Guns don't kill people, people kill people."**
-This is the argument that the tool has no intentionality. It is flawed. Objects carry "affordances"—they make certain actions easy and others hard. You _can_ kill a person with a hammer, and you _can_ hammer a nail with a gun (poorly). But a gun is _designed_ to kill. Its intentionality is destruction. When we build systems, we are embedding intent. If you build a surveillance system, you cannot feign shock when it is used to spy on people.
+This is the argument that the tool has no intentionality. It is flawed. Objects carry "affordances" — they make certain actions easy and others hard. You _can_ kill a person with a hammer, and you _can_ hammer a nail with a gun (poorly). But a gun is _designed_ to kill. Its intentionality is destruction. When we build systems, we are embedding intent. If you build a surveillance system, you cannot feign shock when it is used to spy on people.
 
 **2. "I was just following orders / I just wrote the code."**
 This is the "cog in the machine" defense. "I was young, I needed the money, my boss told me to do it." As we learned from the Milgram experiment, humans are hardwired to obey authority. But "Civil Courage" is the professional obligation to resist. If you are coding a feature that is unethical, you have a responsibility to raise your hand. You are the last line of defense.
@@ -144,13 +144,13 @@ _In the next part, we will explore the "Algorithmic Panopticon," diving into the
 
 ## Part 4: The Algorithmic Panopticon – Surveillance, Morality, and the Climate Cost
 
-In the previous section, we discussed the responsibility gap—the dangerous idea that we can offload moral agency to a machine. Now, we are going to look at exactly what happens when those machines start making decisions at scale. We are moving into the territory of automated morality, the industrialization of surveillance, and the hidden ecological price tag of our digital obsessions. This isn't science fiction; these are the economic and ethical realities of the systems currently running the world.
+In the previous section, we discussed the responsibility gap — the dangerous idea that we can offload moral agency to a machine. Now, we are going to look at exactly what happens when those machines start making decisions at scale. We are moving into the territory of automated morality, the industrialization of surveillance, and the hidden ecological price tag of our digital obsessions. This isn't science fiction; these are the economic and ethical realities of the systems currently running the world.
 
 ### The Trolley Problem: From Philosophy Class to Production Code
 
 For decades, the "Trolley Problem" was a dusty thought experiment reserved for moral philosophy seminars. You know the drill: a trolley is hurtling down a track toward five people. You are standing next to a lever. If you pull it, the trolley switches tracks and kills only one person. Do you pull the lever? It’s a classic utilitarian dilemma. But with the advent of autonomous driving, this is no longer a hypothetical. It is an engineering specification.
 
-Engineers programming self-driving cars are effectively hard-coding answers to the Trolley Problem. A vehicle _will_ eventually face a situation where an accident is unavoidable—where it must choose between swerving into a pedestrian or crashing into a wall and killing its passenger. The car needs a decision tree for death. This raises an impossible question: How does an algorithm value human life? Does it prioritize the passenger because they bought the car? Does it prioritize the pedestrian? What if the pedestrian is a child vs. an elderly person?
+Engineers programming self-driving cars are effectively hard-coding answers to the Trolley Problem. A vehicle _will_ eventually face a situation where an accident is unavoidable — where it must choose between swerving into a pedestrian or crashing into a wall and killing its passenger. The car needs a decision tree for death. This raises an impossible question: How does an algorithm value human life? Does it prioritize the passenger because they bought the car? Does it prioritize the pedestrian? What if the pedestrian is a child vs. an elderly person?
 
 To tackle this, MIT launched the **Moral Machine** project. They crowdsourced millions of decisions from people around the world to see if there was a universal consensus on how machines should kill. The results were not comforting. They found that "morality" is geographically and culturally relative. Some cultures prioritize saving the young; others prioritize the elderly. Some prioritize following the law (crossing at a green light) over maximizing the number of lives saved. There is no single "correct" algorithm for morality, yet we are deploying cars that must act as if there is.
 
@@ -158,15 +158,15 @@ To tackle this, MIT launched the **Moral Machine** project. They crowdsourced mi
 
 If the Trolley Problem deals with immediate physical harm, **Predictive Policing** deals with systemic societal harm. Law enforcement agencies increasingly use algorithms to allocate resources, sending officers to "high crime" areas based on historical data. This sounds efficient, but it creates a dangerous feedback loop known as a **Self-Fulfilling Prophecy**.
 
-If you send more police to a specific neighborhood based on past arrest data, those police will inevitably find more crime—even minor infractions—simply because they are there to see it. This generates new data points that reinforce the algorithm's bias, telling it to send _even more_ police next time. The system isn't predicting crime; it is predicting (and amplifying) policing.
+If you send more police to a specific neighborhood based on past arrest data, those police will inevitably find more crime — even minor infractions — simply because they are there to see it. This generates new data points that reinforce the algorithm's bias, telling it to send _even more_ police next time. The system isn't predicting crime; it is predicting (and amplifying) policing.
 
 Data scientist Cathy O'Neil explores this in her seminal book, _Weapons of Math Destruction_. She argues that the problem isn't just "biased data" (though that exists); the problem is the _goal_ of the modeling itself. We optimize for efficiency, arrests, or convictions, but we rarely optimize for fairness. When you treat human behavior as an optimization problem without accounting for the social context, you end up automating oppression.
 
 ### Surveillance Capitalism: The Business Model of Our Time
 
-The data feeding these systems has to come from somewhere, and that brings us to the economic engine of the modern internet: **Surveillance Capitalism**. Coined by Shoshana Zuboff, this term describes a market logic where human experience is claimed as free raw material for translation into behavioral data. This isn't just about showing you better ads. It is about predicting and modifying your behavior for profit. Zuboff argues that this accumulation of behavioral data fundamentally undermines democracy by creating an asymmetry of knowledge—they know everything about us; we know nothing about them.
+The data feeding these systems has to come from somewhere, and that brings us to the economic engine of the modern internet: **Surveillance Capitalism**. Coined by Shoshana Zuboff, this term describes a market logic where human experience is claimed as free raw material for translation into behavioral data. This isn't just about showing you better ads. It is about predicting and modifying your behavior for profit. Zuboff argues that this accumulation of behavioral data fundamentally undermines democracy by creating an asymmetry of knowledge — they know everything about us; we know nothing about them.
 
-We see this creeping into the workplace. Microsoft, for example, faced severe backlash for rolling out a "Productivity Score" in Office 365. This feature allowed employers to monitor granular employee activity—how many emails they sent, how often they collaborated, effectively turning the office into a digital panopticon. It creates a culture of fear where workers are constantly performing for the algorithm.
+We see this creeping into the workplace. Microsoft, for example, faced severe backlash for rolling out a "Productivity Score" in Office 365. This feature allowed employers to monitor granular employee activity — how many emails they sent, how often they collaborated, effectively turning the office into a digital panopticon. It creates a culture of fear where workers are constantly performing for the algorithm.
 
 ### The Shadow Market: Data Brokers
 
@@ -206,7 +206,7 @@ Instead of embracing the feedback, Google pushed her out. Her firing (or "resign
 
 If we can't change the companies, can we hack their products? Designers have begun creating "parasitic" technologies to reclaim privacy. A brilliant example is **Project Alias**, created by Bjørn Karmann and Tore Knudsen.
 
-Alias is a "smart fungus" that you physically place on top of a Google Home or Amazon Echo. It constantly feeds white noise into the device's microphone, deafening it so it cannot listen to your private conversations. When you want to issue a command, you speak a custom wake word (of your choosing) to Alias. Alias then stops the white noise and plays a recording of "OK Google" directly into the device's ear. It acts as a middle-man, allowing you to use the tech without being constantly monitored, and even allows you to rename your assistant. This is "Adversarial Design"—using technology to disrupt technology.
+Alias is a "smart fungus" that you physically place on top of a Google Home or Amazon Echo. It constantly feeds white noise into the device's microphone, deafening it so it cannot listen to your private conversations. When you want to issue a command, you speak a custom wake word (of your choosing) to Alias. Alias then stops the white noise and plays a recording of "OK Google" directly into the device's ear. It acts as a middle-man, allowing you to use the tech without being constantly monitored, and even allows you to rename your assistant. This is "Adversarial Design" — using technology to disrupt technology.
 
 ### The Role of Critical Research
 
@@ -231,7 +231,7 @@ We end this series with a return to the fundamentals. Historian Melvin Kranzberg
 
 This is the summary of everything we have discussed. Technology is not "good" just because it is new. It is not "bad" just because it disrupts things. But it is _never_ neutral. Every line of code, every dataset, and every design choice carries the values, biases, and politics of its creator.
 
-We need new spaces—an "Agora"—to debate these values, because Twitter and Facebook are not designed for nuance. We need to write our own **Manifestos** (like the _Vienna Manifesto on Digital Humanism_ or the _IoT Design Manifesto_) to clearly state what we stand for before we get swallowed by the industry.
+We need new spaces — an "Agora" — to debate these values, because Twitter and Facebook are not designed for nuance. We need to write our own **Manifestos** (like the _Vienna Manifesto on Digital Humanism_ or the _IoT Design Manifesto_) to clearly state what we stand for before we get swallowed by the industry.
 
 The "Responsible Thinking" mindset is simply this: Acknowledge that you are building the world, and accept the weight of that fact. No more excuses.
 
diff --git a/src/content/posts/scientific-thinking.md b/src/content/posts/scientific-thinking.md
index 2263631..bb5b679 100644
--- a/src/content/posts/scientific-thinking.md
+++ b/src/content/posts/scientific-thinking.md
@@ -13,7 +13,7 @@ But let’s put the simulation theory on the back burner for a moment. Even if w
 
 ### The Conjecture: Our Hardware is Compromised
 
-To test our ability to observe reality, we are going to run three experiments. A good experiment starts with a conjecture—a guess about what will happen. Our conjecture for this entire section is this: **Our perception and our thinking are not capable of conveying reliable information about the world.**
+To test our ability to observe reality, we are going to run three experiments. A good experiment starts with a conjecture — a guess about what will happen. Our conjecture for this entire section is this: **Our perception and our thinking are not capable of conveying reliable information about the world.**
 
 For the purposes of this discussion, we aren't drawing a sharp line between "perception" (the sensory input) and "thinking" (the processing). Whether the error happens in the eye or the cortex doesn't matter; we are interested in the reliability of the system as a whole. This aligns with the "Critical Thinking" models where we treat the human cognitive stack as a single, often flawed, unit.
 
@@ -21,11 +21,11 @@ For the purposes of this discussion, we aren't drawing a sharp line between "per
 
 Let's look at the human eye. It is, frankly, a bit of a design disaster. In humans, the nerve fibers run _in front_ of the retina. For those nerves to exit the eye and travel to the brain, they have to punch a hole through the retina. Where that hole exists, there are no photoreceptors. No rods, no cones, nothing. This is the **blind spot**. It is a structural failure in our vision. Interestingly, this wasn't inevitable; cephalopods (like octopuses) have nerve fibers running behind the retina, meaning they have no blind spot and get better light throughput. We got the short end of the evolutionary stick here.
 
-You can verify this glitch right now. Imagine a black dot and a black "X" on a piece of paper, separated by about 10 centimeters. If you close your left eye and stare directly at the dot with your right eye, the "X" is in your peripheral vision. If you move your head back and forth—usually finding the sweet spot around 20 centimeters away—the "X" will suddenly vanish. It is gone. The image of the "X" is hitting exactly where your optic nerve punches through the retina.
+You can verify this glitch right now. Imagine a black dot and a black "X" on a piece of paper, separated by about 10 centimeters. If you close your left eye and stare directly at the dot with your right eye, the "X" is in your peripheral vision. If you move your head back and forth — usually finding the sweet spot around 20 centimeters away — the "X" will suddenly vanish. It is gone. The image of the "X" is hitting exactly where your optic nerve punches through the retina.
 
 But here is where it gets terrifying. Keep staring at the dot. Don't look away. Try to perceive what is in the empty space where the "X" used to be. You do not see a black void. You do not see a hole. If the background is white, you see white. If you run this experiment on a page full of text, replacing the "X" with a word, something even stranger happens. When the word hits your blind spot, you don't just see a gap. Your brain fills it in with "text." It is blurry, unreadable, and logically invalid text, but your brain generates the texture of writing to patch the hole.
 
-This is a biological version of the "Content-Aware Fill" or "Inpainting" found in modern image editing software. Your brain knows there is no data there, but it refuses to show you the lack of data. It constructs a lie—a plausible texture—and presents it to you as reality. You are seeing something that you know, with 100% certainty, does not exist.
+This is a biological version of the "Content-Aware Fill" or "Inpainting" found in modern image editing software. Your brain knows there is no data there, but it refuses to show you the lack of data. It constructs a lie — a plausible texture — and presents it to you as reality. You are seeing something that you know, with 100% certainty, does not exist.
 
 ### Experiment 2: The Checker Shadow Illusion
 
@@ -51,15 +51,15 @@ Let’s return to our conjecture: "Our perception and thinking are not capable o
 
 But the most damning realization is that our **rational thinking** cannot override these errors. Even when you know the "X" is there, you can’t see it. Even when you know the squares are the same grey, they look different. Even when you know the hand is rubber, you feel it.
 
-Why are we built this way? Because our thinking is the result of millions of years of evolution, and evolution does not care about "Truth." Evolution cares about "Survival." For the vast majority of our history, knowing the exact hex-code value of a grey pixel didn't matter. Recognizing a pattern quickly—identifying a tiger in the shadows—mattered.
+Why are we built this way? Because our thinking is the result of millions of years of evolution, and evolution does not care about "Truth." Evolution cares about "Survival." For the vast majority of our history, knowing the exact hex-code value of a grey pixel didn't matter. Recognizing a pattern quickly — identifying a tiger in the shadows — mattered.
 
 We are designed to project **Meaning** (Sinn) onto the world. We are storytelling engines, constantly connecting dots to create a coherent narrative. We discussed this in Critical Thinking under the concept of the **"Cognitive Miser."** As Richerson & Boyd noted in 2005: "In effect, all animals are under stringent selection pressure to be as stupid as they can get away with." Processing power is expensive (calories), so the brain takes shortcuts. It biases towards meaning and speed, not accuracy.
 
 ### The Truth-Meaning Gap
 
-This creates a "Meaning-Truth Scissors"—a divergence between what feels true (Meaning) and what is factually true (Truth). The brain’s strategy of projecting sense onto the world is so dominant that it interferes with our ability to observe the world as it actually is.
+This creates a "Meaning-Truth Scissors" — a divergence between what feels true (Meaning) and what is factually true (Truth). The brain’s strategy of projecting sense onto the world is so dominant that it interferes with our ability to observe the world as it actually is.
 
-This leads us to the **Big Idea**—the "OG" concept of scientific thinking:
+This leads us to the **Big Idea** — the "OG" concept of scientific thinking:
 
 If we want to learn anything about the real world, we must **radically distrust our senses.** We cannot just be "careful." We cannot just "double-check." We have to operate on the assumption that our perception is actively lying to us. Nothing our senses tell us can be accepted as reliable data until it has been stripped of human interpretation.
 
@@ -77,23 +77,23 @@ To understand where our modern scientific operating system comes from, we have t
 
 ### The Four Idols of the Mind (Sir Francis Bacon)
 
-In 1620, Francis Bacon published _Novum Organum_ (The New Instrument), essentially a user manual for bypassing human stupidity. Bacon identified four specific "Idols"—systematic errors or illusions—that prevent us from seeing the truth. These aren't physical statues; they are categories of cognitive failure.
+In 1620, Francis Bacon published _Novum Organum_ (The New Instrument), essentially a user manual for bypassing human stupidity. Bacon identified four specific "Idols" — systematic errors or illusions — that prevent us from seeing the truth. These aren't physical statues; they are categories of cognitive failure.
 
 First, he identified the **Idola Tribus (Idols of the Tribe)**. This refers to the errors inherent to human nature itself. This is exactly what we covered in Part 1: the biological limitations of our senses, our tendency to find patterns where none exist, and our evolutionary baggage. These are the bugs hardcoded into the firmware of the human species.
 
-Second are the **Idola Specus (Idols of the Cave)**. These are the errors specific to the individual. We all grow up in a "cave"—our specific culture, upbringing, education, and reading habits. This personal context filters the light of reality, meaning no two people see the world exactly the same way because they are looking out from different caves.
+Second are the **Idola Specus (Idols of the Cave)**. These are the errors specific to the individual. We all grow up in a "cave" — our specific culture, upbringing, education, and reading habits. This personal context filters the light of reality, meaning no two people see the world exactly the same way because they are looking out from different caves.
 
 Third, and perhaps most insidious, are the **Idola Fori (Idols of the Market)**. This refers to the "Marketplace of Ideas," or language itself. We use words to describe the world, but language is imprecise, loaded, and often defined by the masses, not the experts. We get trapped by definitions and semantics, arguing over words rather than the reality those words are supposed to represent. The framework of our language limits the framework of our thinking.
 
-Finally, the **Idola Theatri (Idols of the Theater)**. These are the dogmas and received systems of philosophy. Bacon called them this because he viewed previous philosophical systems (like Aristotelian logic) as stage plays—artificial worlds created for entertainment or comfort that have no bearing on reality. It is the tendency to accept established academic or scientific authority without question, creating a resistance to fundamentally new ideas.
+Finally, the **Idola Theatri (Idols of the Theater)**. These are the dogmas and received systems of philosophy. Bacon called them this because he viewed previous philosophical systems (like Aristotelian logic) as stage plays — artificial worlds created for entertainment or comfort that have no bearing on reality. It is the tendency to accept established academic or scientific authority without question, creating a resistance to fundamentally new ideas.
 
-It is worth noting that while Bacon’s ideas were revolutionary, the man himself was … complicated. By all historical accounts, he was a fairly nasty piece of work. As Lord Chancellor, he justified corruption, was bribable himself, operated as a ruthless opportunist, and was generally disliked. But even a corrupt opportunist can spot a system failure. Bacon proposed a new method to escape these Idols: rather than testing assumptions until they are confirmed (confirmation bias), we should draw well-founded conclusions from experimental data. He explicitly argued for focusing on **negative instances**—evidence that disproves a theory—because that is where the real information hides. He rejected the Church’s stance that "all knowledge is already in the Bible" and demanded work that was **systematic** (repeatable), **empirical** (observation-based), and **inductive**.
+It is worth noting that while Bacon’s ideas were revolutionary, the man himself was … complicated. By all historical accounts, he was a fairly nasty piece of work. As Lord Chancellor, he justified corruption, was bribable himself, operated as a ruthless opportunist, and was generally disliked. But even a corrupt opportunist can spot a system failure. Bacon proposed a new method to escape these Idols: rather than testing assumptions until they are confirmed (confirmation bias), we should draw well-founded conclusions from experimental data. He explicitly argued for focusing on **negative instances** — evidence that disproves a theory — because that is where the real information hides. He rejected the Church’s stance that "all knowledge is already in the Bible" and demanded work that was **systematic** (repeatable), **empirical** (observation-based), and **inductive**.
 
 ### The Cartesian Cleanroom
 
 Around the same time, in 1632, René Descartes took a slightly different but equally radical approach. He published _Discours de la méthode_ (Discourse on the Method), proposing a universal way to search for truth. If Bacon was about empirical data, Descartes was about rigorous logical hygiene.
 
-His method was simple but brutal: accept nothing as true unless you can verify it yourself through analysis and logical reflection. He demanded **rigorous deduction**—deriving conclusions only from facts that are already proven—and championed mathematics as the only language reliable enough to formulate these insights. Mathematics, unlike spoken language (Bacon's _Idola Fori_), leaves little room for ambiguity.
+His method was simple but brutal: accept nothing as true unless you can verify it yourself through analysis and logical reflection. He demanded **rigorous deduction** — deriving conclusions only from facts that are already proven — and championed mathematics as the only language reliable enough to formulate these insights. Mathematics, unlike spoken language (Bacon's _Idola Fori_), leaves little room for ambiguity.
 
 The full title of his work is _Discourse on the Method of Rightly Conducting One's Reason and of Seeking Truth in the Sciences_. Interestingly, Descartes published this anonymously in Leiden, Netherlands. Why hide his name? Because in 1632, claiming you had a new method for finding truth that bypassed the Church was a good way to get in serious trouble. He was navigating a minefield of authority.
 
@@ -111,7 +111,7 @@ This secrecy was fatal to progress. Because no one shared their lab notes, no on
 
 We love to tell the story that Europe "invented" science, drawing a straight line from the ancient Greeks to Bacon and Descartes. This is a fabrication of history. The sparks that ignited the scientific revolution didn't just fly in London and Paris; they were burning globally for centuries. The European narrative is the result of selective forgetting and, frankly, imperialist history writing.
 
-Consider **Ibn Rushd** (1130–1198), a Cordoban scholar who argued that men and women possessed equal intellect and should have equal rights—a radical idea for the 12th century. He also argued that a concept could not be theologically true but philosophically false (and vice versa), laying the groundwork for separating faith from reason.
+Consider **Ibn Rushd** (1130–1198), a Cordoban scholar who argued that men and women possessed equal intellect and should have equal rights — a radical idea for the 12th century. He also argued that a concept could not be theologically true but philosophically false (and vice versa), laying the groundwork for separating faith from reason.
 
 Then there is **Al-Haytham** (965–1040) from Cairo. If anyone deserves the title of "Father of the Scientific Method," it is him. Centuries before Bacon’s _Novum Organum_, Al-Haytham was running systematic experiments and formulating theories. He explicitly warned against the _Idols_ of authority long before Bacon gave them a name. In his writings, he stated that the seeker of truth is not the one who trusts the writings of the ancients, but the one who "suspects his faith in them" and "attacks [the text] from every side." He argued that to find the truth, one must make oneself an enemy of everything one reads.
 
@@ -127,7 +127,7 @@ This sparked a rebellion. In the mid-17th century, the first scientific societie
 
 This era defined the **First Pillar of Science: Doubt.**
 
-Previously, Truth was the property of authority. If the Pope or the King said it, it was true. Questioning it was treason or heresy. Think of Galileo and Kepler, who were harassed and punished for doubting the geocentric model. But the printing press made doubt resilient. You couldn't burn all the books if they were being printed faster than you could find them. A scene developed of mobile printing presses—literally printing banned books on ships to evade jurisdiction—using censorship lists as market research to see what people wanted to read.
+Previously, Truth was the property of authority. If the Pope or the King said it, it was true. Questioning it was treason or heresy. Think of Galileo and Kepler, who were harassed and punished for doubting the geocentric model. But the printing press made doubt resilient. You couldn't burn all the books if they were being printed faster than you could find them. A scene developed of mobile printing presses — literally printing banned books on ships to evade jurisdiction — using censorship lists as market research to see what people wanted to read.
 
 This solidified the rule: **Everything may be doubted.**
 
@@ -135,19 +135,19 @@ This is not easy. Doubt is uncomfortable. In a pragmatic sense, you can't doubt
 
 ---
 
-_Next up: We break down the engine itself—how we took this philosophy of doubt and turned it into the rigorous, error-checking machine we call the Scientific Method._
+_Next up: We break down the engine itself — how we took this philosophy of doubt and turned it into the rigorous, error-checking machine we call the Scientific Method._
 
 ## Part 3: The Engine of Truth (The Method, Hypotheses, and the Causality Trap)
 
-We established in the previous sections that our brains are glitchy survival engines and that we need a culture of doubt to bypass authoritarian control. Now, we have to build the machine itself. To operationalize that doubt, early scientists—building on the legacy of Bacon and Descartes—formalized a specific set of heuristics to keep us honest.
+We established in the previous sections that our brains are glitchy survival engines and that we need a culture of doubt to bypass authoritarian control. Now, we have to build the machine itself. To operationalize that doubt, early scientists — building on the legacy of Bacon and Descartes — formalized a specific set of heuristics to keep us honest.
 
 The first move was to replace our biological senses with instruments. Since we cannot trust our eyes to judge brightness or our skin to judge temperature objectively, we build devices like thermometers, photometers, and rulers. These tools don't hallucinate, though they aren't magic; they are built by humans and can reflect human bias. The polygraph, or lie detector, is a perfect example of a broken instrument. It measures biological stress (sweat, heart rate), which has no proven correlation with truth-telling. It measures anxiety, not lies, yet we often treat the needle on the chart as an oracle.
 
-We also shifted our language. Spoken languages are messy and loaded with cultural baggage—Bacon’s _Idols of the Market_. To escape this, science adopted mathematics as its core language. Math expresses very little in terms of emotion or nuance, but what it does express, it expresses without ambiguity. Finally, we agreed on a hierarchy of argument where measurable data and verified facts sit at the top, displacing opinion and authority.
+We also shifted our language. Spoken languages are messy and loaded with cultural baggage — Bacon’s _Idols of the Market_. To escape this, science adopted mathematics as its core language. Math expresses very little in terms of emotion or nuance, but what it does express, it expresses without ambiguity. Finally, we agreed on a hierarchy of argument where measurable data and verified facts sit at the top, displacing opinion and authority.
 
 ### Defining the Indefinable
 
-Before we break down the mechanics, we need a working definition of what we are actually doing. Science is best defined as the **continuous process** of describing the world in our symbolic representations—be that language, math, or code—such that the description withstands every critical examination.
+Before we break down the mechanics, we need a working definition of what we are actually doing. Science is best defined as the **continuous process** of describing the world in our symbolic representations — be that language, math, or code — such that the description withstands every critical examination.
 
 It is critical to understand that science is not a static list of facts or a dusty encyclopedia. It is the act of refining a description until you can no longer poke holes in it. It is also not a belief system. Religion seeks salvation; science seeks insight. As the _Science Busters_ motto puts it, science is what holds true even if you don’t believe in it. To navigate this, philosophers use three specific coordinates. We ask what exists (Ontology), what we can actually know about it (Epistemology), and what that means for our values and ethics (Axiology).
 
@@ -161,17 +161,17 @@ Second, we have **Isaac Newton**. Still operating with the mindset of an alchemi
 
 Third is **Fitts’s Law**, a cornerstone of Human-Computer Interaction established by psychologist Paul Fitts in 1954. He mathematically modeled human movement, discovering that the time required to move a pointer to a target is a function of the distance to the target divided by the size of the target. This is why the "OK" button on your software interface is usually large, and why the corners of your screen are considered "infinite width" targets because you can’t overshoot them with a mouse. It is a biological truth encoded into a formula ($ID = \log_2(2D/W)$).
 
-Finally, **Alan Turing** proposed the "Imitation Game" in 1950 to handle the slippery definition of artificial intelligence. Since "intelligence" is hard to ontologically define, he operationalized it: if a machine can trick a human into thinking it is human via text chat, it passes. While we now know this test is flawed—ChatGPT can pass it without possessing understanding—it was a crucial attempt to turn a philosophical question into an experimental procedure.
+Finally, **Alan Turing** proposed the "Imitation Game" in 1950 to handle the slippery definition of artificial intelligence. Since "intelligence" is hard to ontologically define, he operationalized it: if a machine can trick a human into thinking it is human via text chat, it passes. While we now know this test is flawed — ChatGPT can pass it without possessing understanding — it was a crucial attempt to turn a philosophical question into an experimental procedure.
 
 ### The Algorithm: The Classical Scientific Method
 
 These examples reveal a specific loop which forms the second pillar of science: Systematic Procedure. The loop generally flows from observation to speculation, then to the formulation of a hypothesis, followed by an experiment, and finally a conclusion where the hypothesis is either accepted or rejected.
 
-The **Hypothesis** is the critical firewall in this process. It stops us from simply telling stories about what we see. A scientific hypothesis is an inductive leap—a grounded guess that we assume is true until proven otherwise. However, not every statement qualifies. A hypothesis must be testable. Saying "There is an invisible entity controlling the universe" is a bad hypothesis because it cannot be tested. Saying "Cholera is caused by this specific water pump" is a good hypothesis because you can test it by removing the pump handle.
+The **Hypothesis** is the critical firewall in this process. It stops us from simply telling stories about what we see. A scientific hypothesis is an inductive leap — a grounded guess that we assume is true until proven otherwise. However, not every statement qualifies. A hypothesis must be testable. Saying "There is an invisible entity controlling the universe" is a bad hypothesis because it cannot be tested. Saying "Cholera is caused by this specific water pump" is a good hypothesis because you can test it by removing the pump handle.
 
-In statistics, we often use the **Null Hypothesis** ($H_0$), which effectively assumes "innocence until proven guilty." The Null Hypothesis states that there is no connection between two variables—for example, that video games do not cause violence. We hold this as true until the data overwhelmingly forces us to reject it. In the specific case of video games and violence, meta-studies by researchers like Prescott, Sargent, and Hull suggest we might technically reject the Null Hypothesis, but the effect size is so tiny compared to other factors that it is practically negligible.
+In statistics, we often use the **Null Hypothesis** ($H_0$), which effectively assumes "innocence until proven guilty." The Null Hypothesis states that there is no connection between two variables — for example, that video games do not cause violence. We hold this as true until the data overwhelmingly forces us to reject it. In the specific case of video games and violence, meta-studies by researchers like Prescott, Sargent, and Hull suggest we might technically reject the Null Hypothesis, but the effect size is so tiny compared to other factors that it is practically negligible.
 
-There is a "dirty secret" here. The second step of the method—speculation and hypothesis generation—is the only part of science we don't know how to automate. It requires intuition and creativity. It is the one moment where creative thinking is the dominant force in the rigorous scientific process.
+There is a "dirty secret" here. The second step of the method — speculation and hypothesis generation — is the only part of science we don't know how to automate. It requires intuition and creativity. It is the one moment where creative thinking is the dominant force in the rigorous scientific process.
 
 ### Falsifiability and the Experiment
 
@@ -189,19 +189,19 @@ A more subtle example is the **Uncanny Valley**. In 1970, Masahiro Mori hypothes
 
 ### Theory: The Holy Grail
 
-When a hypothesis survives enough attempts to kill it, it graduates to a **Theory**. A theory is a consolidated explanation of a slice of reality. A good theory, like Einstein’s Theory of Relativity, solves open questions and predicts things we haven't seen yet—like black holes—without falling apart under testing.
+When a hypothesis survives enough attempts to kill it, it graduates to a **Theory**. A theory is a consolidated explanation of a slice of reality. A good theory, like Einstein’s Theory of Relativity, solves open questions and predicts things we haven't seen yet — like black holes — without falling apart under testing.
 
 But theories can also be traps. In the late 19th century, the accepted theory of aerodynamics suggested that heavier-than-air flight was effectively impossible or impractical. This was a "bad theory," but it was socially accepted. The Wright Brothers succeeded because they chose to actively doubt the theory. They built their own wind tunnel, generated their own data, and ignored the scientific consensus. Theories are cognitive artifacts that let us think new thoughts, but they are also social artifacts. If the Wright Brothers hadn't flown, the bad theory of aerodynamics might have persisted for another fifty years simply because the experts agreed on it.
 
 ---
 
-_Next up: We enter the messy world of "Paradigms"—why the rules of science change depending on whether you are studying an iron cube or a group of nuns._
+_Next up: We enter the messy world of "Paradigms" — why the rules of science change depending on whether you are studying an iron cube or a group of nuns._
 
 ## Part 4: Whose Truth Is It Anyway? (Paradigms, Bias, and the Limits of Objectivity)
 
 We have built the machine (the Scientific Method), but now we have to decide where to point it. This brings us to the concept of **Paradigms**. A paradigm is essentially a framework of beliefs and assumptions that defines how we look at the world. It dictates what questions we are allowed to ask and what kind of answers we accept as valid.
 
-The scientific revolution ushered in the age of **Modernism**. This was the era of the Industrial Revolution, where we began to view the world as an objective, measurable reality and ourselves as rational, complex machines. It birthed a kind of "techno-solutionism"—the belief that any problem, no matter how human, could be solved with enough engineering. You can see this optimism in the art of the time, like Italian Futurism, which worshipped speed and machinery. But you also see the anxiety in early science fiction. H.G. Wells and Aldous Huxley wrote warnings, but the most striking was perhaps Yevgeny Zamyatin’s 1920 novel _We_, which depicted a dystopian world ruled entirely by cold mathematical logic.
+The scientific revolution ushered in the age of **Modernism**. This was the era of the Industrial Revolution, where we began to view the world as an objective, measurable reality and ourselves as rational, complex machines. It birthed a kind of "techno-solutionism" — the belief that any problem, no matter how human, could be solved with enough engineering. You can see this optimism in the art of the time, like Italian Futurism, which worshipped speed and machinery. But you also see the anxiety in early science fiction. H.G. Wells and Aldous Huxley wrote warnings, but the most striking was perhaps Yevgeny Zamyatin’s 1920 novel _We_, which depicted a dystopian world ruled entirely by cold mathematical logic.
 
 ### The Reign of Positivism
 
@@ -251,7 +251,7 @@ We need all the lenses. If you only have a hammer, every problem looks like a na
 
 ---
 
-_Next up: The ugly truth about the academic industry—fraud, the "Publish or Perish" meat grinder, and how to survive it all with your integrity intact._
+_Next up: The ugly truth about the academic industry — fraud, the "Publish or Perish" meat grinder, and how to survive it all with your integrity intact._
 
 ## Part 5: The Academic Game & How to Play It (Fraud, Metrics, and Practical Wisdom)
 
@@ -265,7 +265,7 @@ But sometimes the fraud is designed to expose the system, not exploit it. In 199
 
 This tradition of "sting operations" continued. In 2005, three MIT students built _SCIgen_, a software that automatically generates grammatically correct but meaningless computer science papers. They submitted a paper titled "Rooter: A Methodology for the Typical Unification of Access Points and Redundancy" to a conference, and it was accepted. In 2009, Philip Davis from Cornell used similar software to submit a paper to _The Open Information Science Journal_. The journal accepted it, asking only for an $800 publication fee. They didn't care about the science; they cared about the check.
 
-The most recent and grotesque example dropped in 2024, when the journal _Frontiers in Cell Development and Biology_—supposedly a peer-reviewed publication—published a paper containing AI-generated diagrams. One diagram featured a rat with a biologically impossible, gargantuan reproductive organ, labeled with gibberish text like "dck." The image went viral on social media, the paper was retracted, and the reviewers claimed it "wasn't their job" to check the images. These aren't just funny anecdotes; they are structural failures showing that the "critical collective review" we rely on is often asleep at the wheel.
+The most recent and grotesque example dropped in 2024, when the journal _Frontiers in Cell Development and Biology_ — supposedly a peer-reviewed publication — published a paper containing AI-generated diagrams. One diagram featured a rat with a biologically impossible, gargantuan reproductive organ, labeled with gibberish text like "dck." The image went viral on social media, the paper was retracted, and the reviewers claimed it "wasn't their job" to check the images. These aren't just funny anecdotes; they are structural failures showing that the "critical collective review" we rely on is often asleep at the wheel.
 
 ### The Grind: Publish or Perish
 
@@ -292,7 +292,7 @@ The first tip is the hardest: Learn to doubt. But you must distinguish between *
 When you are researching or arguing a point, look for sources that confirm your view _and_ sources that contradict it. If you can't find a source that disagrees with you, you aren't looking hard enough. Also, drop the ego about "originality." Extensive citing isn't cheating; it's proof of quality. It shows you have done the work to map the territory.
 
 **3. Discourse Control**
-When someone attacks your idea, your lizard brain thinks they are attacking _you_. You will feel the urge to get defensive. Fight this. Count to ten. Science happens in the **Discourse**—the cool, detached exchange of arguments—not in a heated debate. If you get emotional, you have lost the ability to think critically.
+When someone attacks your idea, your lizard brain thinks they are attacking _you_. You will feel the urge to get defensive. Fight this. Count to ten. Science happens in the **Discourse** — the cool, detached exchange of arguments — not in a heated debate. If you get emotional, you have lost the ability to think critically.
 
 **4. Scientific Reasoning (Induction vs. Deduction)**
 Understand the difference in how you build arguments.
@@ -305,7 +305,7 @@ We end where we began. Your brain is a pattern-matching machine that wants to co
 
 ### Summary
 
-Scientific Thinking is simply a systematic, traceable form of curiosity. It requires admitting that we are easily fooled, that our senses are flawed, and that our biases are strong. It demands that we build systems—peer review, open data, falsification—to protect us from our own nature. Whether you are debugging code, diagnosing a patient, or just reading the news, the goal is the same: to describe the world in a way that withstands critical scrutiny.
+Scientific Thinking is simply a systematic, traceable form of curiosity. It requires admitting that we are easily fooled, that our senses are flawed, and that our biases are strong. It demands that we build systems — peer review, open data, falsification — to protect us from our own nature. Whether you are debugging code, diagnosing a patient, or just reading the news, the goal is the same: to describe the world in a way that withstands critical scrutiny.
 
 ---