Wednesday, June 20, 2007

Developing for Two Worlds

Developing for two worlds (Internet and appliance, or perhaps more accurately public and corporate) has its benefits and its downsides.

A lot of my time is spent implementing features which only really are going to be used by the Internet version, or the appliance version. Or, more commonly, after implementing a feature for one of them, I have to do a significant amount of re-tooling the feature to work for the other world. For example, adding tagging to the appliance version of All The Code was able to be done in only a few minutes, however for the Internet version I need to keep in mind the problems of database synchronization, possible untrusted users.

On the other hand, developing for two very different types of users has its occasional benefit. Traditionally with appliance software, and most software which is for internal company use, getting beta testers is much harder than with a public application.

With all that said and done, there are still things which are almost exactly the same. For example improving syntax highlighting is the same bit of code, without having to make changes for either "world".

Saturday, June 09, 2007

Code monkey likes code :)

Amazon recently discontinued AWSP, which is kind of unfortunate given that All The Code relies on it for raw data for the public version. That being said, the new interface is seems much cleaner and has the potential to make my life a whole lot easier.

Fortunately, this coincides with my need to test the subversion integration of All The Code, so I'm in the process of pulling down as lot of code from various subversion repositories. I'm looking to truly stress test the core before I hand it off to the first round of beta testing, so I'm also pulling down code from a few other sources. The next public version of ATC should see the index increase in size by a factor of about 20 [and this will hopefully be ready for the end of next week, but no promises :)]. There are quite a few sources of potential problems related to growing the amount of code indexed by so much, so I'm really hoping to flush out some bugs.

If there is time, I will try to roll out tagging and possibly voting, although that might have to wait until the end of the summer. Since, initially, All The Code was built where updates would be incredibly infrequent (say once every day at most), I made some archecture decissions, which in hindsight weren't the greatest. On the other hand, nothing is set in stone yet so I'm going

The new PLT scheme release supposedly has a new unit testing framework which I'm hoping to get a chance to play around with and maybe use for my Google Summer of Code project. Ideally I want to make things easy for people to go forward and take it on to different scheme implementations (like chicken scheme), so I'm going to have to tread carefully with how much PLT specific magic I use.

Thursday, June 07, 2007

Google Summer of Code Surpise

All Google Summer of Code students received a copy of "Producing Open Source Software", my copy arrived a few days ago in Ottawa and just finished the trip down to Waterloo. I'm looking forward to reading it, although where I'll find the time is another matter entirely.

Presenting at DemoCamp Guelph

I went to the first DemoCampGuelph which was lots of fun. I was one of the presenters there, and so I naturally demoed All The Code. I managed to get a lift down with (one of the other presenters also from waterloo)

One of the people in the audience (David Crow) knew of Ocaml [which is the language in which a lot of the backend for ATC sits] and we talked a bit about the fun world of functional programming :)

Free Blog Counter