It has a oxymoronic feel to it, the title, yet it seemingly is so that relative and absolute complexity downstream makes for a simpler upstream. Examples for this are Kubernetes and Docker, C and Python, and infrastructure surrounding HTTP servers and application servers.
So to take my mind off of things and just trying a little something on the side to get me to become productive again I decided to look into a thing called AssemblyScript.
It has been another long hiatus of writing and in the meantime I started a new job somewhere much better than my previous environment and still I felt like I was stagnating and not moving ahead much.
So I was working with Spring Webflux to fix some issues regarding processing items and not continually processing the same items. I ran into a nice deep issue that I fixed with a simple trick.
I am writing this as we transition from the warm last days of summer, into still warm days of autumn into possibly colder days of winter. The question that always arises, same in spring, is how many layers do I need to wear? I did not know the same question applies to Docker.
My adventure of installing Postgresql 13 on Windows Server without using Docker was met with some resistance. For some reason the installer could not run because it did not have enough permissions to write to a certain folder?
So I learned this the hard way, but in reactive programming, aka my WebFlux project. Do not ever use Void as a type. Just wrap it in something you can propagate like Object, String or Boolean or something else.
Sometimes you need to run Docker containers in different circumstances, like on Raspberry Pi's or you have systems that are just wired differently (Alpine) and sometimes even a combination of those (Alpine on a BananaPi) and you do not always have everything laying around to reproduce it. So what do you do?