Mark Jensen

• Website: www.linkedin.com/in/fortinbras
• About: Getting there from here. CPANID: MAJENSEN

Recent Actions

• Posted REST::Neo4p catches up to Neo4j V4.0+ to That doesn't look work-related...

  For a long time (since 2012), REST::Neo4p has provided a way for Perlers to play, and even work, with the graph database Neo4j.

  Neo4j has made many changes and improvements in its server and its query langu…

• Posted Version Control - Just Do It to That doesn't look work-related...
  If you do any kind of programming that extends beyond one-liners, you need to version control your work...even if you are a lone wolf weekend warrior, like myself. Why? At least three reasons:

  • Safety. Version control backs up your code, plain and simple. Many options of course for …
• Commented on I translate "Modern Perl Writing Style" to English
  +1 - do tell!...
• Commented on Three things you must do
  Absolutely- what I did myself when I first started with VCS. Will include in the VC post....
• Commented on Writing the Perl I Want to See in Others
  Sidd- thanks; I wish I could more spend time over there....
• Commented on Writing the Perl I Want to See in Others
  Hey Ether-- thanks! Feeling encouraged by KWALITEEs above 100%, which I think is good, or perhaps GUD....
• Posted Three things you must do to That doesn't look work-related...

  Tired of being a Perl script-kiddie? There are three things you must start doing with your code.

  • Use version control
  • Write tests
  • Create distributions

  You say, "No need to waste my time, only people who work in teams need that."

  • Gues…
• Commented on Writing the Perl I Want to See in Others
  Shawn- thanks, was thinking about those just this morning. I will use them on my current distros and record the experience- cheers MAJ...
• Posted Writing the Perl I Want to See in Others to That doesn't look work-related...

  How many of you are in my shoes? There isn't much scope for Perl coding in your day job, so you find yourself furtively browsing Metacpan, checking the latest Perl Weekly on your lunch hour, and dream about getting beyond

Comment Threads

• Ether commented on Writing the Perl I Want to See in Others

  Also check out the reports at http://cpants.cpanauthors.org

  And when you're up to it, consider competing on http://onceaweek.cjmweb.net :)

• sidd.basu commented on Writing the Perl I Want to See in Others

  Mark,
  Agree with your sentiment about perl in bioinformatics. Also, really appreciate your contribution to BioPerl project.

• Yuki Kimoto commented on I translate "Modern Perl Writing Style" to English

  >You should add a section on using Perl::Critic and its script, perlcritic. This will tell you everything about a Perl script or module that is not compatible with PBP.

  I like PBP. but I don't like some of these. In my opinion, PBP is a little tight compared with current Perl trend.

  And PBP is too long for beginners to read when they start Perl programming. I wanted to provide short topic for beginners.

  >If you use the three argument open, you can use an array for the command of a pipe. This will bypass the shell interpretation of the command:

  In my opinion, p…

• Yuki Kimoto commented on I translate "Modern Perl Writing Style" to English

  >I would never ever recommend anyone, *especially* beginners, to use $@ directly.

  $@ is not bad. I always use $@, but I never have big troubles. People likely to deny $@, but $@ is not bad.

  
  

• Yuki Kimoto commented on I translate "Modern Perl Writing Style" to English

  >eval { ... }; if($@) { ... }

  This is correct syntax.

  eval {
  ...
  };

  if ($@) {

  }

  If eval is nested , $@ is maybe cleared, but you can save $@ to lexical variable when $@ is overwritten. This is edge case. Usually, $@ work well.

  Try::Tiny big problem is that we use return function transparently.

  I will recommend try { } catch { } syntax if this syntax is added to Perl core.