Back to YAPC 2006
Monday
Presto - Automagic Object Storage
you register your class with the presto object and call "save" on it.
call find on the presto object to get the thingy back.
it's not backed by a RDBMS, nor does it do relationships. Poop.
Holy moses, it's backed by DBM. Fine. let's just go back to '98.
Hmm, uses Class::MOP, which looks nice. Method injection without working in the symbol table.
Looks like I should check out MOOSE, there's a talk tommorrow
Get out of technical Debt now - Andy Lester
technical debt is all that documentation, all those tests, all that *stuff* you should be doing to support your project that never get done.
This debt accrues interest, and eventually you can't get anything done.
The solution is simple, but hard. You just have to do it.
Less common ones to watch out for:
- clutter
- anything planned for later without a schedule
- any test failure/crash that you ignore
- code without comments - man we are thick in this
- Specialists, or bus-sensitive knowlege
- Jerks on your team
- Jerks in the management
- No coding standards
Novel fixes: *write a test script that fails tests if it sees XXX and TODO *use a bug tracker *use VC stuff *automate logwatching/backups/etc *automate code standards *Pick one at a time.
Future: Do not incur more debt - schdule documentation. Schedule tests. If you do - write it down right away. You never don't have time to sharpen your saw, it helps you cut faster!
JSAN, AJAX, WHATEVER!
if you don't do Ajax, you're dead. Keep that in mind.
JSAN is CPAN for JS. It's a repository and a library. The library gives you some perl-ish library use syntax.
watch out - browsers don't really cache xmlhttp requests, so you'll run the code and send the content over and over.
JSAN::ServerSide puts script tags into your doc in the appropriate order, allowing you to auto-satisfy dependencies and still serve static
There's some damned useful JSAN modules, such as:
- a port of Test::More for JS.
- an interface to dom events that is cross-browser and lets you stack events - no more onloadService!
- JS table sorting
- special effects
Watch out for:
- breaking the back button
- defying user expectations
- stupid UI
Perl::Critic for best practices - Chris Dolan
uses PPI.
Finds potential bugs, deviations from style standards.
can be written as tests something fierce
All the policies it tests for are implemented as pluggable modules. You can customize what it's looking for.
You can customize per-run the strictness of the policy - each policy has a severity and you can get the pedantic ones or just the dire ones.
Yikes. I think that this might be a gigantic investment to start now. I can't even imagine what the output would be like if we pointed this at the framework tools, never you mind anything legacy.