Video

Here’s another story about BDD using cucumber: how it helped us with a client who was not very easy to convince, and also on a technically complex platform.

Video

We were so excited to experience the power of seeing a line modified in our infrastructure code, get reflected across the bunch of instances we had. Wow!

Here’s the power of Chef. 50+ amazon instances, and every config and deployment on that box is controlled via code!

Video

Non-blocking I/O has caught everyone’s fancy. We’ve used Goliath - a non-blocking Ruby 1.9 server - on one of our projects and built a fast image transfer service.

Video

Does working with spaghetti JS code make you pull your hair out at times?

One simple technique we use, mostly on Rails projects, is to scope JS execution by detecting the controller and action that serves the page.

Video

Google+ Hangout for daily client catch-up calls. That sounds fun!

It also turned out to be a good ice-breaker, helped smooth out communication and reduced distance between offshore and onshore developers.

Video

Someone wrote up a cucumber test on the project with a @javascript tag and the rest just followed. Is that what happens?

Did you think of options or actively look out for opportunity to convert a bunch of tests not dependent on JS to run on RackTest driver? Save a lot of minutes on your builds in the process.

Video

We always separate out processes like: image thumb-nailing, indexing records and sending out emails from a user request cycle. Can’t keep him waiting for all this.

Rather we use simple AWS SQS to communicate to hungry worker units about these tasks, workers pick up the message and they know what to do. Workers, are small units of code, deployed on their own instances. This makes it easier to analyze performance, monitor and independently scale them.