Neat document from ALM Rangers

September 9, 2011 Leave a comment

Interesting (but long) read on requirements management written by MS and some sample document templates.

A lot of it is capturing way more information than Lancaster Labs is, but it’s still nice to see another company’s process. I thought the section on traceability was good and liked their definitions for the various requirement types. They also provide detail on how Team Foundation Server lets them store all of this information electronically, so you don’t need to wade through stacks of paper to find the info you’re looking for.


Nice comparison of requirements, use cases, and user stories

July 29, 2011 Leave a comment

I found this on Scrum Alliance. It makes a sometimes difficult topic very clear.

Neat use of HTML5

July 28, 2011 Leave a comment

Windows 8

Mary-Jo Foley reports that Windows 8 ARM won’t run legacy applications, and Windows 8 x86/x64 will run legacy apps through a “Windows 7 Mode”.


James also told shareholder meeting participants, as The Register reported, that there will be two classes of Windows 8 PCs: Ones running x86/x64 chips that will be able to run legacy applications, and ones running ARM processors that will not. The x86/x64 version will include a Windows 7 mode, she said, that will enable this legacy-app support

This could mean great things for “Windows 8 approved” applications, as MS could pull out a lot of the legacy support in Windows. There are things in the win32 API that have been there since Windows NT 3.1 way back in 1993. Pulling those out could make startup, shutdown, application loading, and general UI responsiveness much faster. Of course, this requires developers to get on board with making their apps “Windows 8 ready”, but I don’t think that will be a problem for most of them. And if they’re made available in the rumored Windows App Store, then users will have an easy time finding them. I wonder if MS will require the rumored “AppX” framework to be used, or if any old win32 app can be upgraded.

Case sensitivity in code

May 17, 2011 1 comment

Another thing that VB has spoiled me with is its case-insensitivity. I’m working on a small project in C# and I’ve had to retype almost every method call because I never hit the shift key. Is there a real argument to having a case-sensitive language? Do I really want to be able to have two different objects called object1 and Object1? Talk about confusing!

I think VB has an undeserved bad reputation.

Dabbling in C#

May 14, 2011 3 comments

So I’ve been strictly VB since starting at Lancaster Labs five years ago. Some of that must have worn off because I’m finding C# a little odd. What’s up with the code needed to wire up an event? VB is definitely easier for this.



Public Event SomeEvent(sender as Object, e as EventArgs)

Public Sub DoSomething()

RaiseEvent SomeEvent(Me, EventArgs.Empty)

End Sub



public event SomeEvent(Object sender, EventArgs e);

public void DoSomething()




private void OnSomeEvent()


if (SomeEvent != null)

SomeEvent(this, EventArgs.Empty);



Same result in the end, but which is more readable? I think the VB.

So that’s how it works…

Just read a nice blog entry by Joel Spolsky on character encoding.