Fixed some typos, added new post about "a second pair of eyes".

Author: redcatbear

content/posts/2018/10/31/openfasttrace-2-0-2-released.md

@@ -1,5 +1,5 @@
 ---
-title: "Openfasttrace 2 0 2 Released"
+title: "OpenFastTrace 2.0.2 Released"
 date: 2018-10-31T20:29:27+02:00
 draft: false
 params:

content/posts/2018/11/24/gradle-plugin-upgraded-to-openfasttrace-2-1-0.md

@@ -1,5 +1,5 @@
 ---
-title: "Gradle Plugin Upgraded to Openfasttrace 2.1.0"
+title: "Gradle Plugin Upgraded to OpenFastTrace 2.1.0"
 date: 2018-11-24T20:33:37+02:00
 draft: false
 params:

content/posts/2019/01/14/test-coverage-pitfalls.md

@@ -0,0 +1,30 @@
+---
+title: "Test Coverage Pitfalls"
+date: 2017-01-14T15:29:02+02:00
+draft: false
+params:
+    author: Sebastian
+---
+
+When did I test enough?
+
+While code coverage is a good indicator, you still have to know how code coverage works. Today I was hunting a bug in a Markdown importer I wrote for OpenFastTrace. The class where the bug sits had a whooping 93.1% code coverage and part of that missing coverage was owed to the fact that the JaCoCo coverage tracer can’t mark code that throws exceptions as covered – even though there is a test case for it.
+
+So I wrote a new issue ticket, created a fix branch and wrote a three line test case that reproduced the problem. While the test now failed as expected, the code coverage didn’t go up.
+
+I used the [Mockito](http://mockito.org/) mocking framework to verify that an interaction with a mocked observer happened or in my case due to the bug didn’t.
+
+The error was hiding in a regular expression which read
+
+"Needs:\\s*(\\w+(?:,\\s*\\w+)+)"
+
+instead of
+
+"Needs:\\s*(\\w+(?:,\\s*\\w+)*)"
+
+Notice the asterisk in the end.
+
+So while there are a lot test cases waiting to be written for this regular expression, code coverage won’t tell you.
+
+You get what you measure, so be sure you understand what it is you are measuring.
+

content/posts/2024/06/04/tracability-talk-at-the-xen-summit.md

@@ -1,6 +1,6 @@
 ---
 title: "Tracability Talk at the Xen Summit"
-date: "2024-06-04T19:59:27+02:00"
+date: 2024-06-04T19:59:27+02:00
 draft: false
 params:
     author: Sebastian

content/posts/2024/06/29/a-second-pair-of-eyes.md

@@ -0,0 +1,36 @@
+---
+title: "A Second pair of Eyes"
+date: "2024-06-29T13:53:22+02:00"
+draft: false
+params:
+    author: Sebastian 
+---
+
+Which developer does not know this situation: you debug like a mad person and form all sorts of crazy theories my the code in front of you does not work. Especially if you are new to a topic — like we are with our shiny new Hugo blog.
+
+When I created the blog, I intended to keep the directory structure identical to the old WordPress blog:
+
+    <domain>/<year>/<month>/<day>/<post>
+
+All good and well, until I updated to a different theme, because the [minimal theme](https://github.com/calintat/minimal) by Calin Tataru that I originally chose — and which I still find stunningly beautiful in its clean simplicity — is apparently not maintained anymore. At least the last commit dates four years back.
+
+But this story was not supposed to be about the challenges of supply chain management. That's a whole different story.
+
+It's about your thoughts going in circles and ending up in a cargo cult[^1]. I had all sorts of crazy theories, why we only get the year 2018 in the index with the new theme. I even hypothesized that a kind of hidden cache in Hugo held pre-built pages.
+
+Turns out, I couldn't have been more off. Christoph, whom I called for help debugged the current template and found out that Hugo has a concept of main sections. And 2018 simply got auto-picked because it had the most entries.
+
+So here's the fix:
+
+1. Put your posts under the top level directory `posts`
+     ```
+    <domain>/posts/<year>/<month>/<day>/<post>
+    ```
+2. List it in the configuration
+   ```yaml
+   params:
+     mainSections: ['posts']
+
+Big thanks to Christoph for saving my sanity.
+
+[^1]: The term "[Cargo cult](https://en.wikipedia.org/wiki/Cargo_cult)" refers to the practice of primitive civilizations believing that one factually unconnected thing influences the other, because the mechanism behind the correlation is not understood by the observer. First appearance of the term "cargo cult" in print Norris Mervyn Bird, *Pacific Islands Monthly*, November 1945.