• 0 Posts
  • 164 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle



  • Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

    If your software is following semver, not necessarily. It only requires a major version bump if a change is breaking backwards compatibility. You can have very big minor releases and tiny major releases.

    there was more time for people to run pre-release versions if they are adventurous and thus there is better testing

    Again, by experience, this is assuming a lot.


  • From experience shipping releases, “bigger updates” and “more tested” are more or less antithetical. The testing surface area tends to grow exponentially with the amount of features you ship with a given release, to the point I tend to see small, regular releases, as a better sign of stability.


  • folkrav@lemmy.catoLinux@lemmy.mlOptimize your shell experience
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    4 months ago

    I do connect to VMs and containers all the time, I just don’t see a reason not to speed myself up on my own machines because of it. To me, the downside of typing an alias on a machine that doesn’t have it once in a while, is much less than having to type everything out or searching my shell history for longer commands every single time. My shell configs are in a dotfiles repo I can clone to new personal/work machines easily, and I have an alias to rsync some key parts to VMs if needed. Containers, I just always assume I don’t have access to anything but builtins. I guess if you don’t do the majority of your work on a local shell, it may indeed not be worth it.


  • folkrav@lemmy.catoLinux@lemmy.mlOptimize your shell experience
    link
    fedilink
    arrow-up
    18
    arrow-down
    3
    ·
    edit-2
    4 months ago

    I’d rather optimize for the 99% case, which is me getting shit done on my machine, than refuse to use convenient stuff for the sake of maybe not forgetting a command I can perfectly just look up if I do legitimately happen to forget about it. If I’m on a remote, I already don’t have access to all my usual software anyway, what’s a couple more aliases? To me this sounds like purposefully deciding to slow yourself down cutting paper with a knife all the time cause you may not have access to scissors when you happen to sit at someone else’s desk.








  • I too had those hour long snoozefests where 99% of what’s said doesn’t pertain to my work, and those useless meetings that could have been a message on a Slack channel. I still feel like the sentiment is a very broad generalization based on some assumptions that may or may not apply well to every work environment.

    My most recent project has direct dependencies between 5 teams just on the developer side, and multiple internal and external clients. Figuring out if we need to reach out to the stakeholders or figuring out who can help them on a particular task isn’t necessarily always that straightforward, depending on scope.

    Anecdotally, the devs on my team were losing a lot of their time doing all that stuff before I joined as a tech lead in August. I spend most of my non-dev time (about 50% of my time, lately) shielding the rest of the team from stakeholders, pushing back when needed, pushing back on various demands, enabling communication lines, all to protect them from context switching and let them code.

    And honestly… Outside all that, agreeing with me or not, is 15 minutes of human interaction that terrible lol?



  • Ardour is indeed pretty good. I’m a Reaper guy, which is incidentally available on Linux as well nowadays, so on the DAW and audio interface front, I’m all covered. If anything, my older 2i4 runs slightly more stable over Linux/Pipewire than it does on Windows with the official driver. I’m more on the composition/production side of things (amateur, although I do have a very small amount of professional experience), it’s mostly the amp sim and virtual instruments landscapes that left me on my appetite a bit last time I tried. There just weren’t many option and they all frankly sounded like crap. Maybe that got better since then, I don’t know hehe.





  • The newest Teams app (and I think newest Outlook amongst others) is using system/Edge provided WebViews rather than Electron, which I guess takes care of the “each app gets its own Chrome instance” part of the Electron bloat. It’s so far running better than old Teams for me. On my old work laptop, the fans spun up the second the old Teams client launched lol