RubyGems and npm are the de facto standard package managers for Ruby and Node.js. At first glance they seem similar (because they are!), but when building a product that interacts with both of them, there are subtle difference that need to be taken into account.
Metaprogramming is one of Ruby’s most powerful, intriguing and hard-to-grasp features. Ruby has a deep kind of truth that I could not yet find in any language, similar to the chicken & egg dilemma that we find in real life: an object is generated from a class, but a class is an object itself.
You have a Rails application and need to persist some data through a form which has a JavaScript money mask. Looking for a better way to do it I found two good solutions.
I’ve been doing Rails development already for more than five years and only now I learned about the schema cache, although this feature is mostly relevant for apps under the massive scale.
It’s been a while since I have had a full-blown, this is really truly nutso, case of Imposter Syndrome. I’m having one now, so I want to pull it apart and see what makes it tick.
When you go too far up, abstraction-wise, you run out of oxygen. Sometimes smart thinkers just don’t know when to stop, and they create these absurd, all-encompassing, high-level pictures of the universe that are all good and fine, but don’t actually mean anything at all.