Jens Berthold (maxhq)

• About: Coding in Perl for 10+ years, recently getting deeper into Modern Perl with a growing fascination of the programming freedom Perl gives us compared to other languages.

Recent Actions

• Commented on Writing Declarative Perl
  Nice and clear syntax! Very inspiring. Adding cash to the Wallet is the last step. Without knowing the exact mechanisms I guess there will be a problem if one of the first steps fails as FAILURE will then remove cash...
• Commented on Devops in the cloud with perl
  Correct link: www.youtube.com/watch?v=i9ZlcDNLIkg...
• Commented on Please don't use ::Tiny unless it meets the ::Tiny criteria, thanks!
  Hi Dan, I think that's a fair thing to say. But I feel in your vibrations :-P that you have particular modules in mind... Maybe you should name them so that the rest of us can take care when using...
• Posted Inline tests with Dist::Zilla to Jens Berthold (maxhq)

  I'd like to give my debut to the community with a small module whose code I snatched from someone else ;-) - Dist::Zilla::Plugin::Test::Inline.

  It's a plugin that integrates Test::Inline into Dist::Zilla by looking fo…

Comment Threads

• Ether commented on Please don't use ::Tiny unless it meets the ::Tiny criteria, thanks!

  > Maybe make a Dist::Zilla plugin to test for it all?

  https://metacpan.org/pod/Dist::Zilla::Plugin::OnlyCorePrereqs can check for one part of it. [Test::MinimumVersion] can test for another.
  

• Samuel Kaufman commented on Devops in the cloud with perl

  Whoops, lesson learned, don't hit publish on a moving train tethered to your phone's internet.

• john napiorkowski commented on Devops in the cloud with perl

  thanks sam!

• john napiorkowski commented on Devops in the cloud with perl

  Personally I'd love a strong Perl option for devops and deploy stuff.

• Pawel bbkr Pabian commented on Writing Declarative Perl

  Personally I find declarative programming very obfuscated for two reasons:

  1. Call to attempt() is outside Steps(). That is the very core of declarative programming - to separate process definition from its execution. But this leads to:

  2. Unclear SUCCESS/FAILURE triggering. "If Wallet( ... hasminimumcredits .. ) step is not met does that mean FAILURE should be triggered?". In this case obviously not - if there was no bet no funds should be taken from wallet. But this is way too blurry.