mrc's Cup of Joe Blog

Join us in exploring the world of modern development, evolving technologies, and the art of future-proof software

Month: February 2012

A quick way to modernize with a small IT staff

Save TimeWhat’s keeping your company from modernizing those legacy applications? If our 2011 survey is any indication, the answer is “There’s not enough time.” In fact, the survey results show that modernization is the biggest need, but a lack of time keeps most companies from addressing that need.

If your company lacks the time required to modernize your legacy apps, you’ll certainly want to read this story. It explains how one very small IT staff with limited time and resources managed to modernize their legacy green-screen interface quickly. You can read the whole story here.

5 big problems caused by bad application architecture

EducationApplication architecture is one of the single most important, yet boring topics you’ll ever run across. You’re not going to make too many friends at a party talking about technology stacks, open frameworks, or any other architecture-related themes. In fact, you’ll probably get a lot of blank stares wherever you talk about those things.

Yet, the difference between good and bad application architecture is mind-blowing. Good architecture is nearly invisible. Everything just works, it’s easy to maintain, and all of your applications operate in perfect harmony.

On the other hand, bad architecture is only invisible at the beginning, but becomes increasingly obvious over time. When you buy a new development tool or begin using pre-built software, the applications may initially work fine. But, if they’re built on bad architecture, problems will quickly arise. What exactly can you expect? Here are 5 costly problems caused by bad application architecture: