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

help-circle








  • Yeah you keep saying that, but that’s not really the argument being made. If you’d actually read all the text, you’d find the argument being made is that lawns are no longer environmentally sustainable, which is just true.

    Just because something was done 300 years ago doesn’t mean it’s ok to do now. And acknowledging that isn’t saying that things that are old are necessarily bad. It’s just recognizing that things change.


  • Ok but lawns have always been bad. Their whole original purpose was so rich people could flex their ability to leave some of their land useless. The whole point was for lawns to be useless. So like, the argument of “this is the way it was 300 years ago therefore it’s bad” is actually valid in this case. They were useless then, and they’re still useless now.


  • zalgotext@sh.itjust.workstosolarpunk memes@slrpnk.netOutdated
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    2 months ago

    Beds don’t have an adverse effect on our ecosystem like lawns do

    Also beds back then were made of straw and rope, maybe feathers if you were rich. Nowadays they’re made of a precision engineered combination of different types of foam and springs, all topped with self-cooling materials, placed on bases that can detect if you’re snoring and automatically adjust the mattress’s angle and softness to get you to stop. Beds are way fucking better than they were centuries ago. Yards are still useless wastes of space.




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