I guess it's a good thing of sorts if you consistently look back upon your code and find it antiquated... it means (let's hope) that you're still constantly learning. Of course I'd love to just see it and be proud every time, but I don't see that coming anytime soon... So I've decided make from tripas corazón and start publishing code more consistently, more often.
I've opened up, together with Beto Brealey, a google code repository for all the new stuff. Our code folders hosted here, on rojored.com, were becoming unruly: difficult to publish, difficult to correct, and difficult to deprecate when the time came.
We've vowed to keep the source code clean and documented. Definitely it'll be unstable, but at least it won't look ugly. We've decided to go the zen-ish path of the egoless coder that will try to dissapear and become transparent to let the code shine through.... that meaning mostly that we've decided to follow the Flex sdk coding conventions as closely as we can, whatever it says; no idiosyncratic bracket "buts" or signature whitespace layout. We've discussed that the closest our code gets to the framework's, the better.
So, from now on, I'd suggest you check there first before downloading any stuff from old things posted here. The saveable stuff should be there anyways. It's just to prevent link rot that I'll keep what was added here before.
BTW, Google doesn't seem yet to host code with the license I'd been releasing it with until now, so MIT license will have to do for the time being.