• 8 Posts
  • 178 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • I’ve seen some shit. But I’m also old enough to not care. I’m a freaking system administrator, not a surgeon. No one has died if their email is unreacable for an hour or two. Shit happens, then you deal with it and that’s all. Difference between a junior and a seasoned veteran is that old guys with battle scars is that the seasoned guy knows that something will break, shit will hit the fan and everything might turn up into a chaos and plan accordingly. Juniors will either endure and learn along the way or crumble.

    When you’ve been in the business for few decades it’s not that big of a deal to cause an outage. You know how to fix your shit, you know how to work with a severely crippled environment and you know how to build the whole circus from the ground up. And you also know that no matter how disappointed or loud the C** suits are, they’ll calm down once you get them out of the hole.

    Just today I had a meeting with discussion on what to do if some obscure edge-case ruins our ~5k users and few continents wide AD tree. Sure, if that would happen, it would most definetly suck balls to get back up and it would hurt the company bottom line and it would mean few nights with very little sleep, but no one would still die and our team is up to the task to build the whole crap out of nothing if needed. So, it’s just business as usual. But all of us have been in the business long enough that we know how to avoid the common pitfalls and we trust eachother enough that should the shit hit the fan in the big way we could still recover the whole situation.

    And still, even if the whole thing burns up in the flames, I’ve got the experience and skillset under my belt which will be valuable to some other business entity. I just don’t care if the main office building is on literal fire. It’s not my problem to fix immediately and when it is it’s still just work. I put in the hours they pay for me and do whatever I can but when I’m off the clock the employer doesn’t really exist in my world.



  • Neither can Ukraine.

    True, but Ukraine has played this game pretty well in my opinion. They keep negotiations going, speak nicely about the deal in public and at least in here media represents Ukraine as willing and open of discussion about whatever deal Trump suggests, no matter how bat shit crazy they are.

    I mean, Ukraine isn’t stupid enough to sign off all of their wealth to USA or surrender land without any significant gain. But they can now at least say that they’re willing to discuss about the matter while Russia just bluntly rejects the proposals.




  • Good luck with trying to evade payments.

    I don’t know how things work in Germany but here in Finland we have an government agency which pays salaries if company can’t or won’t as a safeguard for employees. After that they go after the company with pretty beefy lawsuits which eventually say that either the company pays for the salaries and some extra for the trouble or government just seizes and sells enough property that they get what they’re owed. And if company doesn’t have money nor property then it’ll go bankrupt and that’s it. I assume Germany (and most of the other European countries) have similar mechanisms.

    And then there’s of course the union too. They can just decide to either stop coming to work altogether or go in a ‘sitting strike’, as in show up but don’t do anything during the day. And they can enforce that, you can’t just hire new people to replace those on strike.


  • people using it are not secure at all.

    And this is very much not limited just to signal. No matter what software, protocol or any other way you use to communicate, both you and the receiving entity/entities are the weakest link by a long shot. I don’t expect even my closest friends to hold our everyday conversations secret if for whatever reason their wellbeing was threated in any way. And even if I did there’s always other options, like targeted social engineering, to get trough pretty much any reasonable safety concerns on digital communication.

    Of course in everyday life if our chat histories were publicly available it would not be too big of an issue, but it’s still something worth keeping on mind when interacting over any digital or any other written medium.







  • Debian. I’ve had installations which went trough several major version upgrades, I’ve worked with ‘set and forget’ setups where someone originally installed Debian and I get my hands on it 3-5 years later to upgrade it and it just works. Sure, it might not be as fancy as some alternatives and some things may need manual tweaking here and there, but the thing just works and even on rare occasion something breaks you’ll still have options to fix it assuming you’re comfortable with plain old terminal.


  • Don’t know what Elmos minions are doing, but I’ve written code at least equally unefficient. It was quite a few years ago (the code was in written in perl) and I at least want to think that I’m better now (but I’m not paid to code anymore). The task was to pull in data from a CSV (or something like that, as I mentioned, it’s been a while) and it needed conversion to XML (or something similar).

    The idea behind my code was that you could just configure which fields you want from arbitary source data and on where to place them on the whatever supported destination format. I still think that the basic idea behind that project is pretty neat, just throw in whatever you happen to have and have something completely else out of the other end. And it worked as it should. It was just stupidly hungry for memory. 20k entries would eat up several gigabytes of memory from a workstation (and back then it was premium to have even 16G around) and it was also freaking slow to run (like 0.2 - 0.5 seconds per entry).

    But even then I didn’t need to tweet that my hard drive is overheating. I well understood that my code is just bad and I even improved it a bit here and there, but it was still so very slow and used ridiculous amounts of RAM. The project was pretty neat and when you had few hundred items to process at a time it was even pretty good, there was companies who relied on that code and paid for support. It just totally broke down with even a slightly bigger datasets.

    But, as I already mentioned, my hard drive didn’t overheat on that load.


    1. VM running on a proxmox host. Tips: make sure you know your backups are in a state you can restore data from them.
    2. Nightly backup via proxmox to Hetzner Storage box with 2 day retention. I’d like a local copy too but I don’t currently have hardware for it.
    3. Don’t know. Personally I have a DNAT rule on firewall and my instance is directly open to the internet. You might not want that and I might not recommend it, but right now, for me, it works. I’d need to look in a VPN solution for android I could replace the current ‘open for all’ situation.