Add chaos-engineering-failure-injection-low-cost-experiments article

Author: webstackdev

.vscode/settings.json

@@ -12,6 +12,7 @@
     "AIMD",
     "amondnet",
     "anonymization",
+    "appns",
     "Asana",
     "bento",
     "bezier",
@@ -23,6 +24,7 @@
     "CCPA",
     "Centricity",
     "cfduid",
+    "chaosk",
     "cnst",
     "codel",
     "Consolas",
@@ -46,6 +48,7 @@
     "finnadie",
     "firko",
     "Flink",
+    "flowid",
     "FNAME",
     "fosstodon",
     "FOUC",
@@ -72,6 +75,8 @@
     "KHTML",
     "koko",
     "kubeval",
+    "kustomization",
+    "Kyverno",
     "labelledby",
     "LGPD",
     "lighthousejs",
@@ -98,6 +103,7 @@
     "navigations",
     "ndots",
     "nektosact",
+    "netem",
     "Neue",
     "Niklas",
     "noabbr",
@@ -110,6 +116,7 @@
     "oncall",
     "Onest",
     "optin",
+    "PERC",
     "pgbouncer",
     "PGRST",
     "pids",
@@ -119,10 +126,12 @@
     "Postg",
     "postgrest",
     "preemptible",
+    "prio",
     "psql",
     "Pulumi",
     "Pybreaker",
     "pylint",
+    "qdisc",
     "qpart",
     "qparts",
     "Qualys",
@@ -156,6 +165,7 @@
     "tfsec",
     "TIMESTAMPTZ",
     "tktco",
+    "toxiproxy",
     "Trino",
     "TRUNC",
     "Tscompile",

COVERS.md

@@ -223,3 +223,25 @@ Create an image showing a "purge wave" propagating across a network of edge node
 ### Prompt 5: The Correctness vs Performance Balance
 
 Design a balance scale where one side holds "Performance" (represented by speed/lightning icons, high CHR numbers) and the other holds "Correctness" (represented by checkmarks, security shields). The scale is balanced but precarious. Below the scale, "cache misconfiguration" tips it dangerously toward performance. Style: classical balance scale with modern tech iconography, warning colors where imbalanced, 16:9 aspect ratio.
+
+## chaos-engineering-failure-injection-low-cost-experiments
+
+### Prompt 1: The Controlled Demolition
+
+Create an image of a controlled building demolition where specific structural elements are being strategically removed while engineers observe from a safe distance with monitoring equipment. The building remains standing but reveals its structure. Style: architectural illustration, dramatic but controlled, dust and debris contained, blue safety barriers visible, 16:9 aspect ratio.
+
+### Prompt 2: The Lab Experiment
+
+Design an image of a scientific laboratory where engineers in lab coats are conducting controlled experiments on miniature server infrastructure. Beakers and test tubes are replaced with small server racks and network diagrams. Safety goggles, controlled environment, careful observation. Style: scientific illustration meets tech infrastructure, clean lab aesthetic, blue and white colors, 16:9 aspect ratio.
+
+### Prompt 3: The Stress Test
+
+Illustrate a system (represented as interconnected glowing nodes) being deliberately stressed in one area while monitors display the ripple effects. The stress point is contained (visible barrier) while the rest of the system continues operating. Data flows around the stress point. Style: abstract network visualization, glowing connections, red stress point with blue healthy areas, 16:9 aspect ratio.
+
+### Prompt 4: The Fire Drill
+
+Create an image of a modern office building during a fire drill—orderly evacuation, clear signage, safety equipment visible—as a metaphor for chaos engineering. People are calm because they practiced. The "fire" is controlled (small flames in a training area). Style: architectural cutaway showing organized response, warm safety colors against cool building tones, 16:9 aspect ratio.
+
+### Prompt 5: The Vaccine Metaphor
+
+Design an illustration showing a small, controlled "virus" (representing failure) being introduced to a system that develops "antibodies" (resilience improvements) in response. The system becomes stronger after exposure. Scientific/medical aesthetic applied to infrastructure. Style: biological illustration meets system architecture, microscope view aesthetic, greens and blues, 16:9 aspect ratio.

_TODO.md

@@ -251,12 +251,13 @@ Let's write our next article. Review ./CONTENT.md for the goals and voice to use
 
 Act as a principal software engineer. Your goal is to write a detailed technical article based on the provided outline. Context: The target audience is Senior DevOps and infrastructure Engineers. The tone should be authoritative, professional, and concise, avoiding fluff or filler words. Think step-by-step before writing to improve the accuracy of technical explanations. Use a friendly first-person voice. Anything that reads like generic marketing copy is not what we want but we still want the effect of being "real" and approachable - try not to sound like technical documentation. We want to show empathy for our readers.
 
-Let's work through each article section by section based on the H2 headers in the outline. Write directly into the *.astro article file, not into the chat window (it's difficult to read). If the section looks good as-is, I'll just type "ok" so you know to continue to the next section.
+Let's work through each article section by section based on the H2 headers in the outline. Do not do the whole document in one pass. Write directly into the *.astro article file, not into the chat window (it's difficult to read). If the section looks good as-is, I'll just type "ok" so you know to continue to the next section.
 
 - Ignore the coverAlt frontmatter line that has "TODO". It will be added later when cover art is added.
 - Use a single underscore for emphasis style, not asterisks.
 - Use plain quotations and apostrophes, not smart quotes. Do not start the article with an H1 in the Markdown - the system automatically adds the title frontmatter key as an H1 header.
 - Prefer contracted forms like "Here's" instead of "Here is". The content is so technical I want to make it a little more approachable.
+- Let's not use code blocks if it's just a presentation gimmick. Code blocks should be pseudocode that applies to a real tool, or in a limited usage (once per file), a markdown runbook.
 - If it's necessary to show a nested code fence inside a markdown code fence in the document (for example, a markdown runbook that has a prometheus config example inside the runbook), escape the backticks for the nested code fence so that our system handles it correctly. Ensure there is a blank line before and after the escaped code fence. For example:
 
 ```markdown title="some-runbook.md"