[AmsterdamX-pm] Amsterdam eXpats Perl Mongers January meeting (January 25th, 18:30)

[Sawyer X]

Hi everyone!

This is just a reminder that today we're having a great AmsterdamX.pm
meeting with lots of crazy interesting talks. Don't miss out!!

On Fri, Jan 15, 2016 at 4:44 PM, Sawyer X <xsawyerx at gmail.com> wrote:
> This January we're getting lots of amazing speakers, including a guest
> speaker - Dana Jacobsen! Don't miss it!
>
> (Please let me know if you plan to come.)
>
> In a nutshell:
> Date: 25th, January Monday.
> Time: 18:30 - 20:30 (theoretically)
> Location: Booking.com, Herengracht 597, Amsterdam room on 1st floor.
>
> Talks:
>
> Mickey Nasriachi - PONAPI - The anti-bikeshedding tool for your REST API
>
> * Tired of arguing over how JSON responses should be formatted?
>
> * Come to my talk and I'll show you how you can avoid it.
>
> Gonzalo Diethelm - Devel::QuickCover - Quick & dirty code coverage for Perl
>
> * A lean and mean XS module that gathers runtime code coverage information
>
> * We will briefly describe how Perl uses an optree and how we can hook into
> it for our own nefarious purposes.
>
> * Then we will discuss the very simple implementation of Devel::QuickCover,
> which tracks what lines in each loaded Perl module are actually executed.
>
> * The talk will end with some real world instances of using
> Devel::QuickCover.
>
> Dana Jacobsen - Practical Cryptography
>
> * This talk will discuss cryptographic hashes, signing with DSA, encrypting
> with RSA, and random numbers.
>
> * Rather than discussing the theory and the hundreds of modules available,
> the focus is on a few good tools to get things done.
>
> Vikentiy Fesunov - Rust inside Perl
>
> * Rust is a new systems language with strong focus on memory safety.
>
> * It tries to help programmers write more correct code with as little
> runtime overhead as possible.
>
> * XS is an interface used by the perl interpreter to talk to native code,
> built on top of the C language.
>
> * This project's goal is to bring XS API to Rust and explore ways Rust can
> make development of well behaved perl extensions simpler.
>
>
> Unabridged:
> You've probably heard of the Perl Mongers meetings, where fellow Perl (and
> non-Perl) programmers can get together to "talk shop", make fun of
> everything (including Perl), and have a good time. These meetings often have
> a few technical talks (which are usually light-hearted, and not necessarily
> - but likely - involve Perl). There are already Amsterdam.pm meetings. This
> is not about those. This is about AmsterdamX.pm.
>
> The talks can be a 5 minute tidbit about a cool module, or a 40 minute
> tutorial about some cool new (or old) software.
>
> AmsterdamX.pm?
> AmsterdamX.pm (Amsterdam eXpats Perl Mongers) is a new Perl Mongers group
> whose purpose is to optimize for expats. The major differences are:
> * use English; We might speak more than 50 languages, but we commonly speak
> only one.
> * Meeting early: we meet at 18:30, so you can come straight from work
> instead of having a long buffer time to the meeting.
> * Held at Booking.com, where most Perl expats in Amsterdam already work.
>
> This isn't to replace Amsterdam.pm, but to provide an additional group. It
> is only meant to supplement.
>
> Why should I attend?
> Here are a few reasons which might appeal to you:
> * You will improve your knowledge of Perl (and most likely other
> technologies) through the knowledge and experience of others. It's like a
> free course, with snacks!
> * You could give a talk and share your knowledge and experience. If you're
> going to YAPC to give a talk, this is great practice.
> * It's a wonderful chance to socialize.
>
> How many talks, and how long are they?
> Usually there will be 2-3 talks, ranging between 5 minutes (lightning) and
> 40 minutes (tutorial).
>
> Is it just for Booking.com?
> No. This isn't Booking.pm, this is AmsterdamX.pm. (also, Sparta!)
> This means that everyone is invited! We suggest that people register so we
> could have a good estimate of the people arriving. This will help with
> various things like optimized snack distribution, making sure reception
> knows of people arriving that don't have keys, making sure we get a proper
> room, etc.
>
> Now I'm interested, what's the next step?
> Please let us know by return email if you will be attending as well as the
> names of anyone you plan on bringing from outside of Booking.com.
>
> Then mark the date, time and place, and show up!
>
> See you there!