Debugging container workloads can be a challenge sometimes, especially when running them in k8s,
behind a reverse proxy or in other, possibly complex, traffic flow scenarios.
Copy & paste from untrusted sources on the internet into the terminal is a really bad idea!
Early in my career I did it too and still often see others doing it.
I write an extensive personal knowledge base using markdown, code-server and a variety of other tools.
Originally, in 2021, I wanted to have something like Obsidian Publish but self-hosted, so I created it.
Over time my knowledge base evolved more into a second brain, tracking not only my technical notes and journal, but also things like recipes and hikes.
With this my publishing pipeline, and the script at it’s core, extended in a multitude of ways.
This is a guide to a simple self organization/task management system I built for myself over the years.
From time to time I showed it to someone and they got some benefits from it, most adapted it to better fit their needs down the line,
which is exactly what you should do with any kind of personal task management in my opinion.
Sometimes you have to do a specific task and you are fully capable of doing it manually,
however those tasks are also great to flex your muscles and hack something together.
They can be an excellent tool to sharpen your skills with the tools you use regularly,
and improve your quick prototyping skills.
In addition, with a couple of iterations, again sharpening an important skill, you could afterwards create a more general purpose tool from a hacky script.
Given the recent rise in text-based language models, sometimes called AI tools, I wanted to share my thoughts and experiences in using them,
especially in the context of blogging.
