Ask HN: Which tools have made you a much better programmer?

Re:Ask HN: Which tools have made you a much better programmer? by hinkley on Tuesday June 09, 2020 @01:37PM (#23468811)

If you consider processes as tools, there's one that I suggest to junior programmers bucking for responsibility/promotions.

Twenty minute cleanup. Nobody is really going to notice if you spent 5 hours or 5:20 on a task. As you're closing up and getting ready to push your changes, look if there's anything you can do to make it look or work nicer.

Eventually you start incorporating some of the lessons learned doing this into your implementations.

[ Parent | on HN ]

Re:Ask HN: Which tools have made you a much better programmer? by ayberk on Tuesday June 09, 2020 @01:44PM (#23468876)

+1 to this. I've developed the habit of reviewing my PRs before publishing them. When you assume the role of a reviewer, you end up catching a lot of little (and sometimes big!) stuff, reducing the total turnaround time.

[ Parent | on HN ]

Re:Ask HN: Which tools have made you a much better programmer? by tudorpavel on Tuesday June 09, 2020 @03:11PM (#23469734)

+1 to self code reviews, I almost always find stuff I've missed or could have done better.

[ Parent | on HN ]

Re:Ask HN: Which tools have made you a much better programmer? by kyleashipley on Tuesday June 09, 2020 @10:13PM (#23473174)

I often comment on my own PRs to explain alternatives or tradeoffs I considered. These aren't necessarily worth capturing in permanent documentation or TODOs, but can share knowledge or build confidence that I've considered various angles that might come up in a review.

I'll also call out places where I'm not happy with the implementation, looking for feedback, etc.

[ Parent | on HN ]