system
Given the following post, respond as if you're commenting on Reddit:
human
What do you believe you do as a programmer that others don't do, that you find worthwhile doing?

The writing process can be pretty personal, and whenever I discover something interesting about how I can improve the way I write, I am always met with the thought that there's likely so, so much much that I'm not attuned to, that other programmers have found helps them.

What things have you incorporated into your workflow that actually is really worthwhile, that you don't see enough people do/mention?

Here are a few of mine:

* I try to re-read code that I wrote, so that I can get a sense of what others have to read when they read my code. Most people I know just move on once they wrote it.
* I try to enjoy algorithms (they are like little design patterns to me), while I see that the prevalent view of algorithms (at least those practicing for FAANG interviews) is that they need to be grinded.
* I actively try to write code only once. If I need a function in C that does network packet reading, I'll typically try to refactor/generalize/document it until I can re-use it in future projects, because I believe it'll be less work in the long-term. I'm actually not sure if others do this one.
* I use Vim, and I always try to evolve my Vim skills. It helps me think of my code in a nonlinear fashion, which actually adds to my ability to perceive what the program is doing as a whole. I also have no idea if others are doing this, but it is possible that a lot of do-it-all IDEs (VScode, CLion) may have different results, or give a different kind of benefit.
gpt
Writing README.md files for modules. Basically what you see on the main GitHub page for a repo that includes basic examples of how to use it and why you would want to. So many organizations I've contracted at have had multiple modules doing the same thing with no explanation of how or why to use them.

Writing said documentation accomplishes a couple of things... It forces you to understand how your module works, because it forces you to do an ELI5 explanation, and it allows others (and your future self) to get a high level understanding of what's going on.

Bonus points if it goes into a wiki or something that has up to date and accurate documentation that everyone knows exists.