3 files changed, 10 insertions, 18 deletions

diff --git a/content/posts/2019-01-03-encoding-binary-data-into-dna-sequence.md b/content/posts/2019-01-03-encoding-binary-data-into-dna-sequence.md
index 8bd8d74..2ec9387 100644
--- a/content/posts/2019-01-03-encoding-binary-data-into-dna-sequence.md
+++ b/content/posts/2019-01-03-encoding-binary-data-into-dna-sequence.md
@@ -367,10 +367,10 @@ First we generate some binary sample data with dd.
 dd if=<(openssl enc -aes-256-ctr  -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero) of=1KB.bin bs=1KB count=1 iflag=fullblock
 ```
 
-Our freshly generated 1KB file looks something like this (its full of garbage
-data as intended).
 
 ![Sample binary file 1KB](/posts/dna-sequence/sample-binary-file.png)
+Our freshly generated 1KB file looks something like this (its full of
+garbage data as intended).
 
 We create following binary files:
 
diff --git a/content/posts/2021-12-25-running-golang-application-as-pid1.md b/content/posts/2021-12-25-running-golang-application-as-pid1.md
index e09bbc9..d4db07d 100644
--- a/content/posts/2021-12-25-running-golang-application-as-pid1.md
+++ b/content/posts/2021-12-25-running-golang-application-as-pid1.md
@@ -23,7 +23,7 @@ Really worth a read.
 If we compare a normal operating system to a unikernel side by side, they would
 look something like this.
 
-![Virtual machines vs Containers vs Unikernels](/posts/pid1/unikernels.png)
+![Virtual machines vs Containers vs Unikernels](/posts/pid1/unikernels.webp)
 
 From this image, we can see how the complexity significantly decreases with
 the use of Unikernels. This comes with a price, of course. Unikernels are hard
diff --git a/content/posts/2022-10-06-state-of-web-technologies-in-year-2022.md b/content/posts/2022-10-06-state-of-web-technologies-in-year-2022.md
index e0beed8..ab07a2d 100644
--- a/content/posts/2022-10-06-state-of-web-technologies-in-year-2022.md
+++ b/content/posts/2022-10-06-state-of-web-technologies-in-year-2022.md
@@ -27,9 +27,9 @@ elements.
 So, the natural way to go would be some sort of SPA (single page application)
 with basic routing and some state management. Nothing crazy.
 
-> **Before we move on**, I have to be transparent. Take my views on this with 
-> a grain of salt. I have only scratched the surface with these technologies, 
-> and my knowledge is full of gaps. This is my experience using some of these 
+> **Before we move on**, I have to be transparent. Take my views on this with
+> a grain of salt. I have only scratched the surface with these technologies,
+> and my knowledge is full of gaps. This is my experience using some of these
 > products for the first time or in a limited capacity.
 
 Having this out of the way, I got myself a fresh pot of coffee and down the
@@ -62,11 +62,6 @@ I still reject calling [Typescript](https://www.typescriptlang.org/) to
 [JavaScript](https://www.javascript.com/) conversion a "compilation process".  I
 call them [transpilers](https://devopedia.org/transpiler), and I don’t care! 😈
 
-And if you want to fight this, take a look at this little chart and be mad at
-it!
-
-![Compiling vs Transpiling](/posts/state-of-web/compiling-vs-transpiling.png)
-
 The first one that I ever used was [webpack](https://webpack.js.org/), and it
 was an absolute horrific experience. Saying this, it is an absolutely fantastic
 tool. I felt more like a config editor than actually a programmer.  To be fair,
@@ -195,15 +190,13 @@ All of these options end up creating a fatigue. What to choose, what not to
 choose. Unnecessary worrying about if the stack will still be deemed worthy in
 six months. There is elegance in simplicity.
 
-> JavaScript UI frameworks and libraries work in cycles. Every six months or 
-> so, a new one pops up, claiming that it has revolutionized UI development. 
-> Thousands of developers adopt it into their new projects, blog posts are 
-> written, Stack Overflow questions are asked and answered, and then a newer 
+> JavaScript UI frameworks and libraries work in cycles. Every six months or
+> so, a new one pops up, claiming that it has revolutionized UI development.
+> Thousands of developers adopt it into their new projects, blog posts are
+> written, Stack Overflow questions are asked and answered, and then a newer
 > (and even more revolutionary) framework pops up to usurp the throne.
 > — Ian Allen
 
-![To many options](/posts/state-of-web/2008-vs-2020.png)
-
 And this jab at these libraries and cloud providers is not done out of malice.
 It is a real concern that I have about them. In my life, I have seen
 technologies come and go, but the basics always stick around. So surrendering
@@ -301,4 +294,3 @@ tools like Vite. But I will not waste my time on this anymore.
 It was a good exercise to get in touch with what’s new now. Nothing really
 changed that much. FOMO is now cured! Now I have to get my ass back to actually
 code and make the project that I wanted to make in the first place.
-