The way issue/bug tracking works at our company is that typically an issue is raised, and a team of 'screeners' (the design and verification managers) will look at them and assign them to developers and assign a priority to them. Myself and a co-worker, who shall remain unnamed, joke around about a manager's 'routing' table and how certain keywords automatically trigger an assignment to a particular developer. This got me thinking, what if a program could pre-emptively predict who the issue will be assigned to?
I've been toiling away in the laserdeathstehr labs and have come up with another little project. This one is called TwitterBurst. It is a realtime visualization of the activity on twitter. You can see a video of it here: http://www.youtube.com/watch?v=_i3Zg5CEHnc. And the source for the project is at https://hg.laserdeathstehr.com
I have gone live with what I would say is a prototype, beta site: mytree.laserdeathstehr.com. Here, when the stream is on, you can control the lights of my tree by submitting a MIDI file. It uses the same setup as described in my post Project Rudolph Part 1, but I've built a web front end, to allow the world wide web control the tree.
Over the course of the last year, and even maybe the last two years, I've felt like I've been stuck in a rut and not really going anywhere. I think one of the main reasons is that I feel like I personally had no concrete things I wanted to achieve, only that I wanted something different. Last night, I was laying awake at 2:30 am feeling pretty crappy, wondering how I can feel better. I've always known that there is only one person who can turn things around, but I decided that now is time to go for it.
For as long as I can remember, I've always had an unusual interest in musical lightshows. For those who don't know, I am referring to a light display that flashes lights to music, usually popular around Christmas time. I remember when I was in university, I told myself every Christmas season that I would build one for the house we were renting, but I never got around to it.
One of the ways I like to start my morning is to read up on news from Canada and around the world. I usually do this by visiting the website of the CBC. To keep up with all the web 2.0 coolness, the CBC allows for comments on most of its news stories. On almost every article, I come across a comment that either makes me laugh or wonder what the heck the person was thinking.
This post isn't going to be about any one of my projects, or programming at all, its about something I recently purchased. On Wednesday, I picked up a new piece of hardware, namely a 2010 Mazda 3 sport... :) It was my first time buying a new vehicle, and it was quite the experience.
In one of my previous posts, I outlined an idea for an application that would allow the current song on a mobile device to start playing on the user's computer. After some thought I decided to take the plunge and write it up. The current incarnation is made up of two parts: an iphone/ipod touch app and a cocoa server that runs on the users pc. You can check out a short demo of the system here.
This weekend I started, or rather resurrected a project/idea that I have been kicking around for about a year. Last summer at work, I was busy fixing bugs and was wondering where the majority of the issues were coming from; were they mostly related to the feature I was working on, or were they spread out across the code, and also, who was handling most of these issues. I could dig through the commit history of svn, but its a big project, and where would I start?