Aaron Jensen

Simple site sanity testing with Cassini and friends

aaronjensen — Mon, 23 Nov 2009 00:11:00 GMT

Recently I wanted to add a very simple sanity check to our sites’ build. Typically the Integration/Selenium RC tests would handle this sort of thing, but I wanted something light enough to go in continuous integration build so we would be protected from simple dll version mishaps, configuration errors, container issues, whatever. There’s probably plenty of ways to do this, and if any of you know of a better way, please let me know. In order to do it, I modified the Cassini source to run as more of a daemon, I created a simple rakefile to launch it and I use curl to verify a test url. For my test Url I simply made a Diagnostics Controller with an Ok action that returns a ContentResponse with “OK”. Pretty simple. If you need something like this, give it a shot and let me know what you think.

Download

Source

MSpec latest build download now available

aaronjensen — Thu, 19 Nov 2009 18:30:00 GMT

Update: Here's a direct link to download the latest build of MSpec.

Many thanks again to Alexander Groß for adding packaging to MSpec. You can now download builds from here without having to build it yourself! Just grab the Artifact from the latest build.

Call for help with MSpec

aaronjensen — Thu, 19 Nov 2009 06:51:25 GMT

Thankfully, the community has created a number of very helpful blog posts about MSpec. Unfortunately, I’ve been quite bad at aggregating them into a single authoritative source and documenting the few but somewhat obscure APIs and tools that make up MSpec. It is on my list of things to do but time has been rather… tight. I’d love to get it up sooner than later, as MSpec is getting more and more eyes on it and I want to make things as smooth as possible for new users.

That’s where this plea comes in, I’m looking for someone to help put together some documentation in one place, probably the github README.markdown. I obviously don’t have anything to offer other than fame and fortune (minus the fortune and probably the fame). Rest assured, though, that myself and the rest of the community (like kreiggers) would be forever grateful.

I’d be happy to edit and keep up to date the documentation once created so this wouldn’t be an ongoing effort, but I could use some help getting started. Ping me on twitter if you’re interested and we can brainstorm a bit. Thanks in advance and sorry for the spam.

MSpec v0.3

aaronjensen — Wed, 18 Nov 2009 18:20:00 GMT

IMPORTANT NOTE: This is beta (still). The assertion library is new and may have bugs. I’d appreciate you testing it on your specs, but don’t fight specs breaking too hard if they do, let me know what happened and revert, I wouldn’t want to cost you your day chasing down a bug in MSpec. Thanks!

It’s been more or less forever since I’ve incremented the version number of MSpec so I went ahead and did it today. This is just a brief post to let you know what’s new and what I broke—maybe I’ll post some more detail later.

MOST IMPORTANT NOTE: v0.3 removes the dependency on NUnit/XUnit. If you’re upgrading, delete your Machine.Specifications.NUnit.dll and Machine.Specifications.XUnit.dll and remove their references from your projects. MSpec has an all new assertion library (with a bit of borrowed code from XUnit, turns out equality is hard).

I’ve attempted to format the new error messages to minimize debugging, so they’re rather verbose. Please let me know if they are too verbose or if there’s anything else you’d like to see.

You may need to tweak a few specs (ex. ShouldEquals is now generic, so you have to pass it the same type as the thing you’re observing) but most things should “just work”. Let me know if any of the new assertions give pain.

I also added a XCopy Deployable Test Runner manifest for TD.NET so no more fiddling with the registry or dealing with version issues. Pretty slick really. Thanks Jamie for pointing this out to me.

Of course there are plenty of other changes from 0.2 to 0.3 since it’s been like, a year. Here’s some others off the top of my head:

R# runners for 4.0, 4.1, 4.5 and 5.0 and they’re better than ever thanks to Alexander Groß.
Xml output from the command line runner with --xml for CC.NET/Hudson thanks to Barry Woods.
Concern is now Subject
There is no longer a difference between “Establish context” and “Establish context_once”, the context is always established only once. The idea is that observations are observations, they should not mutate state so there is no reason to execute the context more than once. Same for cleanup. If you *really* want to do execute the context for each specification, first try to change your mind, then if you still want it use: [SetupForEachSpecification] on your context class.
You can implement an IAssemblyContext in your spec assembly to set things up before or clean things up after all of your specs in that assembly have run.
You can implement a ICleanupAfterEveryContextInAssembly to perform cleanup after every context (think cleaning up static state, resetting your ServerClock/DateTime replacement for example.
Selenium RC support

Many thanks again to Alexander Groß for adding packaging to MSpec. You can now download builds from herewithout having to build it yourself! Just grab the Artifact from the latest build.

And, as always, the best way to get me is on twitter.

Machine.Migrations changes

aaronjensen — Sat, 24 Oct 2009 21:56:00 GMT

Jacob first introduced Machine.Migrations over a year ago. Since then, it's been a solid part of our process and we're up to nearly 500 migrations with it on one project.

Recently, I finally got around to making some changes I've been wanting to make and I wanted to call'em out:

We split the repostiory out to its own on github. I did this similar to the way I did it for MSpec some time ago. Again, the advantage here is that change logs are localized to the project rather than the entire machine overarching project.
I added complaints if you have multiple migrations with the same number. This silently caused problems before as one of the migrations would not get applied. Now it just yells and dies like a good app. Of course, this is not as important because of the next change.

Next I added support for timestamped migrations. This helps immensely on active projects with multiple developers. You don't have to deal with communicating migration numbers to the team when you add them, you just generate a new one and merge it when you feel like it. We actually had half of our topic on Campfire dedicated to our current migration number. The other half was who owed how many pushups for breaking the build.

Here's the rake task we use to generate a new migration:

namespace :new do
  task :migration do
    raise "usage: rake new:migration name=\"Your migration name\"" unless ENV.include?('name')

    name = ENV['name']

    filepath = "db/migrate/#{Time.now.strftime('%Y%m%d%H%M%S')}_#{name.gsub(/ /,'_')}.cs"

    text = File.read("db/migrate/template.cs")
    File.open(filepath, 'w') { |file|
      file.puts text.gsub(/\$MigrationName\$/,"#{name.gsub(/ /,'_')}")
    }
  end
end

Usage is simple, just create a template.cs in the directory (we use db/migrate) and then type

rake new:migration name="this is my migration name"

Example template:

using System;
using System.Collections.Generic;
using System.Text;
using Machine.Migrations;

public class $MigrationName$ : SimpleMigration
{
  public override void Up()
  {
    throw new System.NotImplementedException();
  }

  public override void Down()
  {
    throw new System.NotImplementedException();
  }
}

Finally, I added a command line runner. As we've grown more and more sick of msbuild and more and more fond of rake, we've wanted to slowly all but eliminate our dependency on MSBuild. The command line tool is quite simple:

Machine.Migrations
Copyright (C) 2007, 2008, 2009 Machine Project

  c, connection-string  Required. The connection string to the database to migrate
  t, to                 Applies or unapplies migrations to get to the specified migration
  u, up                 Applies migrations to the latest
  s, scope              The scope?
  d, directory          Required. Directory containing the migrations
  v, compiler-version   Version of the compiler to use
  debug                 Show Diagnostics
  r, references         Assemblies to reference while building migrations separated by commas
  t, timeout            Default command timeout for migrations
  ?, help               Display this help screen

The only two flags you usually need are -c and -d. Just pass in the connection string and the location of your migrations. Be sure to quote them: migrate.exe -c "my connection string" -d "my migration directory".

Hopefully these changes help others. Grab the latest here and just msbuild the sln to build it.

I do wonder though, what other active .NET migration projects are people using and how do you like them?

Building an iPhone app

aaronjensen — Wed, 21 Oct 2009 20:12:00 GMT

Today we launched PicTranslator, a free Picture Translator for the iPhone. Building it was quite an adventure. I wanted to share some of the technologies we used, you may be surprised.

On the iPhone:

iPhone SDK: This one's obvious. Unfortunately, MonoTouch wasn't out when we started to develop. It looks rather promising.
To be perfectly honest though, Objective-C is pretty cool. Especially once you figure out it's memory management scheme. It's kind of fun to be back in pointer land again. Brings back fond memories. Oh, and though I did miss vim, xcode is a pretty darn good little editor.
json-framework: This is a pretty slick JSON parser for the iPhone. Hand parsing JSON in obj-C would not have been fun. This made it easy. I'm pretty sure I followed this tutorial to get it up and running.
ASIHttpRequest: Nice Http framework, helpful for doing asynchronous requests and sending and receing files easily.
We also used a few random snippets found around the web. Here's one on rounded corners. Also stackoverflow was invaluable.

On the server:

nServiceBus: NSB is fantastic. It allows us to scale to any size machine or any number of machines. I'm realizing more and more than most reasonable size applications should leverage messaging in one way or another. We're using MSMQ as the transport.
ASP.NET MVC: My web framework of choice.
MSpec: Gotta test it somehow right, why not use my own framework.
Topshelf: Best way I know of to create services in .NET. Makes it easy to run as a console app or a service. Love it.
log4net: Another no brainer. log4net is how you log in .NET. Well, most of you any ways :).

Not a bad stack, eh? Any surprises? Oh, and if you have an iPhone, be sure to give PicTranslator a shot, we'd love your feedback.

Advanced Selenium RC logging with MSpec

aaronjensen — Tue, 20 Oct 2009 01:30:00 GMT

Today I pushed some new features to MSpec to allow you to see this in MSpec’s html report when you get Selenium RC failures:

This is very similar to ruby’s selenium client’s rspec report. You can see a real example of that here.

So how do you get this? It’s pretty easy. All you need to do is grab and build the latest MSpec, add a reference to Machine.Specifications.SeleniumSupport.dll and add a class like the following to your assembly that contains your selenium specs in it:

  public class SeleniumSupport : SeleniumResultSupplementer
  {
    protected override string ImagesPath
    {
      get { return GetTempPath(); }
    }

    protected override DefaultSelenium Selenium
    {
      get { return ...; } // Replace with the DefaultSelenium in use 
                          // by the current running spec
    }

    static string tempPath;

    private static string GetTempPath()
    {
      if (string.IsNullOrEmpty(tempPath))
      {
        tempPath = Path.Combine(Path.GetTempPath(), "selenium");

        if (Directory.Exists(tempPath))
        {
          Directory.Delete(tempPath, true);
        }

        Directory.CreateDirectory(tempPath);
      }

      return tempPath;
    }
  }

That's pretty much it. Like I said, this is brand new, just got it up today so please let me know if you have any problems with it. You can do so on twitter or the machine google group. Enjoy!

A recent conversation about MSpec practices

aaronjensen — Mon, 05 Oct 2009 21:12:00 GMT

Recently I've heard about more and more people checking out MSpec. A few days ago I got an email from a friend. He said he was having trouble with base class explosion while creating specs. Here is a snippet from his code:

public abstract class with_null_program
{
  protected static Program program;
}

public abstract class with_program_and_empty_args : with_null_program
{
  Establish context = () => program = new Program(new string[]{});
}

public abstract class with_list_command
{

}

[Subject("Program")]
public class when_creating : with_program_and_empty_args
{
  private Because of = () => program = new Program(new string[] {});

  It should_output_to_the_console =()=> 
   program.Out.ShouldEqual(Console.Out);
}

[Subject("Program")]
public class when_running_with_no_arguments : with_null_program
{
  private static StringBuilder outputBuilder;

  private Because of = () =>
  {
    outputBuilder = new StringBuilder();
    program = new Program(new string[] {}) {Out = new StringWriter(outputBuilder)};
    program.Run();
  };

  It should_print_usage =()=> outputBuilder.ToString().ShouldContain("USAGE");
}

[Subject("Program")]
public class when_running_without_database_args : with_list_command
{

}

And here's my response:

Hey man, Glad to see you playing with MSpec. Definitely curious to get your feedback on the experience.

So there's a few things I noticed about the specs. For one, you're using the with_ pattern. I know I or Scott or someone started this... but I don't like it now. I much more prefer to just have a base class that contains any utility/meaningless cruft my specs have. You also seem to have taken this to a bit of an extreme. Would you make a regular base class just to create a single instance variable and set it to null in the constructor? Probably not. Same stuff applies here. There's no value in creating base classes unless they provide value. There's no naming or understanding benefit. As a matter of fact, they *hinder* understanding more than anything. This is why I try to only put utter crap in base classes, and when it's important crap, I put it in a method and name it something descriptive and call it in the context. If I were to rewrite these specs I *may* have a single base class called ProgramSpecs. It would probably just have the static program field, but be a place holder in case i needed any utility methods. Naming specs with the with_foo_bar implies that that name is important, which it isn't. It's not included in the report for a reason. Your context description should be fully encapsulated by the name of the context class.

Another thing I'm seeing... and I'm not sure if this is just circumstantial, but do you know that you can have more than one context in a class hierarchy? In other words, something like outputBuilder = new StringBuilder() would go in the subclasses establish context. They're run in order from basiest to subbiest. The Because is *only* a way to highlight a line and say "this is the catalyst that makes the observations possible... everything else up to this point is also important, but this is the real meat". Because is actually *part* of the context. The Context is the arrange and the act (if there is an act). Here's an example of multiple context clauses (though i have no idea why i didn't use because here, heh): http://github.com/aaronjensen/compete/blob/master/Source/Compete.Specs/Model/Game/AggregateResultSpecs.cs

As an aside, I feel the Program class is a bit awkward. Personally, it'd make more sense if the StringBuilder was a constructor parameter and the args were parameters to the run method. That's just my style though--i'm not saying it's better. It would definitely make testing this less awkward. Actually, look at your context. "when running with no arguments". Your code isn't doing what you said it would do, at least not in the simplest fashion. I think I'll change my position to "strongly prefer" the arguments to be passed to the Run method :) More often than not, when you're feeling pain while testing it's because your API can be improved.

You may, if you haven't already, want to take a look at the mspec console runner specs: http://github.com/machine/machine.specifications/blob/master/Source/Machine.Specifications.ConsoleRunner.Specs/ProgramSpecs.cs

They're quite similar to the domain you were writing specs for and may help. Yes, I used with_runner there, they're old ;)

Hope that helps a bit, let me know if you have any other questions or anything.

Thanks, Aaron

Check out Virtual ALT.NET

aaronjensen — Tue, 30 Jun 2009 23:14:00 GMT

Several months ago a few people started hosting a Virtual ALT.NET meeting right here on the information super highway. I've been to a few and they're always packed with information and good conversation. It's a great way to learn new things or show off cool stuff you've been working on. If you haven't been to one, I'd recommend you check one out. There are two great looking meetings hosted by Ryan Svihla coming up soon:

Development with Castle Project with Ryan Svihla July 1 and July 8
Ryan will be doing a two part series on the Castle Project. Mark your calendar for some Castle Project fun.
Ryan Svihla has been working as a C# developer Farm Bureau Bank in San Antonio since September 2007. Before that he worked as a Consultant in Lincoln, NE for 3 years, where he had working experience with Php, some Perl, Python and of course C#. Attemping Agile since early 2008 as an eager student with a focus on making programming more useful and relevant for the end user.

IoC and Dip through Castle Windsor
Ever wonder what acronyms like IoC and Dip mean? If you know what they mean do you wonder why anyone would use them in code? This talk aims to deal primarily with those two questions through the use of Castle Windsor IoC container. Intermediate level C# material with a couple of more advanced demos at the end for fun and pleasure.
Central Daylight Time
Start Time: Web, July 1, 2009 8:00 PM UTC/GMT -5 hours
End Time: Web, July 1, 2009 10:00 PM UTC/GMT -5 hours
Attendee URL: http://snipr.com/virtualaltnet (Live Meeting)

Web Development with Castle Monorail, Active Record and Brail view engine
Have a look at the first popular MVC .Net based web framework. Also will be covering persistance with ActiveRecord, and view templates using Brail. Bonus, will demo a plugin framework for building CMS like applications.
Central Daylight Time
Start Time: Web, July 8, 2009 8:00 PM UTC/GMT -5 hours
End Time: Web, July 8, 2009 10:00 PM UTC/GMT -5 hours
Attendee URL: http://snipr.com/virtualaltnet (Live Meeting)

Hope to see you all there!

MSpec... for Boo!

aaronjensen — Sun, 28 Jun 2009 05:41:50 GMT

Jeffery Olson (a fellow Eleutian guy) has put in some good effort to create a very readable, very clean MSpec DSL for Boo. You should give it a gander.

TeamCity.CodeBetter.com now has git support!

aaronjensen — Sun, 22 Mar 2009 00:05:17 GMT

Just wanted to post quickly to let everyone know that I just finished adding git support to TeamCity.CodeBetter.com, so if you've got an OSS project on git (and if it isn't, you should consider moving it) you've been dying to get continuous integration going, please apply to have us host CI for your OSS project:

Register a user account here.
Email teamcity@codebetter.com with the following information:

Your user account name, which you created above.
Project name & URL.
Link to your OSI-approved OSS license.
URL and type (SVN, CVS, git, ...) of your source control system.
Build runner (NAnt, MSBuild, Rake, etc.) and default target.
Any additional requirements you might have.

Hosting your OSS project on github

aaronjensen — Thu, 12 Mar 2009 17:10:19 GMT

Maybe you've heard me or others blather on about how great git is and how great github is to host git projects. Maybe you've heard it enough that you want to give it a shot or at least see what is involved in it and why us crazies think it's so great. I'll attempt to describe how one could go about moving their project to github and some tips for maintaining it. This is by no means a comprehensive guide, but it should be enough to get you started. Thankfully there is plenty of content on the net already so I'll be doing a lot of linking.

Step 1 - Install Git and create your github account

Read through this awesome guide from Kyle Cordes.

Mac users - follow one of the guides on github to get git installed, then follow the rest of Kyle's guide.

Step 2 - Import your svn project onto github

There are a few ways you can do this. Github makes it very easy by allowing you to just import an svn repository from their UI. Here's a guide on github on some ways to do this.

Step 3 - Clone your project locally

Kyle's guide talks about how to clone your repository. It's pretty simple though, just type "git clone git@github.com:username/repositoryname.git". You can see your public (read-only) and private (read/write, use this one) clone url here on your project's page, like this:

Step 4 - Setup your .gitignore

Unlike SVN's abomination of ignoring procedure, git sticks to a single .gitignore file in the root of your repository to specify ignored files. This makes it very easy to get things up and ignored and keep them clean. In SVN, every time you add a project you'd need to ignore the bin and the obj directories for instance. In git, you just have one rule that always ignores them. Here's a sample of my baseline .gitignore file:

obj
bin
_ReSharper.*
*.csproj.user
*.resharper.user
*.resharper
*.suo
*.cache
*~
*.swp
/Build
NDependOut

Once you've got that file set up, you'll need to commit it and push it. There's lots of guides on committing and staging and such and I'll link to those below, but for now just do this:

git add .gitignore
git commit -m "Adding .gitignore"
git push

So what did that do? The first line, git add..., staged the added file for commit. All changes, adds, deletes, etc, must be "staged" before they are committed. Staging is a powerful thing, but I'll let the other guides go into that. The next line, git commit..., committed your staged change to your local repository. This is so quick because it doesn't actually talk to github. The change is only local. The next line, git push, actually pushes your changes up to the remote repository (github).

Step 5 - Learn

Time to pause for some learning. Like I mentioned, there's a lot of great material out there already. Here are a few resources:

An Illustrated Guide to Git on Windows - Great guide to using git on windows and all of the gui tools available with msysgit
GitCasts - Some great screencasts showing how to work with git. A lot of content here, some are a bit long but they're great learning tools.
Why Git is Better than X - Great for showing people the difference between git and other source control solutions. Helpful sales tool if someone is on the fence.

Step 6 - Maintain and accept contributions

So now the fun part. You get git. You have your project on github. Now what? How do people send you patches? Do they still email you patch files? Isn't there a better way? I thought I said git was better! Never fear, yes there's a *much* better way to accept contributions now that you're using git and on github. Remember, git is a distributed version control system. It was built for this stuff!

First, the benefits:

One of the coolest things you'll notice after accepting your first patch from someone in git is that not only will you have all of their individual granular commits in your timeline (rather than one giant patch) but those commits will still be attributed to the original author and even maintain their original change date!

Next, how to contribute:

Find your repository on github.
Fork it (click the little fork button). Forking on github is not necessarily claiming that you're going to go your own way with a project. I've seen people new to github get concerned when their project was forked, but really it's just the beginning of the contribution cycle.

Clone your fork locally. For example,

git clone git@github.com:aaronjensen/machine.git

Add a remote for the original repository, this way you can get any changes to that repository locally.
```
git remote add machine git://github.com/machine/machine.git
git fetch machine
```
Make local changes. Commit them. Push them.
Send a pull request. This will notify the original repository's owner that you want them to pull your changes and merge them into their repository. Here's a github guide on the subject.
Sit back and wait for the project owner to accept your patch!

Finally, how to accept patches:

As a project owner when one of these pull requests come in you'll get a message in your inbox on github. From there, you can either manually pull from the command line like mentioned in the above github guide or, if there would be no merge conflicts, you can use github's swanky Fork Queue UI to merge changes in from the site itself! Check out a post and a video about that.

Step 7 - Enjoy the pretty pictures

Github has some really cool graphs for all of the projects. I encourage you to check them out. here are a few from machine:

Machine.Specifications (MSpec) has moved (and git rocks)

aaronjensen — Sat, 07 Mar 2009 16:22:00 GMT

EDIT:The actual clone url is here, the original link is to the github page. Sorry for the confusion:

git clone git://github.com/machine/machine.specifications.git

I just completed breaking Machine.Specifications into its own repository. It is now here:

http://github.com/machine/machine.specifications

Why did I do this? Many reasons, for one, git is better suited for many smaller repositories. There is support for submodules so that you can combine and nest repositories. As soon as I finish breaking out all of the various pieces of Machine I will make Machine the root of all Machine projects so you only have to grab the one. Also, having MSpec in its own repository allows you to keep its history in one place. This is helpful if you want to listen to/care about changes only to MSpec and not the rest of the Machine library.

If you'll notice, Machine.Specification's commit log is fully intact. Not only that, but it doesn't have any of the commits for non-related libraries. Yep, I was able to cleanly split it into its own branch and preserve history. Like I said, git rocks. How did I do this? Check out this awesome guide. After following that guide, I used a script to prune empty commits. Quite painless and powerful. I love git.

Oh and be sure to take a look at the latest stuff in there, Alexander Groß added a ReSharper 4.1 and 4.5 runner and Adam Tybor added TeamCity support to the console runner. Thanks guys!

The ALT.NET Programming Contest

aaronjensen — Thu, 05 Mar 2009 17:16:00 GMT

Several months ago, Justin Wilcox introduced me to the idea of a live programming contest. The basic idea is that you get a bunch of programmers together, form teams of two if you wish, and set them off to write a bot for some sort of game (think Rock, Paper, Scissors) with the ultimate goal of them pitting their bots against each other to determine a winner. Check out a video of the first event.

Not too long ago, Glenn Block convinced me to put on a similar contest for ALT.NET Seattle. We held the contest on Saturday evening and got around 14 participants. The event was a lot of fun. The first hour ended up being more of a contest for Jacob and I than the actual participants while we practiced extreme agile just-in-time development on the competition framework we were using and fought off multiple hack attempts from the "participants", but after things settled down and we got some show stopping bugs fixed things progressed and we were able to see some great competition between a bunch of smart people.

Ultimately, John Rudolf Lewis was victorious; you can see his team "More Beer Driven Development" went an awe-inspiring 9-0 in the final round. I should also mention a few other achievements. Jeff Tucker won Round 2, but apparently couldn't keep up when water balloons were introduced. Jay R. Wren successfully html injected a lovely image into everyone's game logs. Nate Kohari tried really hard to hack the game itself and invent an unbeatable move. Unfortunately, he only succeeded in silently bringing IIS down without any sort of error messages with his Mono.Cecil magic and craziness. And finally, Eleutian's very own Jeff Olson managed to thread bomb the server forcing us to reboot. Lesson learned, make sure and bullet proof your server if you're going to give any of these guys access your ip.

In the next post I'll detail the framework we wrote to make the competition happen and describe how you can run your own!

Rapid UI Mockups with Balsamiq

aaronjensen — Mon, 27 Oct 2008 01:12:39 GMT

I recently came across Balsamiq, a very well done application for quickly mocking up UI prototypes. With simple drag and drops you can quickly create some pretty slick prototypes. The prototypes have a sketch like look which allows the viewer to use more of their imagination, something I think is a subtle, yet powerful advantage.

It's been a while since I've been so impressed with an app right out of the box... especially a Flash app. Just about everything works as I'd expect, right down to common keyboard shortcuts. It's got good organization in it's "ribbon" and so far it's had just about every type of thing I need. It looks like it has JIRA and Confluence support, though that's a bit on the pricey side. The Desktop version is reasonably priced though, and the web version seems to be free to use if you can put up with a nag every 5 minutes.

Nothing beats a whiteboard if you're all in the same office, but I'd say this is a close second. Certainly better than Visio :)