• 3 Posts
  • 64 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle

  • There is so much old and creaky stuff lying around and people have no idea what it does. Beige boxes in a cabinet that when we had to decommission it the only way to understand what it does was doing the scream test: turn it off and see who screams!

    Or even stuff that was deployed as IaC by an engineer but then they left and so was managed “clickOps”, but documentation never updated.

    When people talk about the Tier1 systems they often forget the peripheral stuff required to make them work. Sure the super mega shiny ERP system is clustered, with FT and DR, backups off site etc. But it talks to the rest of the world through an internal smtp server running on a Linux box under the stairs connected to a single consumer grade switch (I’ve seen this. Dust bunnies were almost sentient lol).

    Everyone wants the new shiny stuff but nobody wants to take care of the old stuff.

    Or they say “oh we need a new VM quickly, we’ll install the old way and then migrate to a container in the cloud”. And guess what, it never happens.



  • As @candyman337@sh.itjust.works said, use a recruiter/agency. Post your CV to indeed and reed. It depends also where you are, in EU the job boards are different than US I guess. Speaking of LinkedIn, have you posted a message saying “hello world, I’m open to work and I’ve experience at this $stuff”, and then ask your friends to share it. I got a couple of contacts that way.

    Also, look for a resume builder/parser. Quick search gave me https://www.open-resume.com/ https://noted.lol/open-resume/

    Pretty much everyone uses a CV parser when you apply, so if your is not formatted properly it’s properly one of the reasons you get rejected. Another reason is that probably they recognize you are above what they need, so they know that a) you’d be expensive and b) probably get bored fast and leave. Put stuff you have experience with, specifying what your experience is, what your contributions were to the project etc. Saying “5 years of experience on $language” is not very meaningful. Writing “I created a Perl program to import data from Word docs to a MySQL DB, optimizing the code to use no explicit variables” (true story btw) is better. Or most likely “worked on $project for $industry, implementing $modules and enforcing $best_practice, collaborating with the wider team and helping mentoring other junior developers”. Don’t forget to mention non-technical skills. Companies look for someone whom is nice to work with more than someone who knows everything. A guru that alienates people is less worthy than someone that maybe don’t know everything (and admits it) but can talk to others.

    Re: time wasters. Holy shit 8 round of interviews! Even MS and AWS are less than that! MS was the biggest in my experience with 5 (but tbh it was all in a day, so not a horrible drawn out process, just different people). But you can ask at the beginning when speaking with the hiring manager what’s the process, and you can decide if it’s something you want to spend time on or nah.

    Best of luck and don’t be discouraged! I had a 3 months dry spell once, applying every day to multiple roles and being rejected. It’s part of the game I’m afraid. Venting helps. Not getting a job immediately is not a failure in your part.

    Best of luck!







  • That article is SO wrong. You don’t run one instance of a tier1 application. And they are on separate DCs, on separate networks, and the firewall rules allow only for application traffic. Management (rdp/ssh) is from another network, through bastion servers. At the very least you have daily/monthly/yearly (yes, yearly) backups. And you take snapshots before patching/app upgrades. Or you even move to containers, with bare hypervisors deployed in minutes via netinstall, configured via ansible. You got infected? Too bad, reinstall and redeploy. There will be downtime but not horrible. The DBs/storage are another matter of course, but that’s why you have synchronous and asynchronous replicas, read only replicas, offsites, etc. But for the love of what you have dear, don’t run stuff on bare metal because “what if the hypervisor gets infected”. Consider the attack vector and work around that.






  • the question is: why do you want to move on from the Rpi4? Also, how do you plan to handle video decoding 0f x265/av1 streams? Do those miniPCs have a video card with hardware transcoding capabilities? If you plan to do it on software (i.e. CPU transcoding) the CPUs will run hot most of the time.