An almost 30 Software Dev that enjoys gaming, woodworking, electronics and plenty of other hobbies. Too many hobbies.

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

help-circle















  • This is why you have style guides, policies and safeguards, with others checking PRs as they go through to catch this sort of stuff.

    Plus I’m not saying everything should be commented. By default things should be explainable through the code and making sure variable and method names are descriptive, along with strong typing if your language has it.

    Comments are there for when the code itself is not enough. But you’re right shit always creeps in eventually regardless of the best intentions. Which is why teams need tech debt breaks where no new features are added and they go through the code fixing the niggly things that haven’t been worth fixing whilst doing other features, and ensuring critical sections (the kind that usually have comments on them) are still working as intended and described accurately.

    This is from a senior dev in the industry.