Reading Time: 5 mins We have tools to analyze production logs and many companies use that data derived from logs for decision-making purposes, i.e. logs enable them to take decision by analysis the past patterns in the production

Reading Time: 5 mins What constitutes a method in programming is the number of classes. Methods, classes are all made up of lines of code. What happens when your method is fat?

Reading Time: 5 mins How can hundreds of engineers who contribute to software development every single day know how their work is making a difference to the business? How can they measure performance improvement for the number of code check-ins they do every day?

Reading Time: 6 mins The churn rate needs to be tracked early in the process in order to save a lot of time and cost which otherwise would incur when it goes to the production phase.

Reading Time: 5 mins Commits are an easy way to find the contributions made by each developer in building software, it could be fixing a bug, adding new features, etc.…which determine the overall health of the software.

Reading Time: 6 mins The number of lines of code is the base upon which the quality and the complexity of the software that you are building stands on.

Reading Time: 5 mins Cyclomatic complexity yields a value to your Software – Know how. Developed by Thomas J. McCabe, Sr. in 1976, Cyclomatic complexity is a software metric (measurement), used to indicate the complexity of a program.

Reading Time: 6 mins Horus provides an instant, real-time snapshot of technical development and facilitates the measurement of product development in terms of quality.

Reading Time: 7 mins What’s the difference between great engineering organizations that change the world, and other engineering organizations that fail?

Reading Time: 7 mins It was the worst day of her life. Sara Shahi had expected glowing words of praise, a hefty raise, and a promotion to Senior Developer, perhaps even Team Lead. Instead, her annual appraisal turned out to be nothing short of a firing squad. Pun intended.

Reading Time: 7 mins 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.

Reading Time: 7 mins Things were getting out of hand for Jack Reese, CIO. The more code commits his engineers made, the more liabilities they introduced in the form of practically untraceable bugs. The technical debt of his code base just kept piling up. Every moment spent was an expense that showed up on the balance sheet… that he had to answer for. Fortunately, he found a solution in Horus.

Reading Time: 7 mins Quantifying Quality with Horus Digital Enablement Tool