Label Cloud

Thursday, December 30, 2004

New Resharper Changes

There is a new version of Resharper now available from the EAP site: http://www.jetbrains.net/confluence/display/ReSharper/Download

Revision 150 has the following :

  1. Extract Interface refactoring
  2. Extract Superclass refactoring
  3. Introduce Field refactoring
  4. Encapsulate Field refactoring
  5. Copy Type refactoring

From what I see the guys at JetBrains are planning to implement other features of IntelliJ, which is great.


Share/Save/Bookmark

Saturday, December 18, 2004

Bug Tracking Guidelines

This came from the previous link on bugtracking software, however, page states very important points about bug tracking. http://www.bug-tracking-guidelines.com/


Bug Tracking Guidelines - (by Randy Stimpson) Each bug report represents hours -- maybe even days -- of work. It's important company data, which should be well protected and well organized. Bug reports should be recorded in a database that is backed up on a daily basis. A bug tracking system, such as PR-Tracker, should manage that database. Here are some guidelines for effective bug tracking.
  1. Make a build of the software daily Bug tracking works best in an environment where there is a daily build. This enables testers to test the most recent version of software so that they aren't reporting bugs that have already been fixed. They are also discovering newly introduced bugs quicker while the code is still fresh in the mind of the developers that introduced them
  2. Use build numbers When applicable, build numbers should be used to specify what version of software a bug was found in, what version it was fixed in, and what version a fix was verified in. Revision numbers of source code modules modified to fix bugs are helpful notes for developers, but they aren't necessary or sufficient to coordinate work between test and development. Use build numbers instead.
  3. Use a process to handle bug reports Bug reports should go through a process that ensures that they aren't closed if they shouldn't be. Such a process should require that the person who reported the bug be the one to verify that it has been fixed or to approve any other type of resolution. The typical bug report life cycle would include the following status values: New, Assigned, Resolved, Verified and Closed, respectively.
  4. Use a resolution field To keep the bug report life cycle simple, use a resolution field to specify how problems are resolved. Possible resolutions include: Fixed, Won't Fix, Not Reproducible, Duplicate, By Design and External.
  5. Don't triage bug reports in meetings Avoid using a committee or meeting to triage bug reports. This will use a lot of man-hours that could be used fixing bugs. If the schedule dictates a triage, don't close bug reports in the meeting because this will circumvent the quality process by sidestepping testers that report bugs. Instead, use the bug triage to reprioritize, postpone, or resolve as won't fix.
  6. Handle feature requests separately Feature requests and specifications are often recorded as bug reports. These should be recorded separately so that they can be triaged, and so that they don't skew statistics for measuring software quality.
  7. Describe how to reproduce bugs A bug report should include a step-by-step description on how to reproduce the bug. This reduces the amount of time developers spend trying to reproduce the bug before they fix it. Finding the minimal steps to reproduce the bug will save even more developer time.

  8. Record how bugs are detected
    Keeping records on how bugs are detected helps you determine how best to spend your testing dollars. Suggested choices for a detection method field include: Interactive Testing, Test Script Execution, Test Script Design, Unit Testing, Integration Testing, Code Review, Beta Testing and Customer Report.

  9. Keep bug reporting simple
    Don't make bug reporting complicated by requiring entry of more data than is really necessary. If it's too much work to enter bugs into the tracking system, some bugs won't be entered, or people may start going around the system and begin reporting bugs by email or word-of-mouth.


Share/Save/Bookmark

Bug tracking Software

The blog entry is not really informative yet, however, this is the most comprehensive list of bugtracking software that I ever saw on one page.

I will definitely be looking at it at posting more comments.

Bug tracking Software: http://blogs.msdn.com/JoeStagner/archive/2004/12/18/325099.aspx

Gemini: http://www.countersoft.com has a few interesting points.
It is a .NET solution. SQL server backend. Free license for up to 10 users.


Share/Save/Bookmark

Thursday, November 25, 2004

Here's to changing the world...

Finally, the first step....

Not sure this will change the world, but hopefully will start a project that will be helpful. I've just uploaded an initial version of the C# Match project to SourceForge.net

C#Match - C# Pub/Sub Matching Engine. Support for multiple operators, XML subject line, efficient matching algorithm.

The project started as a pub/sub framework that I had to do for work. I was unable to find any available matching engines, and had to write my own. After a bit of research on the efficient matching techniques and a bit of development, C# Match was born.

I want to take the matching engine to the next level. Make it more generic, add multiple operator support (it now support only equality). When the project is a bit more stable.

I am always looking for people to help out, so if you can dedicate a bit of time to code, look at my code and make comments/sujestions, or even provide moral support and spread the word...


Share/Save/Bookmark

Wednesday, November 24, 2004

Coding Sanity: Reflector Diff

This sound pretty cool. Should be a great way to compare files. It would be great to add a command line functionality so it can be scripted with nant for example.

Coding Sanity: Reflector Diff


Share/Save/Bookmark

Wednesday, November 03, 2004

Popular agile software development sites

A pretty good list of Agile Programming related sites.

Popular agile software development sites


Share/Save/Bookmark

Sunday, October 03, 2004

The Code Project - Free Source Code and Tutorials

Code project is definetely a site that every developer should know. It does however keep track of a lot more then just code. Check out the section on Program Design and Methodologies


Share/Save/Bookmark

The Code Project - NPerf, A Performance Benchmark Framework for .Net - Design and Strategy

Performance Testing framework
The Code Project - NPerf, A Performance Benchmark Framework for .Net - Design and Strategy


Share/Save/Bookmark

Thursday, September 30, 2004

Steal This Book: The Free Way to be a C# Expert

A nice list of free book extracts. Steal This Book: The Free Way to be a C# Expert


Share/Save/Bookmark

Thursday, September 16, 2004

This is why I love technology

Currently I am sitting in my car in the middle of Manhattan waiting for my wife to come out of the office. A totally random situation, but what makes it different is that I am with my laptop and I am Blogging.
I started NetWork Stumbler and saw 7 access points, 2 of them unencrypted. 30 seconds changing my network settings and boom, I am on the Net.

I LOVE technology


Share/Save/Bookmark

Saturday, September 11, 2004

Server GC Misconceptions

If you ever wondered what are the diferences between different GC modes. This blog entry makes a pretty good explanation. Server GC Misconceptions


Share/Save/Bookmark

Tuesday, September 07, 2004

Ambient Orb

This Ambient Orb is definitely a thing to have. Awesome idea.


Share/Save/Bookmark

Thursday, August 26, 2004

Rick LaPlante on and the Team System in the next comunity preview

Did Rick just let something slip, or did he mean for this to be told out laud. Anyway, It seems that the next Visual Studio Community Preview will have a part of Team System in it. So expect to hear a lot mor ein the comming week as the word gets around. Summer time, summer time...


Share/Save/Bookmark

Sunday, August 22, 2004

Visual C++ 6.0 mainstream support will end on September 30, 2004

Visual C++ 6.0 mainstream supports ends in a little more then a month. Time to finish up that .NET conversion...


Share/Save/Bookmark

Monday, August 16, 2004

21 Rules of Thumb - How Microsoft develops its Software

The rules of thumb are pretty selfexplanetory. However, once you start reading them they make a lot of sence. 21 Rules of Thumb - How Microsoft develops its Software


Share/Save/Bookmark
Directory of Computers/Tech Blogs