Meanwhile, I’ve updated my research page, so if you’re curious about what I’ve been working on in the academia, be sure to check it. As to what I’ve been up to in the industry, more news will follow soon ;-)

That’s about it. Really. Ok, I’m leaving out some of the details, but the oficial docs provide the full story, and this stackoverflow thread makes a great reading if you are looking to know more about metaclasses.

Edit: Added a couple of instances to the diagram too.

[…] to say that objects have failed because they don’t solve all possible problems is like saying carbohydrates have failed because you can’t live on pure sugar. […]

Don’t miss it, really.

Django’s models do this well¹, but they are more “relational” than they actually needed to be — we still have to deal with stuff like ForeignKeys and the like.

I would rather think exclusively in terms of objects, but, no ORM can fully abstract the relational database underneath. This is a leaky abstraction that half of the world would like to see fixed, and the other half as actually tried to fix it but failed to varying degrees. And that’s why I understand why django’s approach has converged to what it is today. It reflects a reasonable balance of these forces.

I still think there are better names than ForeignKey to represent one-to-many associations, though.

Creating and visualizing django models

Even if not purely object-oriented in their nature, I still think of django models as object-oriented domain entities. And the domain model of a system can really grow beyond the point where it can fit in a single person’s mind. Django projects are no exception.

So, I’ve been trying to find a tool that helps me dealing with large django projects. Here are some of my findings:

• UML-to-Django —Uses XSL to transform a XMI file, to Django model classes. It has a few limitations at this point. Namely, it works well when the source XMI is created by ArgoUML, but I couldn’t use it successful with class models exported from other tools. I’m currently using Visual Paradigm, and the best way I found to bring my model to UML-to-django was to make Visual Paradigm generate Java source-code, and reverse engineer it in ArgoUML. And this still required a little bit of fiddling with the XMI produced by ArgoUML, but it worked in the end.
• Dia-to-Django — Didn’t try it, as the SVN repo seems to have gone the way of the Dodo, but it looks like it could have been a viable alternative to UML-to-Django.
• GraphModels extension — Rather than allow to generate django models from a UML class diagram, the graphmodels extension allows to visualize a django project as a diagram. Not a bad option; one can definitely understand a django project much quicker than looking at a diagram of the model classes. Unfortunately the notation is much closer to the relational world than to a object oriented one. Not that there’s anything wrong with that, but the visual elements of a class diagram convey a richer semantics, and I do take more time to grasp a diagram of this kind than I take to grasp a class diagram.
• Django-yuml — Creates UML class diagrams from django models, using yuml. It’s obviously limited to what yUML can express, and as such it can’t represent stuff like association classes. Django models can express associative classes using the through option.
• DUDE: Django UML Designer — This one is very different from the previous tools, but interesting nonetheless. Its a django-based UML modeler. It’s a dead project, apparently, but in case you’re interested in this kind of stuff, check models.py for a very early implementation of MOF using django model classes.

The graphmodels extension is serving me good for now, after some hacking to make the generated diagrams closer to UML class diagrams. Here’s an example of how it looks for the pycon system source code:

Here’s how it looked before the modifications:

This example doesn’t have generalizations, which also look much nicer with my changes. Here’s an example of how they look using my patch, before and after respectively:

Update 2011/09/23: Fixed big mixup with the pictures.

Lacking the time to make my own theme, this time I’m just going with one by someone else, with of course a couple of customizations of my own. For posterity, this is how the website used to look.

What has been keeping me so busy you ask? My job and my PhD research are the main culprits. I’ve lost count on the number times my thesis title has changed, but I’m pretty confident I’ve finally reached one with which I can reasonably see where I’m heading, and with which I am pretty sure to enjoy the ride. I hope I’ll be ready to give you more details soon :)

But the last few weeks, my mind has also been somewhere else. I’ve been organizing an event on Agile Software Development — Agile Portugal 2010. This will be the biggest event of the kind in Portugal that I have memory of, and putting it together has been quite an endeavor, but an incredibly fun one. I’m very excited about the program and the invited speakers we already have on board, and it keeps getting better and better.

If you want to be part of this great event, you can do it either as a speaker or a participant. The Call for Speakers and the early registration period will be open until the next June 5th.

Want to know what a Kake Coding Dojo is? Hugo Corbucci explains it on his blog, and so does Danilo (note that this Coding Dojo format was previously called UberDojo).

I’m tempted to promote some Kake sessions with fellow co-workers. We’ve been talking about ways to share knowledge on TDD and other agile practices across the company, and I found this to be an excellent way to improve one’s TDD skills, and to have contact with different languages while we’re at it. Will try to report back on my findings.

Update: Hugo has just made a post about this too, with some extra info.

On the first day of EuroPLoP, my workshop said to me:
“Delete everything on page 3”
On the second day of EuroPLoP, my workshop said to me:
“Too many patterns,
and Delete everything on page 3”
On the third day of EuroPLoP, my workshop said to me:
“Three known uses,
too many patterns,
and Delete everything on page 3”
On the fourth day of EuroPLoP, my workshop said to me:
“Four forces,
three known uses,
too many patterns,
and Delete everything on page 3”
On the fifth day of EuroPLoP, my workshop said to me:
“Five good things,
four forces,
three known uses,
too many patterns,
and Delete everything on page 3”
On the sixth day of EuroPLoP, my workshop said to me:
“Six dumb suggestions
five good things,
four forces,
three known uses,
too many patterns,
and Delete everything on page 3”
On the seventh day of EuroPLoP, my workshop said to me:
“Seven minor changes,
six dumb suggestions
five good things,
four forces,
three known uses,
too many patterns,
and Delete everything on page 3”

Credits: Not sure who the author is, but Charles Weir has compiled a very fun song sheet of EuroPLoP conferences which I recommend to all the PLoPers out there.

Although I still don’t blindly trust the numbers I’ve found (University of Porto isn’t on the list, so it can’t be right, can it? ;) they were the most convincing ones I came upon. They do try to explain which was the used criteria, which is a good thing.