One piece of good news about this site is that the code that runs it has been developed -- starting January 30, 2007 -- by a lone, bald, middle-aged guy who hasn't seriously programmed in 20-some years. (This was made possible by Ruby on Rails, as well as many other open source projects.)
Now for the bad news. The bad news is that the code that runs this site has been developed by a lone, bald, middle-aged guy who hasn't seriously programmed in 20-some years.
What does this mean for you? It means ...
WATCH OUT!
Specifically, watch out for the site blowing up on you from time to time.
Don't you just love those weasley lawyer phrases like "from time to time"? Hey, don't say I didn't learn anything in law school.
The reason I use that weasley phrase here is that I have no freaking clue why the bloody site blows up. OK, well I do have some clues having to do with my penchant for failing to clean up after myself (hell, my wife could have told us that), not to mention my $5/month hosting costs.
Anyway, I'm working on it, eh? Point here is: please be patient until such time as we are able to raise an initial round of financing which will enable us to afford a real engineer and dedicated hosting service.
And when that day comes, we'll look back with nostalgia on these present days of "lastworker.com as a minefield".
But until then, watch out. No, really, I mean it. The worst is when you've spent the last half hour banging out a recipe or testimony, you hit "Submit", and you've just lost all your work. That was happening from time to time about a month ago.
I think I fixed that bug, but I'm not really sure, you know? I'm just saying.
Well, with that, have at it! Enjoy playing in our sandbox!
And please, if (when) the site blows up on you, come back and enter some feedback on what happened. It will be useful to me, or even to the aforementioned TBD skilled engineer.