• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle
  • A “server” is just a remote computer “serving” you stuff, after all. Although, if you have stuff you would have trouble setting up again from scratch, I’d recommend you look into making at least these parts of your setup repeatable, be it something fancy ala Ansible, or even just a couple of bash scripts to install the correct packages and backing up your configs.

    Once you’re in this mindset and take this approach by default, changing machines becomes a lot less daunting in general. A new personal machine takes me about an hour to setup, preparing the USB included.

    If it’s stuff you don’t care about losing, ignore everything I just said. But if you do care about it, I’d slowly start by giving from the most to least critical parts. There’s no better time to do it than when things are working well haha!


  • Tramp is more featured, but if all one cares about is being able to edit remote files using a local editor, vim can edit remote files with scp too: scp://user@server[:port]//remote/file.txt

    I tried tramp-mode at some point, but I seem to remember some gotchas with LSP and pretty bleh latency, which didn’t make it all that useful to me… But I admittedly didn’t spend much time in emacs land.


  • 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.







  • 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?


  • we don’t need managers we need people helping us getting the tools we need and trust that what we do

    The word “manager” is extremely overloaded and barely says anything about what that person does for its team without knowing how the company operates. Where I work, the person you’re describing would be someone in technical management.




  • Honestly, it’s just another shell. Both Bash and ZSH happen to be mostly POSIX compliant, so stuff that works for Bash tends to work with ZSH too. For me it’s mostly just about the stuff I can add to it - I use the antidote plugin manager to get additional autocomplete, syntax highlighting, suggestions, async prompt updates, that kind of thing.





  • folkrav@lemmy.catolinuxmemes@lemmy.worldIt do be like that
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    4 months ago

    Some people do overestimate how much of the software they’re actually using, and how far back some features go. I learned the little PS I know using a 7.0 license my father bought, I used it for years doing 2D graphics and web “design”, and still basically still have the same workflow with minor differences to avoid destructive changes.