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.
Try submitting a pull request for something in one of the core repos.
They behave as if every line of code in your commit is a sentence proclaiming "Why yes, your wife is a whore, your dog doesn't love you, AND your baby is ugly."
I'm not kidding, there's no hyperbole in that statement. Go read some of their declined pull requests threads for some entertainment.
Even those who try to contribute to the project get eventually feeling pushed out.
Submitting a pull request to one of their repos on Github was really an experience, and I can tell you that I will never submit another one to the Lemmy project while they're still the lead devs based on that experience.
It would be better to our them on blast on social media since that sometimes gets the companies attention to try and fix PR.
Works almost every time. I had a ticket with a vendor open at work for just about 3 months, and then only replies I'd gotten on the ticket was the "We've received your support request which we'll promptly ignore!" autoresponse upon opening, and then another auto-response a month later saying the ticket was being assigned to another department. I'd replied to the ticket ~20 times asking for updates in that time.
I finally got sick of essentially yelling into an empty room and called out the company, their marketing team, their support team, and their CEO on Twitter, making sure to @ each one of them in the message. I got a reply from their CEO and an actual human responded to the ticket less than an hour later.
It's shitty and a last resort, but it's generally very effective.
I have a Hisense and had a similar experience. I was watching something fullscreen on an HDMI input, and then it suddenly switched inputs and showed a fullscreen firmware update prompt. I had no choice available other than to agree to update the firmware, no cancel button, couldn't change inputs, nothing, the only choice was to update the firmware. So I unplugged the TV.
About 10 seconds after I powered it back on, the exact same update prompt happened, still with no choice to decline it. I pulled power and booted it back up one more time just to be sure, met with the update prompt again.
This made me very angry.
The next time I powered it on, I had a packet capture running to see where it was phoning home. I created a firewall rule blocking all the hostnames it tried to connect to at startup, pulled the plug, and then booted it back up. No more update prompt, and it hasn't happened again. Good thing they don't download and pre-stage the new firmware, I guess.
Let me know if you want the hostnames and I'll PM them to you.
Lots of those in C# now, especially with Unity coming along like it did.
On Error Resume Nextnever before have more terrible words been spoken.
Every time I'm reading a PowerShell script at work and see -ErrorAction SilentlyContinue I want to scream into a pillow and forcefully revert their commit.
I've actually done it a few times, but I want to do it every time.
Eh, it depends. Other low-level things (systemd, glibc, etc) need a reboot too.
It's likely because they use it as the primary/unique identifier for the account, which is just dumb. It's like they've never heard of a UUID/GUID before.
CBOE will create options for it pretty soon after IPO, probably that week or the next. You'll definitely be able to buy puts on it before you'll be allowed to short sell it.
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.