Have you ever wished your code would just tell you how to fix it?
Perhaps in the future, they'll have debugging AI's that could talk to you and tell you just what your doing wrong with your code. Then again, witty programmers just might make them come up with new ways to declare your stupidity to the world every time you crash your program.
Well since it's still the bug-ridden present, I've been spending time, doing what programmers do the most: debugging.
Mostly integrating a debugging log, sensible exception catching, and editing out possible fault-points within my code. Of course, it all started out with just trying to figure out this one bug, but now that I've past that one, with a few new bugs, I'm exercising more caution to catch them before they can add to my woes.
Just thinking about all these preemptive safety measures, makes me wonder if I should also do some kind of exercises so I don't get carpul tunnel...*crack*...
or slow it down at least.
release version 0.3?.? (I'm not sure what to number a release made with just easy-to-read code and nice debugging messages.)
Custicon@andrew.raynier
hotel sarimbit garut
8 years ago
1 comment:
Hello. This post is likeable, and your blog is very interesting, congratulations :-). I will add in my blogroll =). If possible gives a last there on my blog, it is about the Impressora e Multifuncional, I hope you enjoy. The address is http://impressora-multifuncional.blogspot.com. A hug.
Post a Comment