It's hard to understand abstraction when unfamiliar with the underlying mechanisms and patterns. This is why I don't like it when things magically work. I need to know how and why.
So yes, this article is about how I cope with the unfavorable circumstances that are pulled in as a dependency when being a junior web developer in 2024.
Armadillo says no.
The page you are currently reading is generated using the Armadillo CLI. It's a series of modules I ended up with while automating the creation of TailwindCSS pages from templates without pulling a huge entity into my project. I just want to edit the HTML once and have the changes reflect on all pages. So footer.py, just a small Python script that looks at my footer template and recursively applies changes to all pages of my site. Simple and fun. But what if... the whole codebase was managed this way?
"Is that a footer.py? Are you web people like...ok?"
Oh yeah, why not just have my elements in a template library? A Python script to edit / generate / delete / replace anything I want in the site's HTML files. I like working in the terminal, so a shell script to use the tool. This might not be the right way to do it, but it's my way. Call in the cyber police to mog my repo; this is how I'll be managing my static site files from now on. A link to the tool will be included in the 'description' below this article. But I can hardly recommend using it. It's made for my specific use case and comes with no support for basically anything. The codebase is a mess, my catastrophe. No one other than me ever needs to work on it. There are zero plans to turn this into a usable tool for anyone else. The point I'm getting to is that you should make your own armadillo protocol. If you don't feel like using something, make your own. It's complicated only if you have to support other ways to do it than your way.
"UI needs the mouse = unusable"