We had a quick 15-minute meeting where Chris outlined the concept to us and drew some sketches. Tris and I got straight to work on designing the models whilst Chris put together a visual concept. We had lots of discussion about the colour scheme before agreeing on the bright pink. James and Richard were to design the front end, Tris did the backend data manipulating and URL routing. As the person with previous experience in the Twitter API, my part was to get data in from Twitter and send responses out.

By 10:20 we knew this was going to work! Having looked up search.twitter.com for a few select phrases, we discovered that people were indeed twittering about their various addictions!

Data found on Twitter!

As James and Richard were cutting up the design and turning it into HTML and CSS, Chris made a very welcome coffee round.

At about 11:15 we had a major success for the data import, upon discovering that Twitter Search can bring back up to 100 results at a time. We thought it was limited to 15. This meant that we could go back and select much more data.

Lots of data for us to use

Obviously, not all this data is particularly interesting, and some of it is just retweets of other people’s addictions. Tris helped me to tweak the regular expression to filter out unwanted results.

Meanwhile, the front end was coming along nicely:

An early version of the front end

At midday Chris bought the domain ykyat.com. We were going to use a different domain name, but after seeing that ykyat.com was available, we all agreed that it was a much better domain. I created the Twitter account @ykyat and applied the background image and colour scheme to the Twitter page.

There was a mild panic over URL routing – we wanted to give each ykyat a unique tag, but we also wanted a nice short URL to browse by topic. It was decided to use a tilde when viewing by tag. The routing is rather non-standard for Rails; I found it interesting to see how it is done. Kudos to Tris for more regular expression magic! :)

I spent my lunch break sitting outside the office wondering how best to implement the since_id so as not to bother Twitter Search by asking for the same results more than once. I had three ideas in mind, and it was useful to have a break to consider the most efficient way.

At about 14:00 things were all coming together very nicely! Tris had organised a cron job for the import, and I was very excited to see a tweet of mine imported and displayed in the gorgeous UI that James and Richard had crafted!

A tweet imported and displayed

James and Richard turned their attention to the rating system whilst Tris set up the live server on Amazon EC2. My next task was to tweet back an @ reply to the addicted person, with the URL to let them know they had been featured on #ykyat. Thanks to the simplicity of the Twitter API, this didn’t take long …

Ykyat bot responds to the addicted person

Our Git repository was looking quite exciting at about this time!

Everything coming together

I then started to look at bringing in the Twitter user icons. All was going fine until I hit the limit of API requests per hour. We realised that we couldn’t just ask Twitter for the icon each time every page was loaded; we would have to be more pragmatic about it. We put the user icons on hold. It was getting to late afternoon by now and we also decided we didn’t have time for commenting. Although Tris had written the back end to support comments, we were aware that the Twitter authentication needed to be secure and well tested so we didn’t want to rush that bit.

The last part of the afternoon was spent getting it working on the live server and making a few tweaks and polish to the user interface. We were all very excited to see what we had achieved in a day! Chris announced at 17:42 that we were done. We went home. Half an hour later Chris announced it on Twitter:

Chris announces #ykyat on Twitter

We made a few enhancements over the weekend. Chris worked on the navigator, showing popular categories and popular tweeters. I was itching to leave comments, which was very motivating for me, knowing that I had the power to enable it! I wrote the Twitter authentication and commenting system on Sunday evening and it went live on Monday!

Building #ykyat was an exciting and rewarding experience for all of us. It was good to work together as one team when so often we each work on different projects. It was fascinating to see an idea grow into a live web app in one day. I think we all knew that we could do it, but it was great to be able to prove it to the world!

Screenshot of ykyat.com

I’ll blog more about this next week, but just wanted to quickly let you know about our new web application, ykyat.com.

It’s a very simple service built on Twitter. It collates classic ‘you know you’re addicted to…’ jokes on a central website, and allows them to be rated so that the funniest are promoted for all to see.

It was built partly for fun, and partly as a grand experiment in rapid application design and development: we designed, built and deployed the entire app from the ground up in 8 hours 42 minutes. We learnt a lot from the process and I’ll be posting a minute by minute diary with some screenshots next week.

I find it slightly bizarre that even economic cycles have their own branding departments now…

Having ‘taste’ is a really important skill you can have as a developer – even if you don’t classify yourself as a ‘designer’. It’s a great thing to be able to add User Interface elements in just the right place, or code a feature up that just feels right. When a piece of software has been crafted lovingly, everyone loves to use it.

Having taste as a developer is a bit like what my wife says about being tidy around the house. Now, I’m not a naturally tidy guy, but I’m learning to be; mostly because if I wasn’t I would drive her crazy! Sometimes the problem is that I just don’t see the mess, but that’s really laziness. It’s because I’ve not yet learned to take a second look each time and judge my attempt at cleaning the kitchen with her standards. Usually at that point I see where I could do better.

It’s the same with code/feature design. Most of the time it just takes another look, and not settling for just “good enough”. It’s a choice, and making the right one will make someone else that much happier with the work we do. Food for thought.

In the past I’ve been guilty of two equal yet opposite mistakes on website projects regarding design implementation. There’s a temptation to leave the implementation of the design right until the end of the project (”It’ll only take a day or two, after all”). There’s also a strong urge to get the design done right at the beginning of the project, to really show the client what the finished article will look like.

Both of these approaches turned out to be mistakes.

When we’ve left the design until the end of the project, the client ends up directionless. Unless they’ve got a programming background, or heck of lot of vision (and most don’t), they just won’t put your lovely design concepts together with your naked ‘Times New Roman’ HTML wireframes. Sure, the site works, and works well, but it just won’t feel right. The client won’t be able to get past how it looks and will ignore all your fervent feature demos because they’ll be thinking about that ugly font.

With one project on which we did this, the client ended up changing their mind too much about what they wanted; had they seen the design progressively improving look and feel they may well have been able to catch the vision for the site quicker. With less understanding clients, you run the danger that all your hard work behind the scenes will be dismissed just because it looks awful and they wonder what you’ve been doing with all that time and money.

So why not get those concepts right onto screen straight away in their full glory? That way they’ll know exactly what they’re getting, right?

Big mistake. When we’ve done this in the past, we’ve noted that clients often equate the progress of the design with the general progress of the site. With one project, we rolled up at the end of the first iteration with a beautiful website that showed the finished design in all its glory. The client was very pleased. However, the very next iteration, after we’d spent just as much time on functionality and ‘behind the scenes stuff’, they were less pleased. Despite us telling them how much we’d accomplished, they just couldn’t quite see it. We then spent quite a while on the back foot trying to convince them stuff was happening, even though the site looked much the same as it did at the start!

So where’s the balance? I’m not sure there’s a perfect middle way; it depends on the client you’re working with and the type of project you’re working on. These days however we progress with the look and feel in stages; it tends to ensure both client and consultancy are on the same page and everyone can measure progress in their own way.