January 28th, 2008 — career, work
Today is part three in the ongoing Too Many Bugs saga. You might want to check out part one and part two before reading on.
By eliminating the setup/config/curiosity class of bugs you should notice an immediate drop off in the amount of incoming bugs. It’s easy to file bugs on things that aren’t quite clear at first. By helping others get on board with what you’ve produced you’ve started setting expectations on where to test to get the most value out of the process. Continue reading →
January 24th, 2008 — career, work
This is part two of a paper I’ve written on making bug triage meetings more manageable and becoming a leader in a cross functional team. You might want to check out part one before reading on.
The reason we have bug triage sessions in the first place is no one has bothered to talk about these bugs before dealing with the entire list became a high priority. Everyone pays the high price of brutally long bug triage sessions because the low price of communicating on a consistent basis hasn’t been a priority right along. In order to make triage sessions more valuable you have to make it your top priority to get to the meeting with Continue reading →
January 23rd, 2008 — career, work
There is a time or two in every software engineer’s life when he experiences a deluge of open bug reports. I’ve seen times where there are ten new defect reports per day for two weeks straight against one module. At that point checking your “My Bugs” list in Bugzilla is a daunting task. You don’t want to see how far down the page scrolls. Worse, you don’t want to triage all those bugs; each one will take at least five minutes. Continue reading →
March 13th, 2007 — Java
After the popularity of my “How’d this String get into my List<Integer>?!” post I decided to follow up with a few small benchmarks. I got the idea from Geoffrey Wiseman who read my previous post and wondered about Generics performance. Continue reading →
March 12th, 2007 — Java
I was having a discussion with some co-workers at the No Fluff Just Stuff conference this weekend about Java and incorrect types getting put into generic collection classes. Generics were introduced in Java 5 in 2004 to add a compile time type safety to allow a type or method to perform operations on objects of various uniform or related types. The discussion we had focused on the fact that generics do not accomplish what the language specification says they will accomplish by allowing objects of a different type into a generic object. Continue reading →
