I love this wild west phase of the Fediverse! Feels like the good ole days of the Internet. Onwards!

  • 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • I’ve done this every time I’ve looked for a job. If it’s the kind of company that would snoop on my browsing history and cause issues, it would just have motivated me to look harder 🙃

    I’m speaking from my 20+ years of experience in tech, so this advice might not apply anywhere, but I’ve found the fastest way to keep increasing your salary is to switch jobs every couple of years. I usually got bored of a job in a couple of years anyway, so this also helped prevent burnout. Additionally, switching jobs at leisure like this meant I could negotiate new salaries harder at the new place and didn’t need to try and change jobs during an economic downturn or a bad job market.

    Oh, and I’ve always regretted staying on in a company too long once I get the itch so I’d recommend starting a hunt as soon as you think a change might be good instead of waiting till you start hating your job!




  • Funnily enough, I block very liberally.

    I find that having the option to block by keywords, instances, communities and users let’s me curate my feed exactly as I want. What I wouldn’t want is for the blocks to be too broad of a brush (like in the users of instances example), which would lead to missing out on valuable conversations.






  • Anony Moose@lemmy.catoLemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    10 months ago

    I don’t have any particular complaints about the speed of Lemmy development or which features the devs are prioritizing or shutting down. Since there are two primary devs who are working on a pretty complex Rust codebase, it is going to take time for new contributors to understand it inside out as well as they do. The philosophy of a codebase is also very important for maintainers to guard, as just adding code or features without an overarching vision can lead to chaos.

    Having said that, I’m strongly in favour of multiple forks of the Lemmy backend bring developed. This allows new features, visions, optimizations, etc to be developed quickly and a lot of diverse opinions and philosophies to be entertained, exactly as we’re seeing with instances. Alternative UIs are another example of the benefits of this approach.

    This also allows Lemmy maintainers to see which changes are beneficial, and merge them back into the main codebase much more easily. For example, if a fork has 10x the performance with half the resource usage, it’ll be an easy sell to merge back in.

    Edit: typo
    Edit 2: shutting down, not shitting down 🤦