Therapist = The Rapist
More like this:
Story from Firefishy
I have had many problems with my laptop. It just hit it’s two year birthday and decided to celebrate by cracking it’s case. Now, whenever pressure is put onto the case, the crack allows some components of the laptop to touch which then shorts out the board and causes the laptop to turn off.
So today a purchase was put through for a brand spanking new Dell Inspiron 6000. I upgraded the RAM to 1Gig, the hard drive is 80Gigs at 7,200 RPM and got the slightly better screen with the nice resolution over the one that comes standard. Only problem is 7-10 days until it arrives. I can’t wait!
***UPDATE***
After me bitching about the 7-10 days delivery time, I looked at my order status and it was shipped this morning. And believe me I did bitch.
G
Having become more involved in the Mozilla Foundation and working a big deal in the triage of the enormous amount of bugs in Bugzilla (over 310,000 at the moment), I have started to appreciate the work load that is present in this system. As an example, in the month of October I received 5,004 bug-related emails.
The Mozilla Foundation has kindly put together a document of bug-writing guidelines which is used by oh, maybe 1% of all the bug reporters in the world.
This bug report is a pleasure to read and you can understand the problem and how to reproduce it. But this bug report on the other hand is near impossible to understand, reproduce or do anything with it other than request the reporter to please add some more information. How do I reproduce it? What version of Thunderbird is causing the problem?
So this is a call out to all Bugzilla reporters in the world. Consider how difficult it can be to reproduce a certain bug. Give us as much information as possible - I spend more time on well thought out and well researched bug reports than the typical:
“Hey, Firefox doesn’t open my link. Fix! Thnx”
Please think about the people who have to work with the bugs you report!
I haven’t posted in a while as I have been writing some other articles for various sites in the last few weeks. I have a great article on DotNetNuke coming up which I discuss below. This is currently still in a draft form, but I hope to have it out the door by Thursday.
On another front, I had my first patch for Bugzilla accepted. It was very minor but it was my first patch that has been accepted. Which brings me onto my next batch was exciting news. After submitting the patch, I was looking for some more work to contribute to the project and decided to take on the task of supporting SQL Server in Bugzilla!
The code is currently being targeted (by myself) for a preliminary release for 3.0 of Bugzilla and in an unstable testing release for earlier builds. This is the bug if you are interested. The bug has been stagnant for a while and I know most of the developers don’t touch SQL Server as they are more used to MySQL and PostgreSQL so I thought it was a great opportunity. It is another language to learn but I take it on as a challenge! For the initial build, only SQL Server 2000 will be supported with 2005 support added at a later stage. This is simply because I have no idea about the differences and issues that might arise between the two versions.
This project ties in nicely with my Dotnetnuke article coming up as it nails down how simple it is with some foresight to enable developers to support multiple database platforms with minimal effort on your side. In the article I discuss how the data layer in DNN is designed, the inner workings and how using interfaces and some abstract code, multiple database support is easily achieved.
I will be writing an article on each tier of the DNN architecture to complete the series and then will move on to some other aspects of the platform.
Thats it for today - Some exciting things coming up in the next few weeks, so keep reading and keep learning!
