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

help-circle

  • It Could Happen Here is often talking about what’s going on that week in the world. I wouldn’t try to listen to their whole backlog, but I usually catch an episode or two a week.

    Behind the Bastards is great. Since I found it (Summer 2020, I’d reckon), I’ve listened to most of what has come out since.

    Cool People who did Cool Stuff is a sort of spin off of btb. Deep dives on people and movements who were resisting the bastards. It’s only been going on a couple of years, so the backlog is more manageable if that’s your thing.

    I listen to Past Times on the Dollop feed most weeks. The Dollop is another deep dive history podcast. On Past Times, they read headlines and articles from different newspaper every week. Usually from the late 19th through early 20th century, but they’ve gone as far back as the 1600s.

    Anything by Jamie Loftus is great. She’s mostly done short run things on a single topic. She’s on the Bechdel cast, too which I listen to occasionally.

    You might enjoy The Deprogram, which has a less daunting backlog.


  • joby@programming.devtoAsklemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    68
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Before covid lockdown I made my living as a street performer, doing magic shows for crowds of strangers. In that very niche community, “Fat hats!” is a common farewell or replacement for “good luck”. In this case “hat” refers to the donations in the hat rather than the actual hat.

    Me in Jackson Square, New Orleans






  • I’m guessing you don’t mean commits that actually bring updates from a different branch in? I’m responsible for a bunch of commits that catch my feature branch up to main and a couple that bring my branches into main.

    If we were working on the same project, what would you want to see for those? This is hosted on a private gh repo, but it’s a small shop and we were working on a tight deadline for an MVP release and were not using PRs for the stuff I was working on.

    The boss (co-owner of the business) is the Sr dev on the project and until recently was the only sr dev in the whole shop. I actually don’t think he has experience with using git in a team context.

    One of my other tasks is working on internal docs (which didn’t exist before I joined the team) that would include git best practices for branching strategies and commit messages, so I’m interested in what folks who have more experience than I do would like to see as I try to nudge the team practices.


  • Git won’t let the second person push if their commit history doesn’t line up with the origin branch.

    It should be trivial to do a git pull --rebase to move your new commit after the upstream version, but as far as I can tell, no one on my current project remembers this (or perhaps they’re using gui tools or something). Our log is full of “merge origin/main onto main”.