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:
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?
So today I asked the seemingly simple question of "What coding standards does the team go by?". I got "Coding standards?".
I got to look at the Perl code as well. It isn't too bad, though the no coding standards shows. It has its own logging system (I will introduce Log4perl or Log::Dispatch). It has its own configuration system (which I will replace with one of the Config:: modules).
They seem to be "half ass" (excuse my language) with both of those as well.
I am glad I like cleaning up code. : )
I have thought (and prayed) and I am jumping the chasm to being a full fledged programmer. I will initially be tasked with cleaning up some email parsing stuff using Perl (of course). Then I will be doing XML stuff ala some web services and possibly some Java with ArcGIS.
I am pretty stoked as I really love programming and I look forward to the growth this will certainly cause.
I don't have to change companies (which is good) just projects.
I have it on good information that I will be offered a job I interviewed for (same place different project). I will get to grown my meager Java skills (and I do actually like Java) and help maintain a system (in Perl) that parses email messages for ship positions world wide. I think maintain might mean clean up, refactor and stuff along those lines.
This will actually be a big step out from being an accidental programmer/systems admin to being a full time programmer. Needless to say I have butterflies already, and I haven't even been officially offered the job. I am very excited at the prospect of getting to program full time though.