• 8 Posts
  • 1.8K Comments
Joined 2 years ago
cake
Cake day: January 3rd, 2024

help-circle





  • You can make an image of the / drive so it’s easier to restore if they break the system.

    That’s good advice. I always meant to do that with computers my kids access.

    Although I haven’t ever had my kids break a Linux Mint install. I set them up as non-sudo users and that was enough.

    Of course, they grew older and have sudo now, so I should actually think about taking a drive image, now.








  • Oh, nice.

    I’m always looking for another ChangeLog tool.

    That said, I never leave my ChamgeLogs up to automation.

    My git logs are open to my users for full details, but my ChangeLogs are how I communicate which changes my users probably need to be aware of.

    So far, this hasn’t yielded well to automation. But my team is still considering standardizing our commit log messages enough to allow it someday.






  • I’m mainly interested in making code reviews a little easier to manage.

    One thing I haven’t seen mentioned yet, here: All future diffs become much easier to read if the team agrees to use a very strict lint tool.

    I know, I know. “Code changes should be small.” I’ve already voiced that to my team, yet here we are.

    I understand from another Lemmy thread that the tradition is to toss the offending team members’ laptop into the nearest large body of water.