<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gábor Szabó on Medium]]></title>
        <description><![CDATA[Stories by Gábor Szabó on Medium]]></description>
        <link>https://medium.com/@szabgab?source=rss-31310cace66e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GdbfznPq7j8pjAHzp4CHhA.jpeg</url>
            <title>Stories by Gábor Szabó on Medium</title>
            <link>https://medium.com/@szabgab?source=rss-31310cace66e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:57:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@szabgab/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Issue #746–2025–11–10 — YAPC::Fukuoka 2025]]></title>
            <link>https://medium.com/cultured-perl/issue-746-2025-11-10-yapc-fukuoka-2025-b2af2534694d?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2af2534694d</guid>
            <category><![CDATA[perl]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Mon, 10 Nov 2025 20:38:03 GMT</pubDate>
            <atom:updated>2025-11-10T22:02:44.024Z</atom:updated>
            <content:encoded><![CDATA[<h3>Perl Weekly Issue #746–2025–11–10 — YAPC::Fukuoka 2025</h3><p>Hi there,</p><p><strong>YAPC::Fukuoka 2025</strong> is happening on 14–15 Nov 2025.</p><p>I’m also excited about <strong>LPW 2025</strong>. From our latest update from the organisers, the event is moving forward. They’re making every effort to ensure it happens, which is no small feat given the short notice. What’s particularly remarkable is that they’re managing this with just a two-person team.</p><p>They truly need our support, so please do reach out if you can help. The organisers are currently seeking sponsors, volunteers and speakers. I’ve tentatively submitted a talk proposal myself.</p><p>Hopefully, I’ll see you all at the event. The venue is expected to be confirmed this week. For the latest updates, please check the <a href="https://londonperlworkshop.com/">website</a>.</p><p>Enjoy the rest of the newsletter.</p><p>Mohammad Sajid Anwar</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*KPs6V2k87_ZMihzV.png" /></figure><p><strong>Announcements</strong></p><p><a href="https://yapcjapan.org/2025fukuoka/"><strong>YAPC::Fukuoka 2025</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fyapcjapan.org%2F2025fukuoka%2F&amp;title=YAPC%3A%3AFukuoka%202025">Share</a></p><p>by <a href="https://blogs.perl.org/users/olaf_alders/">Olaf Alders</a> (<a href="https://metacpan.org/author/OALDERS">OALDERS</a>)</p><p>It’s a 2-day event, 14–15 Nov 2025. YAPC::Fukuoka 2025 will be the first time the event is held in Kyushu since YAPC::Fukuoka 2017 HAKATA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*0NUHGdZeWSToX6oB.png" /></figure><p><strong>The corner of Gabor</strong></p><p>A couple of entries sneaked in by Gabor.</p><p><a href="https://luma.com/perl-maven"><strong>Adding tests to legacy Perl code</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fluma.com%2Fperl-maven&amp;title=Adding%20tests%20to%20legacy%20Perl%20code">Share</a></p><p>by <a href="https://szabgab.com/">Gabor Szabo</a> (<a href="https://metacpan.org/author/SZABGAB">SZABGAB</a>)</p><p>Online live-coding event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*BpDwwiiFkAkDTX6o.png" /></figure><p><strong>Articles</strong></p><p><a href="https://bbrtj.eu/blog/article/bitcoin-crypto-4-released"><strong>Implementing Bitcoin in a dead language</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fbbrtj.eu%2Fblog%2Farticle%2Fbitcoin-crypto-4-released&amp;title=Implementing%20Bitcoin%20in%20a%20dead%20language">Share</a></p><p>by <a href="https://brtastic.xyz/">Bartosz Jarzyna</a></p><p>An exceptional piece of technical writing that balances satire, technical depth and human vulnerability while showcasing significant software engineering accomplishment. It now implements BIP340 (Schnorr signatures), BIP341 (spending rules) and BIP342 (script validation).</p><p><a href="https://blogs.perl.org/users/mauke/2025/11/a-polymorphic-quine.html"><strong>A polymorphic quine</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fblogs.perl.org%2Fusers%2Fmauke%2F2025%2F11%2Fa-polymorphic-quine.html&amp;title=A%20polymorphic%20quine">Share</a></p><p>by <a href="https://blogs.perl.org/users/mauke/">Lukas Mai</a> (<a href="https://metacpan.org/author/MAUKE">MAUKE</a>)</p><p>An exceptional deep dive into esoteric programming concepts that demonstrates profound computer science knowledge and creative problem-solving.</p><p><a href="https://theweeklychallenge.org/blog/aws-s3-bucket-events"><strong>AWS S3 Bucket Events</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Ftheweeklychallenge.org%2Fblog%2Faws-s3-bucket-events&amp;title=AWS%20S3%20Bucket%20Events">Share</a></p><p>by <a href="https://manwar.org/">Mohammad Sajid Anwar</a> (<a href="https://metacpan.org/author/MANWAR">MANWAR</a>)</p><p>Back to my favourite topic: AWS. In this post, I show how to tackle S3 bucket events using AWS Lambda.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*DXpDmmE7YKYfD_H5.png" /></figure><p><strong>CPAN</strong></p><p><a href="https://metacpan.org/pod/App::Test::Generator"><strong>App::Test::Generator</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fmetacpan.org%2Fpod%2FApp%3A%3ATest%3A%3AGenerator&amp;title=App%3A%3ATest%3A%3AGenerator">Share</a></p><p>by Nigel Horne</p><p>This is a major improvement of the fuzz testing framework, a building tool that automatically generates comprehensive test suites from formal specifications.</p><p><strong>Grants</strong></p><p><a href="https://news.perlfoundation.org/post/pevans_core_dev_october_2025"><strong>PEVANS Core Perl 5: Grant Report for October 2025</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fnews.perlfoundation.org%2Fpost%2Fpevans_core_dev_october_2025&amp;title=PEVANS%20Core%20Perl%205%3A%20Grant%20Report%20for%20October%202025">Share</a></p><p><a href="https://news.perlfoundation.org/post/maintaining_perl_tonyc_october_2025"><strong>Maintaining Perl (Tony Cook) October 2025</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fnews.perlfoundation.org%2Fpost%2Fmaintaining_perl_tonyc_october_2025&amp;title=Maintaining%20Perl%20(Tony%20Cook)%20October%202025">Share</a></p><p><strong>The Weekly Challenge</strong></p><p><a href="https://theweeklychallenge.org/">The Weekly Challenge</a> by <a href="https://manwar.org/">Mohammad Sajid Anwar</a> 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.</p><p><a href="https://theweeklychallenge.org/blog/perl-weekly-challenge-347"><strong>The Weekly Challenge — 347</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Ftheweeklychallenge.org%2Fblog%2Fperl-weekly-challenge-347&amp;title=The%20Weekly%20Challenge%20-%20347">Share</a></p><p>by <a href="https://manwar.org/">Mohammad Sajid Anwar</a> (<a href="https://metacpan.org/author/MANWAR">MANWAR</a>)</p><p>Welcome to a new week with a couple of fun tasks “Format Date” and “Format Phone Number”. If you are new to the weekly challenge, then why not join us and have fun every week? For more information, please read the <a href="https://theweeklychallenge.org/faq">FAQ</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*jR3JK07DRW2AGMFw.png" /></figure><p><a href="https://theweeklychallenge.org/blog/recap-challenge-346"><strong>RECAP — The Weekly Challenge — 346</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Ftheweeklychallenge.org%2Fblog%2Frecap-challenge-346&amp;title=RECAP%20-%20The%20Weekly%20Challenge%20-%20346">Share</a></p><p>by <a href="https://manwar.org/">Mohammad Sajid Anwar</a> (<a href="https://metacpan.org/author/MANWAR">MANWAR</a>)</p><p>Enjoy a quick recap of last week’s contributions by Team PWC, dealing with the “Longest Parenthesis” and “Magic Expression” tasks in Perl and Raku. You will find plenty of solutions to keep you busy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/80/0*x-B_zpaZGvY3489w.png" /></figure><p><a href="https://deadmarshal.blogspot.com/2025/11/twc346.html"><strong>TWC346</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fdeadmarshal.blogspot.com%2F2025%2F11%2Ftwc346.html&amp;title=TWC346">Share</a></p><p>by Ali Moradi</p><p>For The Weekly Challenge, this is a strong, organised solutions post. Working code for both challenges is provided by Ali, who exhibits a straightforward and useful approach to problem-solving. The answers are clear and accurate.</p><p><a href="https://raku-musings.com/parenthesised-magic.html"><strong>Parenthesised Magic</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fraku-musings.com%2Fparenthesised-magic.html&amp;title=Parenthesised%20Magic">Share</a></p><p>by Arne Sommer</p><p>This blog post is technically sound, informative and well-written. It successfully illustrates a typical Raku problem-solving technique: beginning with a simple, imperative approach and then refining it into a more idiomatic, succinct and potent functional solution.</p><p><a href="https://www.braincells.com/perl/2025/11/perl_weekly_challenge_week_346.html"><strong>Perl Weekly Challenge: Week 346</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.braincells.com%2Fperl%2F2025%2F11%2Fperl_weekly_challenge_week_346.html&amp;title=Perl%20Weekly%20Challenge%3A%20Week%20346">Share</a></p><p>by Jaldhar H. Vyas</p><p>Jaldhar doesn’t just provide solutions but explores multiple approaches for each problem, analysing trade-offs between readability, performance and idiomatic style. The post is rich with technical insights, performance benchmarks and clever algorithmic thinking, making it both educational and intellectually stimulating.</p><p><a href="https://github.sommrey.de/the-bears-den/2025/11/07/ch-346.html"><strong>Magic Parentheses</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fgithub.sommrey.de%2Fthe-bears-den%2F2025%2F11%2F07%2Fch-346.html&amp;title=Magic%20Parentheses">Share</a></p><p>by Jorg Sommrey</p><p>This is an excellent, technically complex post that demonstrates sophisticated Perl programming methods. Jorg exhibits a thorough understanding of mathematical optimisation, regex engines and effective algorithm design.</p><p><a href="https://fluca1978.github.io/2025/11/07/PerlWeeklyChallenge346.html"><strong>really not inspired!</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Ffluca1978.github.io%2F2025%2F11%2F07%2FPerlWeeklyChallenge346.html&amp;title=really%20not%20inspired!">Share</a></p><p>by <a href="http://fluca1978.blogspot.com/">Luca Ferrari</a></p><p>Welcome back, Luca, after the break. Nice hack about tracking nesting levels in Raku.</p><p><a href="https://wlmb.github.io/2025/11/02/PWC346/"><strong>Perl Weekly Challenge 346</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fwlmb.github.io%2F2025%2F11%2F02%2FPWC346%2F&amp;title=Perl%20Weekly%20Challenge%20346">Share</a></p><p>by W Luis Mochan</p><p>This is an excellent technical blog post that demonstrates deep algorithmic creativity and strong problem-solving skills. It’s a genuinely novel approach that demonstrates deep understanding of the problem domain rather than just implementing standard algorithms.</p><p><a href="https://github.com/MatthiasMuth/perlweeklychallenge-club/tree/muthm-346/challenge-346/matthias-muth#readme"><strong>Recursive Parentheses — But no Recursive Magic</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fgithub.com%2FMatthiasMuth%2Fperlweeklychallenge-club%2Ftree%2Fmuthm-346%2Fchallenge-346%2Fmatthias-muth%23readme&amp;title=Recursive%20Parentheses%20-%20But%20no%20Recursive%20Magic">Share</a></p><p>by Matthias Muth</p><p>This is a solid and insightful write-up by Matthias — concise, technically sound and pedagogically clear.</p><p><a href="https://packy.dardan.com/b/dX"><strong>Whoa-oh-oh! Sing about parens!</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fpacky.dardan.com%2Fb%2FdX&amp;title=Whoa-oh-oh!%20Sing%20about%20parens!">Share</a></p><p>by <a href="https://blogs.perl.org/users/packy_anderson/">Packy Anderson</a> (<a href="https://metacpan.org/author/PACKY">PACKY</a>)</p><p>This is a superb technical blog post that exhibits profound pedagogical understanding and remarkable programming proficiency in several languages.</p><p><a href="http://ccgi.campbellsmiths.force9.co.uk/challenge/346"><strong>(Magic)</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=http%3A%2F%2Fccgi.campbellsmiths.force9.co.uk%2Fchallenge%2F346&amp;title=(Magic)">Share</a></p><p>by Peter Campbell Smith</p><p>This post blends practical implementation knowledge with sophisticated algorithms. Peter demonstrates a solid foundation in computer science and carefully weighs the pros and cons of various strategies.</p><p><a href="https://blog.firedrake.org/archive/2025/11/The_Weekly_Challenge_346__All_Aboard_The_Magic_Parenthesis.html"><strong>All Aboard The Magic Parenthesis</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fblog.firedrake.org%2Farchive%2F2025%2F11%2FThe_Weekly_Challenge_346__All_Aboard_The_Magic_Parenthesis.html&amp;title=All%20Aboard%20The%20Magic%20Parenthesis">Share</a></p><p>by <a href="https://blog.firedrake.org/">Roger Bell West</a> (<a href="https://metacpan.org/author/FIREDRAKE">FIREDRAKE</a>)</p><p>This is a solid, practical technical blog post that demonstrates good problem-solving skills across multiple languages.</p><p><a href="https://dev.to/simongreennet/weekly-challenge-longest-expression-b8b"><strong>Longest Expression</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fdev.to%2Fsimongreennet%2Fweekly-challenge-longest-expression-b8b&amp;title=Longest%20Expression">Share</a></p><p>by Simon Green</p><p>Both tasks are implemented correctly, pedagogically and safely. The code favours clarity and correctness over performance, which makes sense for a challenge-focused context.</p><p><strong>Rakudo</strong></p><p><a href="https://rakudoweekly.blog/2025/11/03/2025-44-jimmy-wales-on-audrey-tang/"><strong>2025.44 Jimmy Wales on Audrey Tang</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Frakudoweekly.blog%2F2025%2F11%2F03%2F2025-44-jimmy-wales-on-audrey-tang%2F&amp;title=2025.44%20Jimmy%20Wales%20on%20Audrey%20Tang">Share</a></p><p>by Elizabeth Mattijsen (<a href="https://metacpan.org/author/ELIZABETH">ELIZABETH</a>)</p><p>This is a high-quality community newsletter that successfully serves both technical and social aspects of the Raku ecosystem. It demonstrates an active, thoughtful community with meaningful technical content and important community developments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/61/0*66H4IWgxxg5kASpu.png" /></figure><p><strong>Weekly collections</strong></p><p><a href="http://niceperl.blogspot.com/"><strong>NICEPERL’s lists</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=http%3A%2F%2Fniceperl.blogspot.com%2F&amp;title=NICEPERL%27s%20lists">Share</a></p><p>by <a href="http://niceperl.blogspot.com/">Miguel Prz</a> (<a href="https://metacpan.org/author/NICEPERL">NICEPERL</a>)</p><p><a href="https://niceperl.blogspot.com/2025/11/dlxxiii-9-great-cpan-modules-released.html">Great CPAN modules released last week</a>;<br><a href="https://niceperl.blogspot.com/2025/11/dcxviii-metacpan-weekly-report-dbdduckdb.html">MetaCPAN weekly report</a>.</p><p><strong>Events</strong></p><p><a href="https://luma.com/perl-maven"><strong>Perl Maven online: Adding tests to legacy Perl code</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fluma.com%2Fperl-maven&amp;title=Perl%20Maven%20online%3A%20Adding%20tests%20to%20legacy%20Perl%20code">Share</a></p><p>November 11, 2025</p><p><a href="https://paris.mongueurs.net/"><strong>Paris.pm monthly meeting</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fparis.mongueurs.net%2F&amp;title=Paris.pm%20monthly%20meeting">Share</a></p><p>November 12, 2025</p><p><a href="https://yapcjapan.org/2025fukuoka/"><strong>YAPC::Fukuoka 2025</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fyapcjapan.org%2F2025fukuoka%2F&amp;title=YAPC%3A%3AFukuoka%202025">Share</a></p><p>November 14–15, 2025</p><p><a href="https://www.londonperlworkshop.com/"><strong>London Perl and Raku Workshop</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.londonperlworkshop.com%2F&amp;title=London%20Perl%20and%20Raku%20Workshop">Share</a></p><p>November 29, 2025</p><p><a href="https://lu.ma/v90mkqj5"><strong>Toronto.pm — online — How SUSE is using Perl</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Flu.ma%2Fv90mkqj5&amp;title=Toronto.pm%20-%20online%20-%20How%20SUSE%20is%20using%20Perl">Share</a></p><p>December 6, 2025</p><p><a href="https://paris.mongueurs.net/"><strong>Paris.pm monthly meeting</strong></a></p><p><a href="https://perlweekly.com/#twitter">Twitter</a> <a href="https://perlweekly.com/#facebook">Facebook</a> <a href="https://perlweekly.com/#email">Email</a></p><p><a href="https://www.addtoany.com/share#url=https%3A%2F%2Fparis.mongueurs.net%2F&amp;title=Paris.pm%20monthly%20meeting">Share</a></p><p>December 10, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2af2534694d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cultured-perl/issue-746-2025-11-10-yapc-fukuoka-2025-b2af2534694d">Issue #746–2025–11–10 — YAPC::Fukuoka 2025</a> was originally published in <a href="https://medium.com/cultured-perl">Cultured Perl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up CI with Jenkins is easy]]></title>
            <link>https://medium.com/daily-standup/setting-up-ci-with-jenkins-is-easy-d3da17dd955a?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3da17dd955a</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[jenkins]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Wed, 25 Apr 2018 12:40:26 GMT</pubDate>
            <atom:updated>2018-04-25T12:41:36.939Z</atom:updated>
            <content:encoded><![CDATA[<p>Well, it has its own quirks and you can waste quite some time until your find your way around the UI, but that’s not the difficult part.</p><p><strong>The difficult part is</strong> taking a project that has many parts and changing it so the CI system can handle it.</p><p>In many cases people are used to compile their code on their own machine using their IDE. We need to be able to compile the code using the command line only.</p><p>We cannot rely on someone installing the correct version of all the dependencies. We need to be able to that using a command on the command line.</p><p>If there is a database behind the application then we need to be able to have a similar database for the automated testing.</p><p>If we need specialized hardware we need to be able to access such a devices from the CI machine and make sure our processes don’t interfere.</p><p>All the above will require cooperation among front-end and back-end developers, sysadmins, DBAs, etc. Not an easy task.</p><p>Most importantly it will require a change in the <strong>culture</strong> of the organization to maintain the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/185/1*YsOKMA7JfUAep_0aTZSMGA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3da17dd955a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daily-standup/setting-up-ci-with-jenkins-is-easy-d3da17dd955a">Setting up CI with Jenkins is easy</a> was originally published in <a href="https://medium.com/daily-standup">Daily Standup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The layers of DevOps — Build system]]></title>
            <link>https://medium.com/daily-standup/the-layers-of-devops-build-system-e7dfb358b2fb?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7dfb358b2fb</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[build-system]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[compilers]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Tue, 24 Apr 2018 17:32:33 GMT</pubDate>
            <atom:updated>2018-04-24T17:32:33.093Z</atom:updated>
            <content:encoded><![CDATA[<p>There is this new client of mine that has a very successful business, but they still release software after the compiled and created a release on the desktop computer of on of the developers.</p><p>Something I managed to eradicate in my first real job back in 1994.</p><p>How do you get from here to some reasonable level of automation?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQaWYwirQbcjuFEw99Bp8Q.jpeg" /></figure><ul><li>Luckily they already us Git for version control so we probably won’t need to tackle that issue, but who knows. Do they use it in a way that makes it easy to create builds or is there some strange thing going on? Do they have one single Git repository or many small ones? Do they use branches? We’ll find it out.</li><li>Start by setting up a machine running <a href="https://jenkins.io/">Jenkins</a>. For this we need a machine, possibly <strong>support from the sysadmin team</strong>. It can be any machine local or in the cloud, physical or VPS, but it must be able to access the Version Control System which might limit the location of it as we probably won’t want to create a hole in the Firewall of the company.</li><li>Create a Jenkins project that will notice every push to the central Git repository. If this can be done by a trigger that’s great. If not then let Jenkins poll the server. (For the former we need to enable the server running the Git repository to be able to reach our Jenkins server which might be problematic if Jenkins sits on our private network.) This will create a working directory with the specific version of the project checked out on the Jenkins server. (Well, actually we could set up other servers that will act as workers for Jenkins, but for now we stick to one machine.) Here we’ll need <strong>help from the people who have admin rights on the Git repository</strong>.</li><li>Create a command line tool, a script, a collection commands that can compile the code if it is necessary. This will already require a lot of <strong>interaction with the developers</strong> and potentially it will need some work on their part to change they way the code works. Earlier they might have relied on features of their IDE or some other GUI-based tool that might not be available on the command line. For this we’ll need to figure out if the Operating System the compilation requires can be the same we used for the Jenkins server or something else. For example, do we need Mac OSX for a OSX or iOS based project? Do we need a Windows machine for something? For this we might need to set up another machine as the worker machine of Jenkins.</li></ul><p>Image from <a href="https://www.pexels.com/photo/architecture-building-construction-daylight-534220/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7dfb358b2fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daily-standup/the-layers-of-devops-build-system-e7dfb358b2fb">The layers of DevOps — Build system</a> was originally published in <a href="https://medium.com/daily-standup">Daily Standup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering Practices vs Agile Techniques]]></title>
            <link>https://medium.com/daily-standup/engineering-practices-vs-agile-techniques-e645cfb901f5?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e645cfb901f5</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Mon, 23 Apr 2018 07:46:38 GMT</pubDate>
            <atom:updated>2018-04-23T08:45:33.569Z</atom:updated>
            <content:encoded><![CDATA[<p>Reading the <a href="https://explore.versionone.com/state-of-agile/versionone-12th-annual-state-of-agile-report">12th State of Agile</a> we can see the practices listed there divided into two groups: Agile Techniques and Engineering Practices.</p><p>The most commonly used Agile Technique is The Daily Standup, but it also includes things like Sprint planning, Sprint reviews, Retrospectives, <a href="https://en.wikipedia.org/wiki/Kanban_(development)">Kanban</a>, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eqmCI3rkkiS6zkwLO2E7SQ.jpeg" /></figure><p>The Engineering practices include things like Unit testing, Coding standards, Continuous Integration and similar items.</p><p>I’d say the Agile Techniques are mostly about management while the Engineering Practices are mostly about, well, engineering. That is Development and QA if you really want to separate those two.</p><p>Recommended reading today: Download the pdf version of the <a href="https://explore.versionone.com/state-of-agile/versionone-12th-annual-state-of-agile-report">12th State of Agile</a> and flip through it. It will give you quite a few ideas to think about.</p><p>Image from <a href="https://www.pexels.com/photo/full-frame-shot-of-abstract-pattern-249798/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e645cfb901f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daily-standup/engineering-practices-vs-agile-techniques-e645cfb901f5">Engineering Practices vs Agile Techniques</a> was originally published in <a href="https://medium.com/daily-standup">Daily Standup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started is Easy]]></title>
            <link>https://medium.com/daily-standup/getting-started-is-easy-52a320ddf17d?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/52a320ddf17d</guid>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Sun, 22 Apr 2018 12:53:46 GMT</pubDate>
            <atom:updated>2018-04-23T08:32:15.816Z</atom:updated>
            <content:encoded><![CDATA[<p>Getting Started with a new publication and with a new projects is easy. Sustaining it is hard.</p><p>The same is true with Software Development. You can create an application fairly easily. There are tons of tools out there that will help you do that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SaLSZvJta1if0qPwonP4BA.jpeg" /></figure><p>Making it do something marginally useful is also not very difficult.</p><p>The real difficulty starts as you make progress and you want to make changes without breaking the features that already worked earlier.</p><p>It is much harder to keep adding new features at a pace you had at the beginning.</p><p>You might have code that is not well designed. You might have no tests to help you verify that everything works fine.</p><p>How can you get from a working project that is hard to maintain to one that is easy to maintain and it is still working?</p><p>In the <strong>Daily Standup</strong> I’ll bring you a short article every week referencing other, more interesting articles to help you make a little improvement to yourself and your Engineering team.</p><p>BTW The flamingos are from <a href="https://www.pexels.com/photo/flock-of-white-flamingoes-710802/">here</a> and the running lady is from <a href="https://www.pexels.com/photo/healthy-person-woman-sport-4078/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52a320ddf17d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daily-standup/getting-started-is-easy-52a320ddf17d">Getting Started is Easy</a> was originally published in <a href="https://medium.com/daily-standup">Daily Standup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interviewing Open Source developers — what is the focus?]]></title>
            <link>https://medium.com/@szabgab/interviewing-open-source-developers-what-is-the-focus-3188361e3475?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3188361e3475</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[newbie]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Fri, 21 Oct 2016 08:49:54 GMT</pubDate>
            <atom:updated>2016-10-21T08:49:54.788Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been running the <a href="https://code-maven.com/cmos">Code Maven Podcast and video interview series</a> for two month now and it feels that Open Source is a bit wide of a subject.</p><p>So where should this lead me? There are podcasts that focus on specific languages, such as <a href="https://talkpython.fm/">Talk Python to Me</a>, <a href="https://devchat.tv/ruby-rogues">Ruby Rouges</a>, and <a href="https://devchat.tv/js-jabber">JavaScript Jabber</a>, there are generic Open source podcasts such as the <a href="https://twit.tv/shows/floss-weekly">FLOSS Weekly</a> and <a href="http://changelog.com/podcast/">Changelog</a>, and then there is the <a href="http://www.codenewbie.org/podcast">Codenewbie</a> which emphasize the experience of people new to programming or software development.</p><p>So where do I go from here?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3188361e3475" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with Jason Crome on Perl Dancer 2]]></title>
            <link>https://medium.com/@szabgab/interview-with-jason-crome-on-perl-dancer-2-2c12ffb01d2a?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c12ffb01d2a</guid>
            <category><![CDATA[perl]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[podcast]]></category>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Thu, 25 Aug 2016 11:54:44 GMT</pubDate>
            <atom:updated>2016-08-25T18:28:02.423Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://perldancer.org/">Perl Dancer</a> is a modern web framework. In <a href="http://code-maven.com/cmos-1-jason-crome-perl-dancer2">this interview</a> I talked to Jason Crome one of the developers of Dancer 2.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c12ffb01d2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello Medium]]></title>
            <link>https://medium.com/@szabgab/hello-medium-859abc069373?source=rss-31310cace66e------2</link>
            <guid isPermaLink="false">https://medium.com/p/859abc069373</guid>
            <dc:creator><![CDATA[Gábor Szabó]]></dc:creator>
            <pubDate>Thu, 25 Aug 2016 11:43:05 GMT</pubDate>
            <atom:updated>2016-08-25T11:43:05.445Z</atom:updated>
            <content:encoded><![CDATA[<p>So I was tricked into signing up to Medium. Let’s see what can I do here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=859abc069373" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>