You know, you could get the Perl Weekly right in your mailbox. Every Week.
Free of charge!
Just ONE e-mail each Monday. Easy to unsubscribe. No spam. Your e-mail address is safe.
Issue #745 - 2025-11-03 - Perl IDE Survey
latest | archive | edited by Gabor Szabo
This edition was made possible by the supporters of our cause.
Don't miss the next issue!
|
Hi there! First of all, apologies. Apparently last edition included a link the source of the Perl IDE survey and not the actual Perl IDE Survey itself. This week we hope to provide you with the correct link. The announcement about the London Perl Workshop might have also been a bit premature as it was still unclear if it will happen at all. I am still unclear about the exact situation, but this is an excellent opportunity for you to step up. Check out the web-site of LPW where you can find the names and the contact information of the organizers. Talk to them and offer your help. Any help. That will increase the chances for this to actually take place. We even received a special announcement exclusive to the readers of the Perl Weekly. I figured I need to update my web site and emphasize that I help companies deal with legacy code, and that made me think: What does 'legacy code' mean? How is it different from 'existing code' or 'code in production'? Is it a term use in a derogative manner? Does it mean 'code that is in use, but where the authors have disappeared'? Does it mean 'code that I am scared to touch'? Maybe 'code that still makes money, but we are unsure how it works, we need to make changes but we are scared to do'? I'd love to hear (well, read) what do you think about it. I know I could ask the AI overlord, but I am old-school and I prefer human intelligence. While we are figuring out how to define legacy code I thought I'll organize an online event in which we'll take a CPAN module and add some tests to it. Register here In any case, have a nice week! Gabor Szabo |
|
Announcements
|
After a long hiatus the Perl IDE Survey is back to another round. It will take you about 20 seconds to fill it. |
Articles
|
by Mohammad Sajid Anwar (MANWAR) OpenAPI has become the standard for designing, building and documenting RESTful APIs. However, ensuring your OpenAPI specifications are both syntactically correct and follow best practices can be challenging. OpenAPI::Linter brings comprehensive validation and linting capabilities directly into your Perl applications and development workflow, helping you catch issues before they impact your API consumers. | 
|
|
|
App::Test::Generator - Generate fuzz and corpus-driven test harnesses. This module takes a formal input/output specification for a routine or method and automatically generates test cases. |
The Weekly Challenge
The Weekly Challenge by Mohammad Sajid Anwar will help you step out of your comfort-zone. You can even win prize money of $50 by participating in the weekly challenge. We pick one champion at the end of the month from among all of the contributors during the month, thanks to the sponsor Lance Wicks.
|
by Mohammad Sajid Anwar (MANWAR) Welcome to a new week with a couple of fun tasks "Longest Parenthesis" and "Magic Expression". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ. |
|
|
by Mohammad Sajid Anwar (MANWAR) Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Peak Positions" and "Last Visitor" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. |
|
|
by Ali Moradi Code that is clear, effective and useful and that accurately addresses both issues. The solutions demonstrate good Perl fundamentals with straightforward algorithmic approaches. |
|
by Arne Sommer This is an excellent example of using Raku's special feature set to solve a problem in a stylish, understandable and effective manner. In addition to solving the problem, Arne uses it to illustrate why Raku is a delight for algorithmic and data-centric programming. It is a brilliant pedagogical move to go from a naive to an idiomatic solution. |
|
by Bob Lied Excellent practical Perl programming is demonstrated in this post, with an emphasis on readable, maintainable code that addresses the issue at hand directly. Bob takes a methodical, deliberate approach that is full of the kind of practical judgment that distinguishes good code from great code. The technical content is very interesting because of the conversational tone and cultural allusions. |
|
by Jaldhar H. Vyas Excellent approach to problem-solving that combines efficient debugging and logical reasoning. By pointing out edge cases, clearing up early misunderstandings and offering comprehensive explanations, Jaldhar exhibits strong analytical abilities. |
|
by Jorg Sommrey This is a thorough, engineering-focused in-depth analysis that places a premium on robustness, accuracy and beautiful API design. It is not merely a solution post. Jorg approaches the challenges with the rigor of a software engineer building production-grade code, not just solving puzzles. |
|
by W Luis Mochan A sophisticated, functionally-focused Perl solution that showcases complex programming methods like closures, iterators and functional composition. He tackles the problems with a thorough knowledge of Perl's functional programming features. |
|
by Matthias Muth Brilliantly idiomatic Perl that makes use of sophisticated language features to produce succinct, effective and ingenious solutions. Matthias exhibits a thorough comprehension of Perl's contemporary features and functional programming capabilities. |
|
by Packy Anderson (PACKY) This is a philosophical and pedagogical analysis of the Perl Weekly Challenge itself rather than a solution post. The difficulties serve as a starting point for more in-depth conversations about community, learning and the nature of programming expertise. |
|
by Peter Campbell Smith A simple, effective and useful Perl implementation that uses little code to accurately address both issues. Without superfluous abstraction or flourish, Peter concentrates on the fundamental algorithmic requirements. It is an example of "get the job done" programming. |
|
by Robbie Hatley A comprehensive, expertly designed set of solutions with a focus on robustness, extensive testing and unambiguous documentation. Robbie shows how to develop software in a methodical, quality-focused manner. |
|
by Roger Bell West (FIREDRAKE) A highly analytical and mathematically complex method that investigates the problems underlying structure. Beyond simple implementation, Roger explores mathematical properties, algorithmic complexity and sophisticated Raku idioms. |
|
by Simon Green A simple, useful implementation that puts accuracy and readability ahead of cunning. Simon is refreshingly honest about their comprehension of the issues and exhibits a methodical approach to problem-solving. |
|
by Vinod Kumar K A clear, useful Perl implementation that uses simple, readable code to accurately address both issues. Vinod exhibits solid Perl foundations and a pragmatic approach to problem-solving. |
Weekly collections
Events
