Lettuce eat lettuce

Always eat your greens!

  • 18 Posts
  • 775 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle







  • Straw man. I’m encountering sys admins and systems “engineers” who don’t know how to spec out a server, don’t understand how certificates work, don’t understand basic IP addressing principles, don’t understand basic networking topology.

    They just know how to click a list of specific buttons in a GUI for one specific Corpo vendor.

    Maybe that is fine for a Jr. Admin just starting out, but it isn’t what you want for the folks in charge of building, upgrading, and maintaining your company’s infrastructure.

    There’s nothing wrong with making interfaces simpler and easier to understand. And there’s nothing wrong with building simplified abstractions on top of your systems to gain efficiency. But this should not be done at the cost of actual deep understanding and functionality.

    The people you call when things go badly wrong will always be the folks that have that deep understanding and competency. It already has started hitting the developer community in the last few years. The Jr. Devs that did a 3 month boot camp where they learned nothing but how to parrot code and slap APIs together, are getting laid off and cannot find work.

    The devs that went to school for Comp Sci, that have years of real world experience, and actually understand the theory and the nuts and bolts of the underlying tech, they are still largely employed and have little trouble finding work.

    I think the same will happen soon in the IT world. Deep knowledge and years of dirty, greasy hands will always be desirable over a parrot that only knows how to click GUI buttons in a specific order.




  • Performance and how configurable things are, plus ease of use.

    For instance, my default router/modem device from my ISP was super clunky and confusing. I needed to set up some custom port forwarding and firewall rules. The aftermarket router I bought was faster, had way better wireless coverage, and the UI was so much easier to set up the configs I needed.

    So it’s up to you, from what you said, seems like you probably would be good with the default from your ISP.







  • In the last year I have switched to all cast iron, carbon steel, and stainless steel for all my pots and pans.

    No Teflon or “non-stick” coated garbage for me. Properly seasoned and cared for cast iron, carbon, or stainless steel will all be nearly as good as a “non-stick” pan and doesn’t have the risk factor.

    Recently, non-stick pans have been released that supposedly are safer, but I don’t really feel like trusting billion dollar corpos to not lie for the 20th time about that, not when there are fantastic alternatives.






  • I’ve heard that the DoD uses RHEL pretty extensively. RHEL in the US Military

    That article says that the US military has the largest single install base for RHEL in the world, but that was about 15 years ago, I don’t know if that’s still true.

    Apparently back then the US nuclear sub fleet and its sonar systems also ran on RHEL.

    I suspect lots of military hardware runs some form of *Nix or BSD type system. Many embedded systems run some *Nix type OS, and a huge portion of the developed world’s weaponry is smart, so it it full of low power embedded systems and custom SoCs.