This is an interesting article about Twitter's shrinking use of Ruby and Rails. (My friend and coworker Abdul Habra sent it my way.)
The upshot is that Ruby and Rails are better tools for rapid development with a small team, but that they don't compare to the JVM for encapsulating things so that multiple teams can change things at the same time. There is also a performance gain, but that's a secondary concern.
Twitter seems to have taken a very smart route here - build their product quickly with "Agile" tools, then change as needed to support a larger user base.
I'm particularly geeked (pun intended) about their choice of JVM language. They went more cutting-edge with Scala as their language of choice for most applications.
All of my fellow Agile and Software Craft practitioners have experienced failure. It happens far more often than success, and usually for o...
Windows 10 has an issue with this mechanical keyboard (which works great, BTW). It's a Chinese-made keyboard (aren't they all?), bu...
What People Actually Hear in a Performance Review Many thanks to Mary Poppendieck, who wrote about this topic in 2004 , and proposed a...