-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
76 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| +++ | ||
| title = "London Perl & Raku Workshop 2024" | ||
| date = 2024-10-27T13:00:00+01:00 | ||
| draft = true | ||
| images = [] | ||
| tags = [] | ||
| categories = ["community"] | ||
| +++ | ||
|
|
||
| Yesterday we held the 2024 London Perl & Raku Workshop. It was the 20th aniversary of the conference, but it wasn't the 20th installment. The previous one was in 2019, just before Covid hit, and it has taken us five years to have another. People often write blog posts about the conference they have attended, talking about the talks they saw and the people they've met. I've never done that, but I'm going to try to do it, from an organiser perspective. | ||
|
|
||
| But before we start, I would like to give some context to what LPW means to me personally, as an elective Londoner who's now helped organise a few. | ||
|
|
||
| The fist LPW I attended was ten years ago. The tenth installment of LPW, at a time when Mark organised them on his own, I believe. That whole year was full of conference experiences for me. | ||
|
|
||
| I was the lead organiser of the German Perl Workshop in Hannover, I went to NLPW in Utrech, to YAPC::EU in Sofia, and it was only logical I should also go to LPW at the end of the year. While I'd been to the UK many times, including a few road trips, I'd never really been to London. And because I was stupid, I flew in in the morning and back out in the evening. No hotel. No pub. No social. It was exhausting, but I didn't know any better. The most imporant part of this was probably meeting Rick Deller in person, who would later convince me to move to the UK. | ||
|
|
||
| I returned in November 2017, to give [my first full-length conference talk](https://www.youtube.com/watch?v=jMYIwT5w4oY}} "About Us") at a conference. I'd run one before, I'd done lightning talks, but I'd never done a proper talk. At this point I'd already spoken to my now employer [Oleeo](https://oleeo.com) (then WCN) on the phone, and the talk became something like my job interview. The conversation that followed began with "when can you start?", and here I am now. | ||
|
|
||
| Naturally I volunteered to help with the 2018 installment, but only played a small role. I did a lot of on-the-day stuff, including the opening and anouncements, but not much in the run-up. In 2019 my role was more hands-on, but I didn't drive the conference either. | ||
|
|
||
| This year, Lee Johnson did most of the work. It was the two of us as the organiser team, but my work really only happened on the day. Lee did all the hard stuff, almost entirely on his own, from Switzerland. Lots of people thanked me for a great event, but I think my strength is being a good host. I can make people feel welcome. Lee deserves all of that credit for getting things going, and I'm very grateful for what he did this year. | ||
|
|
||
| Having said all of this, let's talk about LPW 2024. | ||
|
|
||
| We were in yet a new venue. The previous one was not available anymore, so we had to search. During the day, I heard a lot of positive feedback about The Trampery. People liked the vibe of the place, the layout, the lobby with its couches and comfy chairs, the cozy small rooms, and the fact they provided coffee throughout the day without disturbing us. | ||
|
|
||
| One piece of constructive feedback I got was that the Library room was too small for some of the talks, and that the TV was too small to see properly when the room was really full. I think this is something we could have solved with better scheduling the talks, putting that particular speaker into the large room instead. But this is only possible if people sign up early and mark which talks they want to attend, so there was very little we could do to change it on short notice, unfortunately, but we will remind people to indicate interest in talks in the run-up in the future. As for the TV, it would originally have been smaller, had the wall mounted TV not fallen off the wall and broken on Friday, as we were setting up. It missed Lee by inches, and it made a pretty loud bang. | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| <article> | ||
| <article id="{{ .Title | anchorize }}"> | ||
|
|
||
| <h1>{{ .Title }}</h1> | ||
|
|
||
|
|
||