All The Code launched today, with a bit of a rockety start [namely <>() and similar broke the engine]. Right now its on reddit. Its kind of interesting looking at what people are searching for, namely one person searched for "lang:c [somestuff]", so I'm thinking about adding an error message for that. I'll probably write some more later, but I've got to be ready for tomorrow.
Wednesday, January 31, 2007
Monday, January 29, 2007
So I was starting the post of as an explanation of yet another delay for AllTheCode. I decided I'd take a quick 30 minutes to take a look at the state of things. Those 30 minutes quickly turned into two hours, but now All The Code seems to work properly enough to be ready for release. The
nameservers have been swapped over, and its just a matter of swapping some files on the 31st and launching the instance, and hoping nothing else breaks :). Sure, it still has a lot of "features" of the suspiciously like a bug variety, but its usable enough. Now back to the work I should have been doing :)
Tuesday, January 23, 2007
The past few weeks have been fairly hectic which have been keeping me from working on All The Code. Another DB build did go through [thanks largely to amazon increasing my EC2 instance limit :) ], but I haven't had time to fully verify it yet. Early next week I'm giving another demo of All The Code so I really should get around to that soon.
I've started the process to take the four months starting in may to work solely on All The Code. The way things are structured, there is a lot of writing and presenting that I'm going to have to do before I can get final approval, but even if that does not work out I've got a back up plan. I'm hoping I can find some time in February to really pull things together, since I am going to be giving a public demo of it on the 26th of February. While the demo will probably not in front of a large number of people, but it will be recorded and I would much rather not have a "oops it crashed" moment on tape [or even worse live] :)
I'd also like to take this time to thank the people at Amazon Web Services and Alexa Web Search Platform for providing the platform I've built almost everything on top off. They have gone a long way to opening the websearch (and other data intensive operations) to the three crazy guys in garage.
Monday, January 15, 2007
So, the database built again. There seems to be a bug in the code where by certain cases involving weird class inheritance isn't being properly handled [whereas it use to be handled properly], so I'm going to have to look into that and probably do another database build. I have a meeting on Wednesday with the person at UW responsible for students wishing to do business on their Co-Op term. From what I recall, his background is much more manufacturing / physical oriented, so I might have a bit of difficulty explaining exactly what I do. I may also try talking to the people I talked to about eight months ago, but I'm not sure if thats a good idea or not.
Once the final alpha 0.1 database is ready, I will probably give a demo to the csclub, which will hopefully go better than my previous demo :).
The present pre-alpha todo list is:
1) fix class bug
2) rebuild DB
3) fix up HTML so it works on most popular browsers (presently breaks in IE6,Konquerer, and probably a few more).
4)Fix pagination so it makes sense (IE when there are only seven results don't say result 0 to 10 of 7 results )
5)Fix code viewer so it doesn't have a race condition
6)Write the FAQ
7)Have someone who writes better English than I do go over the
8)Fix load balancing so it doesn't die randomly
9)Prepare a demo of All The Code
Saturday, January 13, 2007
The University of Waterloo is celebrating its 50th anniversary, and they have chosen the slogan to be "the spirit of why not?". Right now I'm in my 3A academic term, and I'm trying to figure out what I should do with the Co-Op term between 3A and 3B. I've been going back and forth between applying only to awesome jobs, and not applying to any jobs and working on my own projects (like AllTheCode ). I figure, why not?
Friday, January 12, 2007
So, there is now a completed DB build for the production system, however there seem to be some serious differences between the production system and the development/testing system which have resulted in such fun things as the code viewer erroring out quite frequently. Things are getting quite busy with compilers, so fixing it is going to be challenging to get done. I'm hoping that everything should be ready for the end of the month, since after that point I won't have any serious amount of time to put into All The Code.
Tuesday, January 02, 2007
Not particularly surprisingly, the DB build encountered some not so nice errors, its still trundling along but at its present rate it would take ~ 20 days to build [which is totally not cool]. My normal solution to a problem like this is to through inexpensive hardware at it, but sadly the last stage DB build is still only handled in a monolithic single threaded manner, so it does not look like it will be done in time. The solution is to [hopefully one last time] delay the full product launch until the 8th, which will hopefully give me enough time to either track down and fix the bottle neck, or write some code to split the task up and get Amazon to increase my EC2 limit, or both :)
Monday, January 01, 2007
I seem to be making a habit of doing this, but I've just kicked off the final stage of the DB build for All The Code. Out of the ~50k files indexed it found ~750k relations [for the version I presented at DemoCamp I limited it to 10k relations so that it would build in time for the demo]. I hope this builds in time for Wednesday morning :) Tomorrow I'm moving back to Waterloo, so if there are any problems while its building there is not much that I can do....