we're back with another remote-friendly Ruby User Group! The time is 19:00 CET so that's 18:00 UTC or well 6pm UTC.
You're welcome wherever you're from as long as you adhere to our Code of Conduct - the meetup is in English.
Current schedule is two ~20min talks including Q&A, followed by splitting the audience into smaller groups for virtually hanging out (optional) :)
Joining the meetup
Meeting ID: 998 4414 3955
The meetup will be on zoom and it will be recorded
- if you don't want your video to be visible to others, then turn it off/leave it off
- if you can't make it/don't want to be on zoom, watch the recording!
We're aware of the privacy concerns surrounding zoom and we share them. We're looking for better tools, we haven't found them yet.
Meanwhile, if you don't want to use the desktop client the zoom browser link above should work for you. If it doesn't you can usually get to it like this: the join link should also show a tiny join from browser link at the bottom of the window. It doesn't appear to require an account anymore. If the link doesn't show up, open the Download and Install Zoom link in a separate tab, that should make the link appear. Dark UI patterns 😖
Participating in the meetup
- We'll take Q&A questions in Zoom via the raise hand feature (click on participants, there's a little raise hand link)
- There is also a #rugb-live channel in the Ruby Berlin Slack, you can join the slack here
- the socializing part is optional, naturally, our aim is to not lose that part of our meetup - we'll try to use Zoom's breakout feature to split you into random groups and give you some ice breaker questions to kick it off
Your feedback is very welcome. Things will go wrong, we'll try to fix them.
Hopefully, See you soon. Amr, Pascal & Tobi
We've been using Turbo Streams in production for more than 6 months now. I'd like to share my experience about this simple yet powerful framework that can be a solid alternative to JS-rich frameworks. I'll be talking about some of the things that weren't exactly straightforward, how you can scale it, and how to write tests.
As Ruby developers, we have the good fortune of living in a world where "the code is the documentation", as well-written Ruby is very readable even to the layperson. However, since software and teams grow over time, knowledge can get lost and code can become cryptic. Let's have a look at the basic documentation tools at our disposal, the gaps and where we can borrow ideas from other eco systems and languages.
Alain Mauri - be nice