I’m in this comment and I don’t like it.
I just finished up a ~700 line PowerShell script to send input/keep a login session from timing out due to inactivity, and prior to that was a Python script to format LetsEncrypt SSL certs in a way haproxy likes + an accompanying Bash script to make sure those certs are correct, check in the current good haproxy config to a git repo, and then restart it if there are new certs.
The only thing that I know is that I know nothing.
Before I replace it with something that won’t catastrophically collapse when the wind blows the wrong way, I get some sort of sick satisfaction out of doing autopsies on the house-built-of-matchsticks “solutions” that users come up with and I don’t know why. Some of them are truly fascinating and make you wonder how someone could possibly arrive at that conclusion based on what they were actually try to achieve.
It’s also why if I’m asked to implement something, my first question isn’t “When does this need to be done?,” it’s “What exactly is the problem you’re trying to solve?”
What a user asks for and what they actually need very rarely intersect.
Seriously, it feels like 1999 internet. And I’m loving it!
56K modem handshake sound intensifies
really wish Linux would could up something similar.
I mean, it kinda already exists. Just run it in a Docker container and remap the users in the container to non-existent uids/gids on the host.
I wonder when there will be a Windows client for KDE Connect.
Sorry, I missed this comment. I actually love doing that kind of shit, I get some sort of weird pleasure out of fixing chaotic stuff like that. That tends to be my role almost all the time; I’ll come in, stay a few years, fix everything and get bored, and then move on somewhere else to do it again.
My current job is the only place that I haven’t done that, because it’s probably the best company that I’ve ever worked for.