This is "Through the Stack," a weekly list of links relating to topics relevant to Lead developers (actual or aspiring) working with an internet-related product. Many lead developers, tech lead, and staff engineers have their hands in many projects and influence many layers in their organizations. This publication aims to
After years of working on Ruby on Rails projects, Sinatra projects, and other non-standard projects and libraries, Ruby developers tend to have strong preferences in their gems choices. Here is our shortlist and why we picked those, sorted by themes. Hopefully, that will help you pick and choose a good
Over the years, I encountered Agile methodologies or their different implementations in as many teams. With time passing, it's interesting to live, hear and read about success and failures and the (often) inevitable push-pull between "business" and "engineering" when those are seen as different and in opposition. So this week,
Some time ago I decided to move all my audio episodes from Soundcloud to [Transistor](https://transistor.fm/). I wanted something that didn't cost too much, that I could still include in the Jekyll page and that would help a bit with publishing to whatever audience was reached.
Once a team has a stable and trusted way to get releases deployed quickly and potentially multiple times during a day it becomes very useful to have a way to switch features or changes ON and OFF in the production environment.
When it comes to doing SQL queries onto a relational database there is a time when this query needs to use rows from two tables to give you the rows you want. These are called “join” queries. Their purpose is to combines records from two tables, let's see how that can end up.
Often with RubyOnRails (and other Ruby frameworks) we rely on instance variables and the or-equals operator (||=) to store some expensive data in memory to avoid costly database or API queries : this is called memoization.
This is a little story about an oddity related to date handling and null values in MySQL that a teammate and I spotted when working with Sequel and a custom timestamp plugin.
An overview of Ruby background jobs solutions.
I have published a few posts about Ruby backends, AWS EC2 and using SNS/SQS in the past. Lately I have done and pushed some experiments further to use a lot more from AWS compute services rather than just hosting the services there.