3 ms·
> Do you carefully review your own code? Do you have any resources for getting better at this? I don't get a lot of chances for other people to review what I w
by figgis 9y ago
> Do you carefully review your own code?
Do you have any resources for getting better at this? I don't get a lot of chances for other people to review what I write (yeah believe me I know..) and am looking into better ways to make sure I don't release shit.
I have a decent amount of testing automated for a majority of my projects but that's turning into an extra job on-top of my already demanding job.
- thesmallestcat 9y agoIt sounds like you're already doing a good job of trying to not ship garbage.
- tjalfi 9y agoHere are some of the techniques that I use for C, C++, and C#. Read every checkin twice before committing it. I find and fix many bugs by doing this. Keep a log of errors and problematic APIs. Periodically review your code for methods and idioms that you tend to misuse. I find it easier to spot one incorrect call to an API when looking at all uses of it. Enable all compiler warnings and use warnings as errors. It is easier to spot regressions when the build is normally silent. If a project has a noisy build then use the normal warning level and enable additional warnings over time.