use Perl

There is the "standard" way to do Perl objects and there are these things called InsideOut objects that Object::InsideOut and Class::InsideOut help you with.

Do Perl programmers just stick with the "standard" or is InsideOut being used more?

I know there is Moose as well...

This is my blog. There are many like it, but this one is mine. It is my life. I must master it as I must master my life. Without me, my blog is useless. Without my blog, I am useless. My blog is human, even as I am human, because it is my life. Thus, I will learn it as a brother. I will learn its weaknesses and its strengths. I will keep my blog clean and ready, even as I am clean and ready. We will become part of each other.

A really good friend of mine was complaining about not feeling well yesterday. Today he is in a coma because of a brain tumor. Holy crap I have no idea sometimes.

Well, I interviewed with a Perl company in the DC area. They do mod_perl stuff and are pretty much a Perl only shop. It is a great opportunity to jump deeply in the Perl side. They use Perl and Debian plus some XEN stuff. I like the people I met, the company mission, the $$$ package (includes stock options). I just have to think about "the drive" to and from work. Oh and that would only be 3 days a week. I get to telecommute Tues and Thurs which works great for the family Tae Kwon Do work outs.

Think think think

I was curious as to what percentage of Perl'ers use POD for documenting their code. I was curious because I looked at the Template-Toolkit source and while there is POD after the __END__ there is also documentation in the code using normal # type comments. That seems redundant to me but is that the norm?

Also, is there a good "this is how you use POD" with examples (besides perlpod) somewhere?

I have started looking for smaller part-time work in Perl. I really need to push myself and learn as I don't have anyone to "harass" about Perl. I think I am pretty solid in the fundamentals and I have put up a couple commercial sites for friends.

I think I just need to close my eyes and jump.

I have been reading up on Maven2 for a project at work. It pretty much handles everything about a project (managing dependecies, documentation, tests etc.).

I wonder if something similar would benefit the Perl community or is there something out there that I don't know about or even "it is a bad idea".

This may be just me and if it is correct me please. I was looking at Config::JSON and thinking "this looks good". Then I look at its dependencies:

        Test::Perl::Critic
        Test::Pod::Coverage
        version
        JSON
        Test::Deep
        Test::Pod

JSON and version I can understand but why do I "have to have" those "Test::" modules to install the dang thing without forcing it?

I am just curious. I do not have formal education. I do like Perl though. Sometimes it is hard for me to wrap my head around how to do some things that "I" think should be easy. I recently changed projects to a Perl one where I will be maintaining some Perl and refactoring it. Is my path just reading reading reading and taking classes when time allows?

If you are not formally educated (meaning college) as a programmer what did you do?