In IT, Beware of Fad Versus Functional
Lemeowski writes: Cloud, big data, and agile were three of the technology terms that were brandished the most by IT leaders in 2014. Yet, there could be a real danger in buying into the hype without understanding the implications of the technologies, writes Pearson CTO Sven Gerjets. In this essay, Gerjets warns that many IT executives drop the ball when it comes to "defining how a new technology approach will add value" to their organization. He says: "Yes, you can dive into an IT fad without thinking about it, but I can promise you'll look back and be horrified someday. The only time you can fully adopt some of these new methods is when you are starting from scratch. Most of us don't have that luxury because we are working with legacy architectures and technical debt so you have to play hand you've been dealt, communicate well, set clear and measurable outcomes, and use these fads to thoughtfully supplement the environment you are working in to benefit the ecosystem."
everyone realized that Ruby is awful
I'm tired of hearing this. Ruby is not awful. It's a wonderful language, and Rails is a wonderful framework. The problem is that Rails is designed for a very particular niche (small, fairly CRUD-oriented web applications), and people keep trying to stupidly shoehorn it into places where it doesn't work well (large, enterprise applications that need to do lots of heavy number crunching or querying of enormous databases in the background). Predictably, such projects end in a trainwreck and then people blame Rails, but Rails wasn't the problem.