This presentation will be about the challenges of building large Ruby web applications and how to maintain existing ones. I will use examples adapted from real applications that I worked on during my 10 years of experience with Ruby outlining: technical limitations of the language, how to use a modular dependency structure to enforce boundaries in complex domains.
Building modern eCommerce applications using Rails 7 #
With the newest Rails version, we can create platforms that offer the
modern features customers and sellers expect, with less complexity. Combine
it with an established open-source gem like Spree, and you've got a
comprehensive commerce system. I'll share my learnings from three real-life
examples: a music label selling limited edition vinyl LPs, a wholesaler
shedding enterprise SaaS for a tailor-made setup, and my furniture startup,
where CAD brings bespoke pieces to life.
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.
Flaky tests are awful, in this talk we'll explore why tests flake and look at
some techniques and tools you can use to discover why your tests are flaking.
What does the worst nuclear disaster ever have in common with a web application being down?
On the face of it, vanishingly little, but the incredible series of events before, during and
after the disaster have plenty of insights to teach us about more mundane situations
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 150 people. Even with such a high number, if you
register and realise you can't come, please use ticket tailor 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.
The phrase "Technical Strategy" is often used by senior leaders when they want
something from their tech teams. However, it's an unclear phrase that doesn't
explain what is needed or why. In this talk, you will learn what's behind the
phrase, but also how anyone from a CTO to a new developer can use that
knowledge to drive conversations that will help not just the leadership but
the whole organisation.
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 150 people. Even with such a high number, if you
register and realise you can't come, please use ticket tailor to give up your
place 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 quick dive into getting data-pagination (.csv, .json, .tsv
& .yaml files in your _data directory) working with the jekyll-paginate-v2
gem. After deciding that I wanted to archive my posts to a Slack
#music-we-like channel, I wanted to also make the archived posts
paginatible…
When an engineer joins your organisation, how long does it take for
them to configure their development environment? I will discuss using
devcontainers with VSCode to reduce this time from "days" to
"minutes''.
I'd like to do a whistlestop tour of a few different gems I've written over
the years, with the aim of talking about having fun whilst learning what
ruby is capable of. I'd like to showcase things like aspectual
for bringing aspect oriented programming to ruby, cherry-pick
for when you miss import foo from bar, overload for when you
want to really have optional arguments do something different, and more!
More than 100 lines files are bad? Not if you have the right tools! Inline
your templates, JavaScript, business & controller logic for maximum
productivity!
Elevate your RSpec tests by questioning common DRY practices. Enter the GARY
method, where strategic repetition enhances test clarity and maintainability.
Resist premature refactoring and convoluted logic, leaving yourself with
clearer tests that document your code. Go ahead, repeat yourself.
Learn how the Dragonruby game engine makes game development faster and simpler for
everyone, from beginners to pros. Explore its key features, and jumpstart
your journey into the world of game creation.
Join us to transform your ideas into reality with ease!
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.
What comes after cloud computing? Cloud computing is convenient, ubiquitous and relatively cheap. But it also locks developers into proprietary solutions that make migrating to another provider or bringing your solutions back in-house difficult and expensive. If AWS, Google Cloud Computing, Azure and all the others are clouds, then we also need a sky. Researchers at Berkeley and other institutions have proposed sky computing: an interoperability layer that removes technological lock-in and enables multi cloud application development.
The talk takes a look under the hood of our Rails monolith, our Rails
Engines, and how we share code between them. It's a bit like a kitchen
experiment – blending the best of both worlds to enhance the Separation of
Concerns, while still keeping our favorite code recipes within reach. I'll
share our adventure of moving some Kafka infrastructure code from the main
Rails app into a local gem (with zero downtime!). Think of it as giving the
code a new home where it can be shared across our Rails Engines. We've also
managed to preserve our unique, in-house testing infrastructure in the
process which is a serious Brucie bonus!
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.
