They say that a week is a long time in politics – which must mean that in the world of technology, 23 years is a very long time ago indeed. It has indeed been more than two decades since Ruby appeared, but as Debbie Pearson notes in one of our featured posts for this Ruby Digest, a vibrant Rails community means the language is as fresh now as ever – and the items below are great examples of this…
Looking around for content to feature on Ruby Digest, there’s never any shortage to choose from. That’s great news, but the amount of information out there can be a little overwhelming; luckily, Paulo Santos is on hand with a roundup of the most important things to know.
Remember when buying software meant going to a store and dropping a large (but rather light) box into your shopping cart? We do, and we’re glad they’re over – Software as a Service (SaaS) offers a far better user experience. And RoR is a great framework within which to build it.
After months of meticulous testing, Rahul Mahale and his team recently moved to the production phase of a Ruby on Rails application that makes use of the Kubernetes cluster. Here he discusses how to set up path-based routing for apps like this one using HAProxy ingress.
Sometimes, unpopular things need to be said – but in a team environment, people can can be too shy to say them. Abot, a Slack Bot build in Rails, lets you reply anonymously to Slack conversations; here, developer Pawel Urbanek explains how he made his project profitable.
Memoization is simply the practice of reusing values after they have been calculated, and is now so widespread as to have become part of idiomatic Ruby. In an earlier post, Bradley Schaefer made an ‘off-hand’ reference to getting round the problem of using memoization for falsy values; here, he digs a little deeper.
Sending emails in Rails is easy, says Alessandro Rodi of Renuo AG – and yet, there are many simple errors that can lead to suboptimal performance. So, from using deliver_later, to implementing an effective testing regime, here’s how to do it right.
You’ve invested vast resources in establishing your knowledge base, building a team, attracting clients, and developing projects together. But as things finally near completion, how can you be sure that each and every part of what you’ve made is polished to perfection?
Suffering various annoyances with Sidekiq, developer Stanko Krtalić Rusendić decided to jump ship and try his luck with RabbitMQ instead. He hoped it would prove a more capable replacement – but in practice, it’s been even better than that.
Yield_self has been widely compared to Elixir’s pipe operator – but, says Derek Prior, while he uses and enjoys the pipe operator in Elixir, it can be rather difficult to imagine how yield_self might be used in Ruby code. But after a client project was updated to Ruby 2.5, this all changed.