Keeping a debugging journal
steverydz.com
Keeping a debugging journal
1–10 of 29 posts
Re: Keeping a debugging journal
#2Can you share your debugging journal? I have been thinking about keeping one, just to try see if there are patterns amongst the bugs I inadvertently write. There are indeed patterns and classes and categories of bugs, and I think that knowing them might prevent me from making the same (stupid) mistakes in the future.
Re: Keeping a debugging journal
#3Can you share your debugging journal? I have been thinking about keeping one, just to try see if there are patterns amongst the bugs I inadvertently write. There are indeed patterns and classes and categories of bugs, and I think that knowing them might prevent me from making the same (stupid) mistakes in the future.
I just started it this afternoon but do intend to share it once it fills up a bit. I'll update the post when I do this.
Re: Keeping a debugging journal
#4I started keeping a development journal when I found myself getting interrupted quite a bit more than usual. It turned out to be very helpful but somewhat tedious to maintain at the level I would have liked.
I had some ideas about how to write software to automate some of the tedium and how great it would be if there were a large scale system that many developers used for tracking their work. If this system existed it could compare and contrast techniques and approaches used by more productive developers and help guide less productive developers down the path to improved productivity.
It seems like it would also provide a pretty good automatic Stack Overflow like experience in terms of being able to search for error messages and find the steps others had taken to solve the same problems.
Re: Keeping a debugging journal
#5I started keeping a development journal when I found myself getting interrupted quite a bit more than usual. It turned out to be very helpful but somewhat tedious to maintain at the level I would have liked. I had some ideas about how to write software to automate some of the tedium and how great it would be if there were a large scale system that many developers used for tracking their work. If this system existed i…
That sounds like a great idea!
Re: Keeping a debugging journal
#6[deleted]
Re: Keeping a debugging journal
#7I like this idea. Would anyone find interest in a mini-site for programmers to talk about how they've squashed bugs? Sort of a mini-social network I suppose.
Re: Keeping a debugging journal
#8I like this idea. Would anyone find interest in a mini-site for programmers to talk about how they've squashed bugs? Sort of a mini-social network I suppose.
I think that thing is called a quote bug-tracker unquote.
(ba dum tss)
Re: Keeping a debugging journal
#9I like this idea. Would anyone find interest in a mini-site for programmers to talk about how they've squashed bugs? Sort of a mini-social network I suppose.
StackOverflow contains a list of documented "bug fixes". and I bet most devs find their solutions on SO anyways.
I find this suggestion more valuable within a medium-large company. An old employer of mine had a "Trouble Call" reporting system where you submit a problem/solution and can search the DB later to help with repeat issues.
Re: Keeping a debugging journal
#10I've found it to be really helpful to keep a project work log when working alone. Mine are very verbose and help the most at the time of writing, since it keeps me on task and solidifies ideas.
My friend does the same thing, here's what he wrote about it recently: