Startup Weekend is where it all began. The concept sounded pretty interesting - get a bunch of talented folks from the Boulder tech scene together to create a startup in a weekend. Aaron couldn’t make it due to a charity bike ride, but I went ahead and signed up for a developer position. On the first night, after discussing the potential projects to do for the weekend, VoSnap was born.
So, later that night, the developers started talking. We went around the group, each person stating which languages and frameworks that they were most familiar with. Turns out that most folks claimed to be Java developers - which I thought was cool, of course. Unfortunately, only two people (myself included) mentioned HTML, JavaScript, and CSS. The fact that we only had two resources out of over 30 for front end development was a bit of a concern, but we figured that we would be ok if him and I could focus strictly on it.
I soon found that things weren’t going to go quite as planned. First, we needed version control, but no one knew how to set up Subversion but me. Second, we needed a build system, but no one knew how to set up Maven but me. Third, we needed a basic framework for the domain, persistence, and service layer, but… well, you get the picture. While I worked on all of this non-front end stuff, the back end guys spent quite a long time talking about the domain model.
Sigh. As the end of the weekend approached, I made the sad realization that we were not going to be able to deliver a solid product by our deadline. The problem wasn’t that the rest of the folks didn’t do anything, it was the fact that I had to do a lot of constant refactoring and rejiggering of the domain and service tier to get everything to even kind of work together. I was building all of the front end controller code and stitching it with the view at the last second.
So, at the end of the weekend, what did we have to show for ourselves? We had an ugly product that kind of worked to send email VoSnaps. SMS was not working at all, partly because we didn’t have a good way to test it. We didn’t want to tarnish the good name that we had built up over the weekend (heh), so we didn’t push the build to www.vosnap.com. A little known fact is that it was released under www.vosnap.com/vosnap - and it wasn’t pretty.
Then, aside from a little noise from people asking what happened to it, all was quiet. However, VoSnap was not dead, merely dormant…