Cloning 120-Volt batteries: The Inexpensive route to build better Underwriting Efficiency
Reading Time: 7 mins Building a system that emulates what the team of underwriters can help achieve the goal of attaining better underwriting efficiency.
Do you have production issues? Then, you are doing well.
Reading Time: 7 mins Production issues are a black swan. We classify them as unknown unknowns because we can’t guess what had gone wrong until it has happened, and they usually carry an extreme impact.
We don’t take Production logs seriously, Do we?
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
Method Fattiness | Why it is important?
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?
Do you measure your Engineering Grit?
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?
Churn rate | Why it should be measured
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.
Commit count | Why it should be measured
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.
Class Fattiness | Why it should be measured
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.
Cyclomatic Complexity | Why it should be measured
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.
Horus helps CTOs drive engineering innovation, attract and retain customers.
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.