• 0 Posts
  • 368 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle

  • zalgotext@sh.itjust.workstoMemes@lemmy.mlVote!
    link
    fedilink
    arrow-up
    2
    ·
    13 days ago

    I feel like we’d see a lot more progress if these types of comments were higher up in the chain, instead of buried at the end of a conversation. I see a lot of ridiculing people for not knowing this stuff, a la: https://xkcd.com/1053/

    I understand it’s the ignorant masses’ responsibilities to educate themselves. But like, we could all stand to make it easier on one another instead of jumping down each other’s throats all the time.

    Also this isn’t directed at you in particular, just in general. I just liked your response, and I wish more people would give answers like this.






  • Is frequent rebasing something I should push for? A clean history is nice, but I’ve just won them over on feature branches… Is this something quick and easy that would improve our quality of life?

    Realistically, in the short term, no. If neither you nor any of your team members are familiar with rebasing or rebase-based workflows, you will encounter problems that no one will know how to solve without researching. That’ll lead to frustration, and before you know it those old school teammates that don’t get git will fall back into using svn, or zip files with names like final_project_v1.2_final_final (copy)

    I recommend getting familiar with rebase- and merge-based workflows on your own first, like on your own projects/private repos, and reading through the git documentation. Once you become more of an expert, you might be able to teach your teammates how to be proficient at using git, or at bare minimum, you’ll be able to help them unfuck themselves when they inevitably fuck their repos up.


  • Sounds like the onboarding process needs to have a step in it that says “here’s a link to a git tutorial, read this and get familiar with using git, as it’s an integral tool that you will use every single day on the job”. Bonus points for providing a sample repo that juniors can use to mess around with git, extra bonus points for including steps in the onboarding materials for the juniors to set up their own repos to play around with.


  • Yeah I’m definitely not a cryptography expert, but I’m more used to working with it in the “you need an authority to give relative meaning” use cases, not the “this signature came from that private key and that’s good enough” use cases. I feel like a lot of your examples rely on the “you need an authority to give relative meaning” use case though, and I can’t wrap my mind around a way to make that work in a way that that doesn’t largely negate the benefits you get from blockchain and it’s decentralization.