While improving a build script by parallelising actions, I realised that Ruby’s puts is not atomic

I decided to play around with multithreading in Ruby. So I wrote the following basic script

If you’re using “Form Objects” to not keep validations in your ActiveRecord model, you might find yourself challenged when trying to reuse custom validators, that are common across few classes.

You’ve written a migration in your Ruby on Rails application, and like any normal human, you’ve made a mistake!

I am not that smart. I didn't say it. Michael Feathers did. But it got me thinking and I know it inspired my colleagues as well.

This mantra has became very popular and often is (mis)used to advocate some crazy things people do to avoid crunching the domain knowledge. In this post, I would like to return back to the roots.

As a software developer, it’s time to put your skills to use. The sooner you’re able to develop a working software solution, the happier the world will be.

Much like we gain knowledge about the behavior of the physical universe via the scientific method, we gain knowledge about the behavior of our software via a system of assertion, observation, and experimentation called “testing.”