3 ms·
Granted, I'm a lone wolf (mostly) scientific programmer, not a commercial software developer. I look at a few things: 1. Keep an eye on how big or elaborate my
by analog31 8y ago
Granted, I'm a lone wolf (mostly) scientific programmer, not a commercial software developer. I look at a few things:
1. Keep an eye on how big or elaborate my programs get before I lose control of them, and have to either stop development, start from scratch, or massively refactor in order to know what the heck is going on. Being able to maintain a larger program, or participate in a larger project, without doing too much damage, seems like a reasonable informal metric.
2. Look at programs that I've written months or years ago and critique my own work. A year-old program should hopefully look better than a decade-old program.
3. Try to stay abreast of improved programming techniques, incorporate them in my work, and have faith that my programs will gradually improve.
I just realized these things are not about how good I am, but about the rate of change of my skills.