• Valmond@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    5 months ago

    When you have a nice setup in programming (compiler, database, diverse docs, shells etc), you don’t want to shut all that down. If you can, good for you!

    • nickwitha_k (he/him)@lemmy.sdf.org
      link
      fedilink
      arrow-up
      3
      ·
      5 months ago

      My dev VM is almost entirely disposable. Could be up and running again, fresh in 30-60min, not counting time to pull the repo. Why use a local db server? Seems weird to me but, I came to development through SysAdmin and support stuff, so, was used to not owning the machine that I was on. That probably has heavily influenced my workflow.

      Out of curiosity, would you mind sharing a bit any the languages/frameworks and workflows that you are using? I’m mainly using Go, C++, Python, and a few others and just having trouble figuring out how I’d arrive at a situation like that. No CI/CD and test systems?

      • Valmond@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        5 months ago

        Well if I shut down visual studio, it takes some time to relaunch it, it uses a distant unix server to compile.

        I usually have a bunch of explorers open on distant repos for checking traces. Some soft connected to a database (with tables open), shells open on servers, or inside a docker on that server, all that goes away at reboot.

        Nothing crazy, it’s just convenient to just continue working instead of having to set it all up in the morning.

        CI/CD, thats for integration and should IMO be on a server somewhere 😁 not on your PC that you shut off in the evening!

        I do mostly C/C++, linux/windows. Database, gui, etc.