3 ms·
> Training young programmers to avoid non-issues may make them less productive. I’ve found that training good habits, pays off in spades. Once a technique bec
by ChrisMarshallNY 4y ago
> Training young programmers to avoid non-issues may make them less productive.
I’ve found that training good habits, pays off in spades.
Once a technique becomes habit, its overhead basically drops to 0.
May take bit to get there, but once it’s ingrained, it is cost-free.
An example is when I trained myself to switch from Whitesmiths indenting, to K&R indenting (when I switched from C++, to Swift).
It took a few weeks of discomfort, but it is totally ingrained, these days.
- swader999 4y agoWhy not just make your tool apply the indenting style? Then it's automatically baked into the team and project, no need for debates or merge issues.
- ChrisMarshallNY 4y agoSure, but I needed to do it, anyway. K&R has basically won the fight, so it's a no-brainer. Like I said, once I got in the habit, the overhead dropped to 0. Same for my code commenting and structuring, as well as many of the "little things" that I do, every day.
- wyldfire 4y agoIf your editor can do it, that's great. But another option is to apply it on commit [1]. [1] https://github.com/barisione/clang-format-hooks https://github.com/barisione/clang-format-hooks