After a lengthy break, Server-Side Talks are back with no less than three presentations! Get away from the gloomy November weather and join us in learning how you can create your own OAuth provider, how you can let your users set their own event schedules with Elixir and what agile can do for you when you are faced with real-world uncertainties. As always, there will be beer 🙂
Recently, I needed to add a “Download all” button in a Rails application for managing meeting assets. Specifically, this magic button would allow attendees to download all the meeting documents in a single zip file.
Sometimes you just need to send a lot of emails, and services that make it really simple can get too expensive. Here is how we sent an e-mail to all our users and what we learnt.
Where we look at lessons learned in monitoring and performance, and go through some things that seem simple at first, but turn out to be a bit more complex.
One of the most interesting for me features of the upcoming Ruby 2.7 is the syntax sugar for the method reference. I like using the #method method together with the #then (#yield_self) operator in order to compose several functions in a “pipeline” like fashion.
Refactoring has a specific meaning. When we misuse the word, we lose the ability to communicate an important concept. Let’s revisit what refactoring is and what it is not.
It can happen: sometimes you need to severely curtail access to a resource. Maybe you use a 3rd party API where you can only make one call at a time. To handle this extreme case, you need an extreme tool: a distributed lock.