Static typing has many advantages that we miss out in dynamically typed Ruby code:

• It eliminates a whole category of errors.
• It helps onboarding new developers to your code base.
• It makes static analysis easier which allows better IDE support (method completion, argument hints and more)

Implementing static typing in Ruby is possible, but it comes with the downside of... having to type everything yourself.

During my master thesis I implemented Racer, a gem that traces all method calls during runtime (e.g. when running your automated tests) and generates RBS type signatures from those traces. In this talks I'd like to further explain the motivation, showcase the tool and explain how it works and what future developments may bring.

we would like to discuss whether we want to officially register Ruby User Group Dresden as a German registered association (eingetragener Verein, e.V.). We will also talk about the possibility of applying for non-profit status (Gemeinnützigkeit), which would require more organization and administrative effort but would provide tax benefits. As part of this process, we need to decide what to include in our statutes (Satzung), which define the rules and purpose of the association. Another important topic is whether to introduce a membership fee to cover group expenses such as printing materials, T-shirts, and services like our mailing account. This discussion will help us determine how we want to structure, finance, and grow our community in the future.

FactoryBot is flexible, but slow. Fixtures are fast, but confusing. The Oaken Gem promises to combine the best of both worlds: one-time loading, transaction rollbacks, named scenarios – and all in Ruby instead of YAML.

In this talk, we'll take a look at how Oaken works, compare it directly with FactoryBot, and discuss whether the approach is suitable for larger projects.