An exploration into the world of Software Versioning, with an emphasis on the RubyGems ecosystem. This talk will cover extreme real-world examples from Rubyland and beyond, including code examples, footguns and award winners, as well as tips for developers navigating version management. It will get quite technical, so bring your regex hard hat.
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
Please use the street address and not just the postcode if searching on Google Maps
On arrival you will then be registered with building security and will be permitted up to the 3rd floor via the lifts, where we will greet you and assign you a visitor’s badge, which you should wear at all times whilst in the building. You will be asked to present a photo ID so please come prepared.
The venue has a hard limit of 100 people. If you register and realise you
can’t come, please use tickettailor to give up your place so we can someone
else come in your place. We might be able to let in people on the night
who haven’t registered, but we can’t guarantee it.
Lately, there has been a lot of development in durable workflows in
Rails with tools like active_job_continuation and acidic_job.
stepper_motor is a
new tool allowing for identifiable, associable, orchestrated step
workflows for Rails applications - without gRPC, extra tools or data
stores. Let’s explore where such a system comes from, why every durable
execution system is secretly a DAG, and how the stepper_motor
architecture is informed by VFX software instead of the imperative
ActiveJob methods.
No Browser Required: Dynamic OpenGraph Images with Rails and Rust #
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a hard limit of 60 people. If you register and realise you
can’t come, please use eventbrite to give up your place so we can someone
else come in your place. We might be able to let in people on the night
who haven’t registered, but we can’t guarantee it.
The July 2025 meeting of LRUG will be on Monday the 14th of July, from 6:00pm
to 8:00pm (meeting starts at 6:30pm).
This time we’re being hosted by the lovely folk at Cleo in their offices, on Shoreditch High St.
This event follows a more workshoppy-format: bring a laptop if you can and work through the exercises with some fellow attendees. You won’t go hungry as thoughtbot will kindly be providing food/drinks.
Wish you worked with understandable and easily changeable
code? Practice fixing the incomprehensible in an interactive,
zero-background-required exercise on the career-changing topic of
refactoring.
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a hard limit of 60 people. If you register and realise you
can’t come, please use eventbrite to give up your place so we can someone
else come in your place. We might be able to let in people on the night
who haven’t registered, but we can’t guarantee it.
Service Objects in Ruby can feel a bit off to use, so I’ll share some
experiments insights on some pragmatic ways to make them work better by
shifting toward a more procedural approach.
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more informal,
please remember that still we consider it to be a part of the meeting and
covered by our code of conduct.
Our host for the meeting has a limit of 60 people, and we need to provide a
list of names to them for security purposes. So, to secure your place and not
be turned away at the door you need to register for your free ticket via
ticket tailor.
Judge.me Ground floor 44-46 New In Yard London EC2A 3EY
Note: that the main office door for the venue is on New Inn Yard, opposite the
coffee shop, but we’ll be going in through the entrance on Anning St which is
round the corner behind Tesco.
The venue has a limit of 60 people. If you register and realise you can’t come,
please use TicketTailor’s self-service
tools to give up your ticket
so someone else can come in your place. We might be able to let in people on
the night who haven’t registered, but we can’t guarantee it.
Exploring how Event Sourcing and Ruby can provide a cohesive programming
model where auditable data, durable workflows and reactive UIs are the default.
CoverageBook is a decade-old Rails codebase
which has seen at least one full internal rewrite.
Let’s have a walk through of perfectly “reasonable” decisions we made
at the time that we’re now unravelling, and the new Rails-y-ness we’re
using as we do it.
A no-nonsense exploration of integrating LLM capabilities into Ruby applications using ruby_llm and similar libraries, highlighting real-world use cases without the Silicon Valley hyperbole.
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a limit of 50 people. If you register and realise you can’t come, please use TicketTailor to give up your
ticket so someone else can come in your place. We might be able to let in
people on the night who haven’t registered, but we can’t guarantee it.
For years, React has been the go-to choice for building frontend applications
— but is it always the best solution? In this talk, I’ll share my journey from
working extensively with React to discovering Hotwire, a radically different
approach that enables dynamic applications without heavy JavaScript or complex
state management.
Rather than a theoretical comparison, I’ll walk through real-world examples,
demonstrating how I’ve implemented interactive features using Hotwire. I’ll
also discuss my experiences, the challenges I faced, and some surprising
discoveries along the way.
AI has many applications in our industry, we are just getting started.
In this talk, I’ll explore an approach to AI-powered observability
tooling that knows everything about you and your codebase.
I’ll demo some of the most recent tooling in AI-assisted development,
show you how to enrich an LLM with highly relevant contextual information and
display a little workflow that shows how to use AI to fix bugs faster as
they happen in production.
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a hard limit of 50 people. If you register and realise you can’t come, please use TicketTailor to give up your
ticket so someone else can come in your place. We might be able to let in
people on the night who haven’t registered, but we can’t guarantee it.
A review on what makes OOP such an effective paradigm to work in,
followed by a critical discussion on some of the newer design trends in
the Ruby space. We will discuss the concerns of relying too heavily on
these patterns, and alternative approaches.
In this talk, I recount and discuss how I refactored some legacy ruby
code using the Simple Design Dynamo and ideas from “Tidy First” to make
it more agile, and then, using Domain-Driven Design, take that agility
to the next level.
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a hard limit of 60 people. If you register and realise you can’t come, please use TicketTailor to give up your
ticket so someone else can come in your place. We might be able to let in
people on the night who haven’t registered, but we can’t guarantee it.
Our February meeting is our annual event devoted to short talks of no more
than 10 minutes.
We have space for at least 1 more talk, and it is our most popular event of the year. So, if you have been on the fence about giving a talk, there is no better opportunity than this. To put yourself on the map, email us at talks@lrug.org
Rails 8 + AI = Happy Life for Lazy Engineer to Create a Walking Skeleton #
Zhiqiang Bian says:
In this talk, I’ll explore how Rails 8, combined with AI-assisted
tools, can help engineers rapidly spin up a walking skeleton—a minimal
yet functional end-to-end system—with minimal effort.
Ruby is a high-level language, and there’s a general assumption that
it’s ill-suited to low-level shenanigans. But is this true?
In this lightning talk I’ll introduce some basic Ruby tools for
accessing low-level system features, concentrating on *nix platforms,
and see if it’s possible to replicate tenderlove’s Never Say Die gem
for recovering from segfaults.
Sustainability is important, but it’s also hard, especially when
building web projects. How do you know you’re doing it right? This
quick talk will explain a tool I made for self-assessments against the
Web Sustainability Guidelines, which you can use too!
When the talks come to an end we’ll decamp to a local pub for some food, some
drinks and some chat with your fellow attendees.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a hard limit of 75 people. If you register and realise you
can’t come, please use eventbrite to give up your place so we can someone
else come in your place. We might be able to let in people on the night
who haven’t registered, but we can’t guarantee it.
We are going to look into the essence of what DDD is and why it came to
be in plain English, without any consultant lingo. We will also
evaluate its advantages, indicators of the possibility of successful
adoption, and reasons to do so.
When the talks come to an end we’ll move to a nearby pub for some food, some
drinks and some chat with your fellow attendees. Usually when we’ve visited Canva this has been The George & Vulture on Pitfield Street.
Of course, even though this is the socialising part and seems more
informal, please remember that still we consider it to be a part of the
meeting and covered by our code of conduct.
The venue has a hard limit of 150 people. Even with such a high number, if you
register and realise you can’t come, please use TicketTailor to give up your
ticket so someone else can come in your place. We might be able to let in
people on the night who haven’t registered, but we can’t guarantee it.
