Anecdote from Rebecca Wirfs-Brock: “What’s the difference between an extroverted software developer and an introverted software developer? The extroverted one stares at your feet when talking to you.”

Quote from Don Roberts: “Teaching C++ to freshmen makes me feel like a child molester.”

Here’s the fancy jersey that all student volunteers get to wear this year. I love the colours!

Apparently, attendees often try to buy Student Volunteer shirts at the conference — or afterwards on eBay. I’m not sure I want to sell mine. I think it’ll be an awesome souvenir.

The problem we were given came from Don Roberts, whose wife is a veterinarian. We were tasked with coming up with a design that would allow a veterinary hospital to keep track of its patients and their owners and bill them appropriately. Sounds simple, until you realize that you can have race horses owned by multiple people, each with a different percentage stake… and, of course, many more complications. The group quickly divided into two. One group wanted to try a pure Test-Driven Development (TDD) approach, while others wanted to go for a Prototype. I was in the prototype camp.

The interesting thing about a prototype, is that while the actual development is quick (in theory), there’s still a good deal of work that needs to go into the design before you can start programming. A prototype is usually a set of minimal functional requirements that sort of work. In that sense, it’s not too different from “hacking”. (Yes, we got into a discussion about “prototyping vs. hacking” that derailed us for a few minutes). What happened was we ended up focusing all of our energy (and time) on coming up with a solid, complete Object-Oriented design for our solution. The result of our design was little more than a class diagram on paper, but we were able to work through every use case thrown at us.

The TDD team found that they, too, needed some initial design work to be done before they could start writing the test cases that would yield code. I have trouble wrapping my head around a pure TDD approach. I understand how TDD can work if your requirements are well-defined and you already have a design that you can code tests against. The idea is that you write test cases for the design before you write the actual code. They will fail initially, and your goal as a programmer is to make them pass. In that sense, it is indeed Test-Driven Development. I’m not sure the concept can be extended to Test-Driven Design. The TDD team had little more than one test case, but they had actual code for one of the use cases, which is more than what we had.

The ensuing discussion was extremely stimulating. It’s amazing what happens when you get a bunch of really smart software geeks in a room together.

The key realization that I took away from this experience was that software design is a social activity. Even though we hadn’t met each other previously, our team had to work together. We had to help each other out and make sure we were all on the same page. We had to communicate. It was amazing that we didn’t have a lot of trouble doing it, though. We mostly seemed to agree and moved along at very reasonable pace. Maybe it’s just because we’ve all trained our brains on OOP for so long.

One question in the discussion stuck in my head the most, and I’m still thinking about it. Don asked “What is the language of design?”. Since software is collaborative and social, it follows that like any human language, we must take some concept from our minds and communicate it to someone else. If any non-programmer happened to be walking by our table, we would have sounded like the Children of Tamar. Our speech consisted of terms taken from object-oriented programming (”object”, “class”, “instance”), UML (”association”, “composition”, “aggregation”), and Design Patterns (”state pattern”, “template method”, “strategy”). And that was just the spoken part.

Software Design has a grammar. There is a way of communicating design that involves a vocabulary as well as a set of rules describing how to put sentences together. And I don’t mean English. Design is more like a mash-up that derives itself from UML and Design Patterns and English. Whatever it is, we need to ensure that those designs we have floating around in our heads can remain intact after we’ve thrown them into the ether. I think this is where a formal design language specification like UML falls short. It’s so restrictive that most UML tools require you to input far too much information before they’ll display a simple diagram. Thus defeating the purpose. UML diagrams need to be free-flowing and erasable. The language doesn’t have to be perfect, it has to be understood. More importantly, it doesn’t have to be understood by a computer — that’s what programmers are for. But programmers are people. So, design has to be understood by people. People are capable of parsing an imperfect sentence that might not be “grammatical” according to a formal specification, but can still be understood by those natural language processing mechanisms we call brains. It all comes back to software design being a social activity.

I learned a lot of stuff while coercing Typo to let static pages accept comments (for example, the about and Dead?Docs pages). I also added loads of stuff to the wordpress importer script so that it will import static pages, as well as convert categories to tags, and some other things.

The Logical Counter-point

Why should I switch to a blogging platform that needs my own modifications, when I can just keep on using Wordpress, without any problems or modifications at all?

The answer: I needed a change, and change is fun. Learning is a huge motivation, and playing around with Rails and Typo is a knowledge catalyst. :)

What about the old design? That thing was awesome!

I got bored of it. It’s my site, I can do what I want. :P (Don’t worry, I backed everything up first). I was especially sick of the dark colour scheme. The whole white-on-purple thing … it’s so emo, I don’t think it reflected how I felt anymore.

Neither does your new design, you’re a crappy web designer.

I don’t like using third-party themes available on web sites all over the place for a number of reasons: I like having something homegrown and it’s good to refresh my memory of XHTML and CSS every now and then. I also like the fact that my site looks different from all the other Typo sites out there. Sure, Origami is a beautiful theme, but it’s not mine. If it still bugs you, send your stylesheets to drskrud at gmail.

Lies! You’re procrastinating and you know it!

I have a huge SOEN 390 project work on. It’s a Task Manager written in J2EE and Servlets. I am so sick of task management right now that I needed to clear my head and work with a framework that I enjoy working with: Rails. I can’t imagine I’ll be very productive to MyTeam if I simply continue to bitch about Java, the SoenEA2 “framework”, Tomcat, Internet Explorer …

Sure I also have a chat server and client to implement, from scratch, for my System Software Design course. I’ve been letting my brain’s passive daemon processes handle the problem-solving on that one over the past week or so, and I think a design is formulating. Accorind a recent Lifehacker article, slacking off is a great way to increase one’s creativity.

There’s also an in-class presentation to be given in our User Interface tutorial on Friday morning, but we got the bulk of that done today, and I think we’re stylishly ready.

As always, feel free to leave your comments, and marvel at the really cool AJAX comment form… :)