Madin “Root” Rutgers had everything it took to be a successful software architect. He was technically-inclined, a great problem-solver, and possessed excellent interpersonal relationship skills. A wonderful leader, he was extremely reliable and could be counted on to deliver, especially under pressure and tight deadlines.
Yet, at that moment, he was feeling far from successful.
Upper management expected him to “run a tight ship.” Their financial analyses were going haywire and there was no way to justify cost overruns to customers.
What was Madin to do?
He had more extensive knowledge of the software development process and its technologies than anyone else on the team. He knew architectural styles, design patterns, coding methods, computer languages, data modeling, and database design backwards.
And yet, here he was. Helpless.
It’s Not Just The Data
He needed data to “run a tight ship” and the organization’s “top-of-the-line” software just wouldn’t give him what he needed.
Actually, it did give him data. Useless data. Tons of it. Fancy graphs and bar charts that told him nothing.
True to his name, Madin “Root” Rutgers knew the root cause of the trouble lay in the bloated code churned out by his teams.
What he needed was a way to review millions of lines of code efficiently, to make sure the upcoming release had no fatty code.
He had to zero in on the exact code segments that were causing the problem and figure out which version of the releases were responsible for the bloated code.
That took more time than he had. He couldn’t be expected to live out of the office, right?
He needed to be able to review code anytime, anywhere.
Then he remembered that a friend had mentioned a digital enablement tool called Horus, which turned the conventional quality approach on its head.
Horus — A Friend Indeed
Given that his organization’s revenue — and existence — depended on its underlying code, it went without saying that the code needed to be of the highest quality. Horus was a data-driven engineering solution that could measure the quality of code and the way in which it was written. It didn’t just analyze code but also its context, and provided clarity on what actions needed to be taken. It looked at a lot more than just code, and analyzed issue tracker data, build aspects, and project management data as well. To top it all, it could run off an IDE, or browser, or even his mobile phone.
He reached for his phone, and called his friend.
Horus has enabled companies save >425,000 person hours. Software architects can perform and submit enterprise product reviews right from their mobile phones.
It wasn’t easy to convince middle management to switch over to Horus. Most of the technical features were totally lost in translation. Fortunately, its proven track record helped him swing the organization’s decision in favor of giving it a try.
To cut a long story short, Madin completed his reviews well in time. Not only did they make the release on time, it was a top-quality product that blazed faster than any other product on the market.
Thanks to Horus, Madin “Root” Rutgers had delivered as promised, yet again.