Today I’m going to refactor a part of Ruby library called CreateSend. I’ll work on lib/createsend/createsend.rb, which contains CreateSend::CreateSend class and some other stuff.
Multiple people will use your app at the same time, and you want to deliver your app as fast as possible. So you'll need some way to handle concurrency. Fear not! Most web servers already do this by default. But when you need to scale, you want to use concurrency in the most efficient way possible.
In this post, I would like to summarize the practices that I follow when upgrading to major Rails releases, which have been pretty common for me since Rails 2.
Working on one commercial project I had to import and parse a xls file. Since the file had huge amount of data the parsing took time. To overcome this time-consuming process I had to split a parsing thread on a few ones.
Uncle Bob's response to article written by Ian Sommerville called Giving up on test-first development. An interesting discussion on test first principles.