Friday 6 April 2007

I'm living a geek dream: I've found a confirmed bug in Microsoft Visual Studio 2005.

Friday 6 April 2007 14:25:03 UTC
 Thursday 19 October 2006
I got into a conversation with a colleague about project management. I have sometimes found myself on a badly-managed project; so has he. As a matter of fact, he's just left one. He sent me this post-mortem, as an object lesson in using caution and listening to your gut when taking over a project already underway.
Thursday 19 October 2006 15:18:33 UTC
 Wednesday 11 October 2006
I had an interesting time today convincing a client that I had, indeed, fixed a defect, because the client kept getting an error message even though I wasn't. Once I got the client to send me a screen shot of the error message, I was able to fix it within two minutes. Any guesses why he got the message and I didn't?
Wednesday 11 October 2006 19:52:40 UTC
 Friday 12 May 2006
Here's some code I discovered while tracking a bug this morning.
Friday 12 May 2006 12:56:34 UTC
 Tuesday 11 April 2006

My project manager sent around this link to Joel Spolsky's rules for software management:

I've come up with my own, highly irresponsible, sloppy test to rate the quality of a software team. The great part about it is that it takes about 3 minutes. The neat thing about The Joel Test is that it's easy to get a quick yes or no to each question. You don't have to figure out lines-of-code-per-day or average-bugs-per-inflection-point.

I totally agree with Spolsky's list. I have never been on a project that scored better than 7 until now (which scores 9, IMO, but we're moving toward 11), and only one, ever, has answered "yes" to #8 (quiet working conditions).

Tuesday 11 April 2006 17:24:16 UTC
 Friday 7 April 2006

We spent two hours yesterday debugging some code that kept firing early. It wasn't clear to anyone, including the people who wrote it, why this happened. We patched it with the C# equivalent of duck tape, but really, it still doesn't work right.

This incident shows how important it is to know what your code is supposed to do, and not to accept the code if it doesn't. Many tools exist to help—most notably, unit-testing tools like NUnit—but they have trouble with the specific problem that we encountered: events fired from black-box controls.

I will have more to say about this later.

Friday 7 April 2006 12:10:56 UTC
Search
Navigation
Categories
On this page....
Archives
<October 2008>
SunMonTueWedThuFriSat
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678
Total Posts: 65
This Year: 1
This Month: 0
This Week: 0
Comments: 9
Blogroll
Contact me
Send mail to the author(s) E-mail RSS 2.0 Atom 1.0
Administration