return HTML::br();
jeremy’s thoughts on developers who build from scratch vs. those that bring their own toolkits misses what i think is one big issue: how does each type of programmer fit into a larger team?
i would have serious qualms about hiring someone who had their pet framework that they used for building things. i think part of that comes from seeing so many half-witted frameworks. (anyone who has written a library or class to generate HTML with function, method, or object names like p and br deserves to be shunned.)
but perhaps i’m seeing three categorizations where jeremy sees two. i see people who build from scratch, those who seek out and use common frameworks and libraries from resources like PEAR and CPAN, and those who have built their own toolkits and frameworks. it’s the people at both ends that i worry about. of those three categorizations, i tend to wobble between the first and second.
i've seen a LOT of shit out there that people call their own framework. i agree about the example - WHAT??? who is still doing that? believe it or not, there are lots of shops still stuck in the CGI world that don't know any better. almost everything you are looking to do has been done on CPAN, and it's unlikely you're going to do it any better, unless the CPAN code happens to just suck (which hasn't happened that often). it takes a good programmer to know when NOT to reinvent the wheel.