• BoppityBoop@lemmy.mlEnglish
    40·
    23 days ago

    10 years ago this meme said “compiling” shows how much docker has made things more “efficient”

    • HurlingDurling@lemm.eeEnglish
      61·
      23 days ago

      Tbh, all of web development has become this… efficient. I remember the days where I could create a website in PHP and have it done in a couple of hours (per page), and now the only way I can do that would be using AI and going full on “vibe coding” mode.

      • porous_grey_matter@lemmy.ml
        1·
        23 days ago

        What do you mean? You can just make some react/typescript template and fastapi server thing, or any of dozens of equivalents, extremely quickly. I’m by no means an expert on web stuff as I develop software for controlling machines, but we used the above for some internal services in my last job and I could get a clean and functional site running in a day with no prior experience. I get that for public facing stuff you’ll have some higher requirements but I couldn’t imagine those wouldn’t apply just because you’re coding in PHP…

        • HurlingDurling@lemm.eeEnglish
          1·
          22 days ago

          It’s all the extra requirements, all the extra engineering that needs to be added that is IMO ruining web applications. Sure, they have huge benefits, but I hate when the application is simple but the backend is so overly engineered that it takes a week to completely build a fully fleshed out application. You have to organize your components, add styled-components.js, make sure it’s compatible with mui.js, create test cases for each component, setup a DB and integrate it to hold all copy as well as any input from the customer, make sure that it’s accessible (this part I admit that it’s important), make sure your test cases always pass, setup routing tables, add analytics, add pixel campaign api, squash git conflicts, integrate some other weirdo apis that marketing and leadership pulled from some obscure service no one has ever heard off, debug some weird edge case error caused by a node dependency 3 levels down, present the finished website to leadership only to be destroyed and now you have to redo 75% of the site with leadership changes… rinse and repeat.

          It’s a good thing I fucking love my job 🙃

  • phantomwise@lemmy.mlEnglish
    2·
    23 days ago

    I was going to watch a tuto on how to be more efficient but YouTube is still buffering

      • davel@lemmy.mlEnglish
        15·
        23 days ago

        True. Nothing beats running your unit tests in the actual container image that will be run in production.

        • HiddenLayer555@lemmy.mlEnglish
          7·
          23 days ago

          Race condition that only happens on the much faster production hardware: Allow me to introduce myself

          • davel@lemmy.mlEnglish
            5·
            23 days ago

            Unit tests can’t win ’em all. That’s where things like integration tests, staging environments, and load testing come in.

            The final layer of protection is the deployment strategy, be it rolling, canary, or blue-geen.

          • Qaz@lemmy.mlEnglish
            2·
            23 days ago

            Or an issue that only appears when using ARM and not on my AMD64 dev machine

        • qaz@lemmy.worldEnglish
          6·
          23 days ago

          Yeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.

      • wpb@lemmy.world
        2·
        23 days ago

        At my previous job, we had a “Devops” team. We even outsourced some ops to a third party in the worst possible way (I’m talking “oh you want to set up an alert for something related to your service? Send us an email and we’ll look into it” and so on). All the pre-devops pain magnified by an order of magnitude. Sometimes devs would do their own ops (I know, big shock!), and they would call it “shadow devops”. Nearly fell off my chair when I first heard it. Kinda glad I’m not with them anymore.

    • beeng@discuss.tchncs.de
      51·
      23 days ago

      Devops isn’t a role.

      Platform Engineer maybe, but even then I’d say they were “developing” the platform.