Post Django Dash 2012 Recap

We did it. Django Dash for our second year in a row. A little different, but still memorable.

From home

This year we spent the majority working from the comfort of our own homes.

Thanks to Schipul and our decision to move toward a remote work lifestyle we were able to easily face this year’s competiton in style aka in our jammies.

If anything this saved us valuable travel and setup time.

Lessons learned

I said this last year, but I’ll say it again this year; because apparently we did not learn our lesson.

Make as many decisions as possible before the competition. Think roadmap or dare I say clipboard of fun.

One of our greatest strengths is our team. We work together every workday, this competition was no different. I can only imagine the stop-and-go speed of competing on a team that doesn’t know each other.

Not the time to learn

This year I spent some time on two things I’ve only spent a couple of minutes on in the past. The Twitter Bootstrap project and Class Based Views. While my colleagues spent their time learning about Google authentication and the interim their experiencing as they adopt new technologies.

Competition time is definitely not the time to learn new things. It’s just so hard not to. You find yourself inspired and when inspiration strikes all you want to do is strive, learn new things and create.

In the case of Google authentication, it had to be learned.  Our project was dependent on it, as always; it’s amazing what you can do when you have to.

I don’t foresee this habit waning any time soon. If anything I look forward to it. I learned a lot of useful things this weekend and I’m left wanting more. Give me that feeling anyday.

Veering from the original mission

Early Sunday morning we found ourselves having to make a choice. A choice between accumilating more points by submitting more commits and focusing on specific code requirements such as standards and creating tests. Or making a product that might actually provide some value to many in the near future.

We chose the latter. The idea of our project actually being useful at more than just collecting points is an honor. With this in mind we refocused and put effort into submitting a finished product that’s worth demoing.

We’ll be demoing our finished 48 hour project to the office and get our first ouside perspective. No matter what people say I’m not-so-secretly wishing we can keep up this momentum and continue improving our project.

What did you build, tell me already!?

Without getting into too much detail – at this point in time – it’s best summarized here.

You can sign up for the site now and take it for a spin. Keep in mind that this was 48 hours of code. You might find some quirks and so-called missing features.

What about the competition?

It’s been said that we get our results some time this week; but as I mentioned before we’re more excited about the project itself and what it can bring to others.

It’s open sourced

One of the rules of the Django Dash competition is that the project itself must remain open sourced. So feel free to take a glance at our code on and fork the code if you’d like to start contributing.

The 2012 Django Dash is This Weekend!

We are happy to be sponsoring and participating in the 2012 Django Dash!

What is Django Dash?

The Django Dash is a 48 hour code marathon starting tonight at 7pm CST where teams compete to produce the best app they can in 48 hours! The winners get prizes from the sponsors (including Tendenci)! We’re supplying $100 gift cards to the top three teams.

The Rules:

  1. Majority in Django
  2. Nothing Gets Built Ahead Of Time
  3. 48 Hours To Build
  4. Max Team Of 3
  5. Your Choice Of Git Or Mercurial
  6. Your Entry Is Open Source
  7. Any Third Party Code Is Fine (But Affects Your Score)
  8. You Must Use Pip Requirements Or Buildout

Our experience last year

We competed last year, our first year ever; with a team made up of Glen, Luke, and myself (Eloy). We built a blogging platform specifically for coders. The niche idea being that we can easily reference code blocks using short codes. This means we spend less time writing blog posts, and more time sharing anecdotal code discoveries.

It’s hard to believe that the project has lasted the full year and is still receiving updates regularly.

Last year’s experience could best be summed up as fast and fun. Imagine developing but without the meetings, without constant interruptions, and without having the roadblock of approval. Ideas flowing and tangible features being created in minutes. It’s this for 48 hours straight with the occasional break for eating, sleeping, and … other things.

What you come out with, is a product; ideally mostly finished. Not just a conversation, or a thought, but an actual product. That in itself is worth celebrating. A weekend that can easily be filed under productive.

The freedom of developing for fun and not to pay to the bills. The reason you originally started developing; you remember when all you wanted to do was create.

Look for our Team This Year!

Our team this year will be made up of Jenny, JMO and myself (Eloy). Our team name is Jeff Goldblum and we won’t share what we’re building just yet. Check out our progress on

More on Django Dash!

Whether you’ll be coding through it or not, follow the latest from Django Dash by following @Tendenci on Twitter and the hashtag #djangodash and on