• 0 Posts
  • 119 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle


  • All of these packaging systems have plenty of tutorials. Speaking from experience, many maintainers were not developers when they started maintaining packages for distros other than the official distros. I have worked with several maintainers who do work in tech and know socially several who had no background. This could be a great place for you to start!

    You bother because FOSS is as much paying it forward as it is getting shit for free.












  • I really struggle with the justification present in the article. “I need to emulate to do my job as an academic” is pretty hollow. “I want to emulate because I want to learn” is the real reason and, as an academic myself, I don’t feel like there’s a higher ground that gives me access to literally anything I want just because I want to learn.

    If the argument was “the copyright system is fucked and knowledge needs to be more open” I would be 100% behind that. I feel that way. I just don’t think someone should get to say “show me your secrets because I’ve arbitrarily decided to make my next publication about your secrets.”




  • I’m really confused. The article points out why Brave is a bad choice right after saying it’s a good choice, says that logical fallacies are a problem, moves immediately into why false equivalence is something to look out for in general, and ends. Why is does this mean Brave isn’t going to steal our info? Because Mozilla might too? How does that address any of the valid privacy concerns with Brave (eg forced affiliate links, a privacy violation) rather than social ones (eg Brandon Eich being a piece of shit)? Empathy is a tool to have a conversation with others who might have different values, not a lens to evaluate privacy or user experience.


  • My stance has been that, just as long as I’m interviewing with someone, I’m happy to do it, up to an undetermined time threshold. A screening interview, a tech screen, and then a bunch of panels is what I expect from a solid firm. Just as long as I’m interviewing with someone, I have a lot of opportunities to learn myself. I will also occasionally do a take home if and only if there’s a novel problem I want to solve related to that take home (eg I want to learn a library related to the task) but this is very rare.

    As a hiring manager, I try to keep things to a hiring screen, a tech screen, a team interview, and a culture interview. My team is small. I don’t want to spend more than three hours of someone’s time (partially because I can’t really afford to spend more than that myself per candidate or lose more team hours than that). My tech screens are related to the things I actually need people to do, not random problems you’ll never see.

    My assumption is that a good dev has lots of opportunity and I am in competition with everywhere else. I need to present the best possible candidate experience. Big companies with shitty employee experience telegraph that by presenting a shitty candidate experience, which is where the employee experience begins. You can’t have a good customer focus without starting from a good employee focus.