33

Ooof.

In a meeting with my client today, about issues with their staging and production environments.

They pull in the lead dev working on the project. He's a 🤡 who freelanced for my previous company where I was CTO.

I fired him for being plain bad.

Today he doesn't recognize me and proceeds to patronize me in server administration...

The same 🤡 that checks production secrets into git, builds projects directly in the production vm.

Buckle up... Deploys *both* staging and production to the *same* vm...

Doesn't even assign a static IP to the VM and is puzzled when its IP has changed after a relaunch...

Stores long term aws credentials instead of using instance roles.

Claims there are "memory leaks", in a js project. (There may be memory misuse by project or its dependencies, an actual memory leak in v8 that somehow only he finds...? Don't think so.)

Didn't even set up pm2 in systemd so his services didn't even relaunch after a reboot...

You know, I'm keeping my mouth shut and make the clown work all weekend to fix his own hubris.

Comments
  • 13
    Bloody hell.... Like half of are things hobbyists know not to do
  • 12
    I fired him for a reason, after all.

    But it was so unnerving having him correct me like.

    Me: "I see, you are using nginx as reverse proxy"
    Him: "durr, it's the only thing it does"
    Me: "..."
  • 2
    Meh. I'm sure he has shenanigans in his local machine to do all of this.

    I'm sure I can fucking probe his network and wreck some havoc.
  • 2
    @Nanos

    He's like, semi-freelance, as in, he works at a company that "rents" developers to other companies, if that makes sense.

    When he was with us, I requested the company to replace him with someone else.

    Wouldn't be surprised if that ends up being the case now.
  • 0
    @CoreFusionX I am still a newbie on this journey. Are these things I'll pick up on the way, or are there detours I must take ? If it's the latter, could you show me some road signs, please. I don't want to be called a clown in the future. Thank you🫡
  • 2
    @Omen

    Mostly it all comes down to fully understanding the tools you use, not just skimming the "getting started" section and calling it a day.

    (Part of) The work of a system administrator is making themselves obsolete.

    Therefore, you need not only ensure that you, say, provision a VM for an application.

    You also need to set up monitoring so you can know asap if something sketchy is going on, log aggregation so developers have observability, ensure certificates are setup and renewed accordingly, harden secrets against disclosure, accidental or purposeful.

    Know what happens if the VM suddenly reboots, etc.

    You will make blunders, like all of us have done before. Just be open about them and strive to improve. Trust is the most valuable asset a sysadmin has. If you lose it, your career is over.
  • 0
    @CoreFusionX Understood 🫡. Thank you
  • 0
    Feel obliged to say.

    It's been two weeks. He still hasn't realized what's wrong.

    And I'm not gonna tell him.
  • 0
    @CoreFusionX did you tell him yet? I’m pretty sure he still didn’t find it on his own.
Add Comment