I have been following the Elixir community and the Phoenix framework in particular. I feel a certain familiarity between Ruby and Elixir, and Rails and Phoenix. Chris McCord, the creator of Phoenix writes, a thoughtful post on the differences, and more importantly why they matter. Sometimes, differences in Software Engineering can be esthetic only (e.g. plural vs singular database table names); Not so with these. He makes compelling arguments on the technical choices made in Phoenix.
Mike Perham, the creator and maintainer of Sidekiq, explains how to go about making a business out of Open Source Software. Uncharacteristically for the internet, the comments for this post are actually very interesting, as are the links. For a more in-depth conversation into the same topic, hear (or read the transcript) of Mike’s guest appearance at the Ruby Rogues Podcast
SemVer, short for Semantic Versioning, is a convention for software version numbering. I have been using it very successfully at work with for internal gems and bundler pessimistic locking (
~>operator). In this post Richard Schneeman, explains the practical aspects of choosing a release number, including security releases.
Last Saturday (11/14/2015) I attended my first code retreat, hosted by the kind folks at Pluralsight. The event was part of the Global Day of Code Retreat. 144 cities participated in the event, and for the first time San Diego was one of them.
Materialized views are a way to cache the result of expensive database computations, right on the database. Used in the right manner, they can make speed up performance significantly. As with any other caching mechanism, there exists some caveats about invalidating the cache when underlying data changes. This guide shows how to leverage this database feature in a Rails app. Clear and to the point.
Richard Schneeman writes another insightful post on how to make Ruby applications better. In this case, he talks about how to identify memory leaks (as opposed to memory bloat) and different techniques to mitigate memory leaks. Plenty of good techniques discussed.
One of my favorite books, is Surely You’re Joking, Mr. Feynman!, by Nobel-prize winning physicist Richard Feynman, a collection of anecdotes from his life, in which is unique way of viewing the world and whimsical approach to problem solving is highlighted. This blog post imagines Mr. Feynman at a job interview, where he is asked to solve a “later-thinking” puzzle. It’s hilarious. If you enjoyed it, don’t hesitate to read the book.
Targeted to software developers trying to level up, this articles has great tips on how to be a better communicator and why it’s important. The advice resonates with me. Really, every one can benefit from being better at people, no?
Phil Calçado writes a detailed post on the non-technical side of why Soundcloud moved away from a monolithic Rails app, in favor of a microservices architecture. Main reason: productivity. They were able to reduce their time-to-launch of new features from 66 days to 16 days.
Originally published 2 years ago, Practicing Ruby provides a great explanation of what the Actor model looks like in Ruby. He solves the Dinning Philosophers Problem with bare ruby, the with Celluloid and then shows a simple implementation of actors in ruby would look like. Great read.
Did you know that when a process is forked in ruby, only the main thread is copied and all other threads are dead? Neither did I, until I ran into it recently. Solving threading issues is very hard. This post has great techniques on how to use threads in Rails, even if using forking servers.