Don't write bugs
teamten.com
Don't write bugs
1–10 of 113 posts
Re: Don't write bugs
#2I thought there'd be something meatier than "don't write bugs" and "reread your code" but I was wrong.
Re: Don't write bugs
#3I wish the author had expanded more. It would have been great to hear about the most frequent types of bugs they logged and other mitigation strategies.
Re: Don't write bugs
#4Yeah sure, but what about when you need to add a new feature to an existing buggy code base? A lot of these articles assume you wrote all the code yourself from the ground up.
Re: Don't write bugs
#5At first glance this may sound like advice for a baseball player - “don’t strike out” - but that’s exactly what good players do - they work at identifying the things that get them to strike out and try to minimize them. Tony Gwynn spent hours reviewing tapes of his at bats.
Keeping a log of your mistakes and analyzing them is helpful in any number of things, including coding. Can you not write any bugs? Probably not. But you can certainly reduce the number, and it’s worth taking the time to do so.
The “read what you wrote” advice is good - look for and notice bugs early so they’re easy to fix. Basically be your own pair programmer.
Re: Don't write bugs
#6I wish the author had expanded more. It would have been great to hear about the most frequent types of bugs they logged and other mitigation strategies.
Follow the C link: https://www.teamten.com/lawrence/style/
Re: Don't write bugs
#7I thought there'd be something meatier than "don't write bugs" and "reread your code" but I was wrong.
I think the author put specific recommendations into their own sibling posts, accessible from this table of contents: https://www.teamten.com/lawrence/programming/
Re: Don't write bugs
#8> My Junior year of college I joined the programming team.
School and the software industry are different beasts. Once the pressure of "real life" kicks in, your brain starts to work differently, often trading some of that academic brilliance for other things you need to survive.
Ironically, I have seen some of the best code quality at places with crappy salaries. These companies are aware that they cannot compete with the bigger fish, so they are not as prone to squeeze their developers for that extra cent.
Re: Don't write bugs
#9A specific suggestion the author makes in a post related to the TFA:
> Everyone knows good programmers should plan
> for the future, should avoid boilerplate, should
> write elegant abstractions. Don’t. Those “good
> programmers” write heaps of garbage that get
> thrown away.Re: Don't write bugs
#10I know it's not very much in vogue these days, but this is exactly what the Personal Software Process is all about, but in a very structured and rigorous format backed by data.