Content fixes

src/notes/1-initial-commit/note.md

@@ -1,6 +1,6 @@
 # Initial commit
 
-_2023-09-15_
+_2023-09-15 - 1 minute read_
 
 I've been thinking a long time about having a place to publicly publish things. I'm not really into doing that on social media since it would lock my content in their format and make it hard to move anywhere else so i thought i would just write my "things" in plain markdown and then find a way of hosting them online.
 

src/notes/2-markdown-parser/note.md

@@ -1,16 +1,16 @@
 # Markdown parser
 
-## Part 1
+_2023-09-16 - 5 minute read_
 
-_2023-09-16_
+## Part 1
 
 While traveling today i thought about ways to structure my markdown parser.
 
 What I want is a function that takes a string containing markdown formatted text and outputs a string of html elements.
 
 My plan is to solve this using a markdown line feed and symbol classes representing the different possible elements.
-These symbols are for example headings, list items, code snippets, paragraphs and links.
-Each symbol will know how to render itself as well as being able to tell if it's the right symbol for the current line feed line.
+These symbols are for example headings, list items, code snippets, paragraphs and links. 
+Each symbol will know how to render itself as well as being able to tell if it's the right symbol for the current feed line.
 
 Lets say we have a markdown file that looks something like this:
 

src/notes/3-tunneling-traffic-through-ssh/note.md

@@ -1,5 +1,7 @@
 # Tunneling traffic through ssh
 
+_2024-12-23 - 1 minute read_
+
 This lets you tunnel port 80 from your machine, to port 80 on another machine, using some ssh server as jump node.
 
 ```bash

src/notes/4-converting-document-formats/note.md

@@ -1,5 +1,7 @@
 # Converting various document formats
 
+_2025-01-10 - 1 minute read_
+
 I was in need of a way to convert markdown documents + images into pdfs and came over the [pandoc](https://pandoc.org/) project which seems to be very powerful.
 
 This is how i used it.

src/notes/5-measuring-mash-temperatures/note.md

@@ -13,7 +13,7 @@ Esphome made the setup very easy. After defining the onewire hub component i cou
 
 ![nodemcu](@asset/3.png)
 
-My esphome instance is running in my local homeassistant (HASS) instance which integrates neatly and makes all sensors available to both systems. I created a new view in HASS and added the sensors showing the current values as well as a histogram of the last 5 minutes thinking that is should be a reasonable timespan to have when comparing temperatures. To my suprise the 5 minute interval in HASS didn't show 5 minutes at all but rather 24h. It was possible to zoom in on the graph to see it in more detail but i wasn't happy with how it turned out. Ideally I wanted this view to be visible on one of my screens in my brewery and it should show what I want to see without me having to interact with it.
+My esphome instance is running in my local homeassistant (HASS) instance which integrates neatly and makes all sensors available to both systems. I created a new view in HASS and added the sensors showing the current values as well as a histogram of the last 5 minutes thinking that it should be a reasonable timespan to have when comparing temperatures. To my suprise the 5 minute interval in HASS didn't show 5 minutes at all but rather 24h. It was possible to zoom in on the graph to see it in more detail but i wasn't happy with how it turned out. Ideally I wanted this view to be visible on one of my screens in my brewery and it should show what I want to see without me having to interact with it.
 
 ![nodemcu](@asset/4.png)
 
@@ -27,7 +27,7 @@ We usually brew two batches the same day since it allows us to do utilize the ti
 
 ![mash](@asset/mash.png)
 
-We did the first batch as usual, heating up the water to 67c before dumping in the malt pipe along with our 5KG grain bill of mostly pilsner malt and some wheat. Historically we have been going off of the bult in temperature sensor in the bottom of our brewzilla brewsystem, but one of its flaws is that the sensor is located right above the two heating elements which means that it is going to measure the warmest water in the pot. This works for turning the heater on and off while recirculating using a pump while the brewery has no equipment or ingredients in it, but as soon as you add anything it is no longer going do represent the temperature of the whole vessel. We put the first sensor below the malt pipe right above the false bottom of the brewery, then we put the second one in the middle of grains.
+We did the first batch as usual, heating up the water to 67c before dumping in the malt pipe along with our 5KG grain bill of mostly pilsner malt and some wheat. Historically we have been going off of the built-in temperature sensor in the bottom of our brewzilla brewsystem, but one of its flaws is that the sensor is located right above the two heating elements which means that it is going to measure the warmest water in the pot. This works for turning the heater on and off while recirculating using a pump while the brewery has no equipment or ingredients in it, but as soon as you add anything it is no longer going do represent the temperature of the whole vessel. We put the first sensor below the malt pipe right above the false bottom of the brewery, then we put the second one in the middle of grains.
 
 ![Picture of first batch mash temperature graph](@asset/first-batch-mash-graph.png)
 _Yellow: temperature of the grain bed. Green: temperature just below the malt pipe._
@@ -46,4 +46,12 @@ For the next batch we heated up the strike water to 75c. After adding the malt p
 
 Now we just had to maintain that temperature, something that we have done before with great success by setting the heaters to 67c and starting to pump.
 
-![Picure of second mash histogram](@asset/second-batch-mash-histogram.png)
+![Picture of second mash histogram](@asset/second-batch-mash-histogram.png)
+
+By the end of the brew day the last batch measured 1.050 so suprisingly we ended up 4 points below the last batch that was identical recipe-wise. That could of course be due to multiple factors. We use pre-milled grain so depending on if we use the malt from the top or the bottom of the bucket there might be more or less grain flour. Or perhaps the mash is just more efficient at a bit lower temperature. However from what I've read the most efficient mashing range is between 65-67 degrees celcius so I'm a bit confused.
+
+I think we need to brew some more beers using this method and see if we if it increases our result to recipe accuracy.
+
+In the end the only thing that matters is that we brew good tasting beer and i don't think this process will change much when it comes to that. It's just feels good to hit the target!
+
+Cheers!