5 ms·
Other. Write code without bugs. (I say this in jest, but only a little.) Think about it... I know so many programmers who get lazy because they have such good
by edw519 13y ago
Other. Write code without bugs.
(I say this in jest, but only a little.) Think about it...
I know so many programmers who get lazy because they have such good debugging tools (Let me just slam something out there and let the debugger catch it.) I hate this.
If we developers would slow down and think a little more about what we're building, we may find a dramatically decreased need for debugging.
Variable local or global? Right variable name? Should that be a function? How much am I repeating myself? How should the data be structured for its intended uses? What's the best way to handle recursion? Where might memory leak? Where's the best place to do this? Which is the best technology for this need? And most of all: Will the next programmer be able to read this and tell what it's doing before they break it?
Slow down. Plan more. Think deeper. Debug less.
- deleted 13y ago[deleted]
- nilkn 13y agoBug trackers are more fully featured project management tools these days. We use Fog Bugz and some of our non-coders are using it to record what they're working on/accomplishing.
- serichsen 13y agoI agree, but this still will not make a bug tracker superfluous---if only for tracking change requests.
- beaumartinez 13y agoBugs are inevitable. No matter how much you think about the problem, there will always be things that slip between the cracks.
- pcowans 13y agoThis is true, but you should probably still put more emphasis on avoiding them than optimising your process for fixing them.
- clubhi 13y agoBugs often represent mistakes and miscommunication in areas that the programmer has no input in. If the goal of the project was to draw a circle there is still room for error. The PM might have wanted a red circle with a fade in render.
- gnosis 13y ago"Slow down"? Please try to convince the typical manager, executive, or VC that calls the shots to slow down. Death marches by overworked, sleep deprived, and understaffed development teams are the norm in the industry. It's a wonder that most products aren't even more bug-riddled than they already are. I would love to live in a world where every developer was competent if not brilliant, and had all the time, training, and motivation in the world to write nothing but perfect code at his leisure. If you know of a way to this world, I'm all ears.
- Rexxar 13y agoDid you misread "debugger" instead of "bug tracker"? Your comment doesn't make any sense to me in the current context. If you are really against "bug tracker". I don't really understand as they are often mainly used to report new needs, requirement and enhancement rather than crash due to poor coding practices.
- quadrangle 13y agoThis is fine advice. Had the OP thought it through, they would have made this thread about "ticket tracker" or "issue tracker" and then your comments about debugging would be more obviously non sequitur.