• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle






  • It’s not git that’s complicated. The work is complicated. git is just one of the tools that programmers use to manage the complexity.

    I also think that some people get too hung up on having a “clean” history, and trying to “fix” the history after it has already occurred. I usually have enough problems to worry about in the present, without also trying to worry about the past.


  • Yeah, I think that guy only got a superficial understanding of what Uncle Bob was saying.

    My policy as a tech lead is this: In an ideal world, you don’t need the comment because the names and the flow are good. But when you do need the comments, you usually really need those comments. Anything that’s surprising, unusual, or possibly difficult to understand gets comments. Because sometimes the world is not ideal, and we don’t have the time or energy to fully express our ideas clearly in code.

    My policy on SCM logs is that they should be geared more towards why this commit is going in, not what is being done. And what other tickets, stories, bugs it relates to.






  • I once worked at a place where they announced they were going to start evaluating performance reviews based on number of bugs closed. But the very devs who were responsible for closing the bug reports were also responsible for finding the bugs and opening the bug reports.

    That policy didn’t last very long.