• 1 Post
  • 165 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle






  • Good version control hygiene is important. My most recent job we were pretty good about commit messages for the PR, and then squashing that into a single commit when putting it on main. As you say, avoid unrelated things going together. You don’t want to have to revert a whole major feature because your “I’ll just fix it here” broke something.

    There’s a guy one of my old coworkers has been complaining about who never writes anything useful in his commit messages. It makes the git log useless and the code reviews harder.

    As for abstraction and such, sometimes it feels like it’s just coupling unrelated things together. It can be annoying when it’s like “I want to change this…and it’s used in 17 places for some reason. Guess I’ll check if all of those can handle this change, or this will be the one weird place that’s different…”

    I also worked with a guy that was a big fan of having two dozen one line functions. Monster functions are often bad, but a whole separate function like get_last_item(stuff): return stuff[-1] can be excessive.











  • If I was going to make something like this, it would have to incorporate trust chains. I don’t care if some maga-hat says this lady is horrible. I care if my good friend Alex says she’s horrible. One person’s “this person won’t shut up about communism” is a big red flag (no pun intended) but for someone else that’s the dream.

    When you sign up, you’d need to be referred to someone or be a root node. Anyone connected to you can be weighted differently. If some section of the tree is misbehaving, prune it.

    But that’s a lot of work