Today, Shopify runs on Rails 5, the latest major version. It’s important to us to stay updated so we can improve the performance and stability of the application without having to increase the maintenance cost of applying monkey patches
I’m a former C developer(for 5 years), that fell in love with Ruby and it’s ecosystem 4 years ago. After few months of practicing Ruby, I had quit my old job to become a full-time RoR developer in a great company, doing a lot of website crawling and working on a big rails application
In this blog post I will show how to use neural networks in Ruby to solve a simple classification problem. We will be using the RubyGem ruby-fann to help us setup a network, train and make predictions in a matter of minutes.
Although core team and the community behind Ruby on Rails is working very hard to ensure that this framework is providing high level of security, it is not possible that any framework will cover every possible scenario
In the last few years the Rails community has changed a lot. For people that have been working with Rails for 5+ years, it seems like only yesterday we were being introduced CoffeeScript and the Asset Pipeline
A traditional application architecture has Model, View and Controller or its variants. But over the years complexity of applications has increased exponentially, managing all the complexity in same code base created problems like scaling and code management
The purpose of this architecture is to be as flexible as possible in order to develop a project as quickly as possible and to maintain this speed during the whole development lifespan, whatever how big it grows and the changes that have to be done, for whatever reason
Software developers don’t really like to make schedules. Usually, they try to get away without one. “It’ll be done when it’s done!” they say, expecting that such a brave, funny zinger will reduce their boss to a fit of giggles, and in the ensuing joviality, the schedule will be forgotten