• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle
  • I interviewed for a shop in Ottawa.

    I was working at the time, but it was declining situation so I was Motivated.

    So I show up a the appointed time, and I meet a guy who can best be described as ‘a little grizzled’ and ‘a little stressed’. We go over my resume, first off the bat.

    “These are the things we need from you,” he said, tapping items on a list. “And these are places you suck,” he said, tapping the same list.

    I basically checked out at that point; there was no way I was suitable for this post. I could learn it, but it was a lot. And while I had a lot of other skills that showed up on the job desc and my CV, missing so many important pieces was insurmountable. It wasn’t a super-fun experience no matter how interesting he was - he was a great lead hand - and I left without much fanfare. Great rambling talk about all kinds of things, but it’s the worst I’ve ever flamed out in an interview; and the fastest.

    Imagine my surprise when he 'strong-hire’d me. I actually said to the recruiter, “Yeah, you’ve got it wrong. No no, and it’s totally okay, but you’re off by one or something. You mean to call the name above mine or the name below mine, and that guy is probably gonna love this job. But you don’t mean to call me. No stress, all good, but yeah, I’m not the guy you wanted to call.”

    It was a great job and that guy was my lead. Brutal honestly is fabulous if you can take it.







  • . I would not be surprised if this was just a Red Hat thing.

    It’s a tough one. We blame RedHat for a lot of its half-baked internal fridge art - systemd, network manager; and even, some days, yum in an apt-4-rpm world.

    But this new one is QUITE the departure. It’s not ‘red hat’ stupid but a little further on the spectrum.



  • While Jeff’s support for ELs has been imperfect - I marveled at the supply-chain issues gleefully baked into the drupal vagrant stuff - I came here to really say:

    IBM’s not really the poster-child for preserving the sanctity of source code in the past (cough cough Monterey cough), and I’m surprised they’re even suggesting everyone respect their own demands around that.


  • Docker has an additional issue, but not one unique to docker. Like flatpak, pip, composer, npm or even back to cpan and probably further, as a third-party source of installed software, it breaks single-source of truth when we want to examine the installed-state of applications on a given host.

    I’ve seen iso27002/12.2.1f, I’ve seen supply-chain management in action to massive benefit for uptime, changes, validation and rollback, and it’s simplified the work immensely.

        .1.3.6.1.2.1.25.6.3
    

    If anyone remembers dependency hell - which is always self-inflicted - then this should be Old Hat.

    HAVING SAID THAT, I’ve seen docker images loaded as the entire, sole running image, apparently over a razor-thin bmc-sized layer, on very small gear, to wondrous effect. But - and this is how VMware did it - a composed bare micro-image with Just Enough OS to load a single container on top, may not violate 27002 in that circumstance.