Method Fattiness | Why It Is Important?

Keerthi Veerappan

Lead Marketing Strategist

An INFJ personality wielding brevity in speech and writing.

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?

The sequence of the code based getting into the deployment phase will be,

CPU, Network, RAM & Hard disc is very essential resources to read/write and run code, while rarely the code needs network support, the other elements are a must for a code, thus becoming performance bottlenecks.

The fatty methods gets stored in the RAM, the CPU has to retrieve these methods from the RAM and run which takes a little too much time whereas the lean methods, being thin in size get stored in the server of the CPU itself and when it is run, it takes very less time to run it as opposed to retrieving them from RAM and running it.

Disc write is always costly compared to RAM write. When resources are used minimally, a large amount of work gets done quickly.

Hence writing lean methods is to be recommended to save time and storage for fast execution.

Horus, an engineering management platform helps companies follow the best practices and help the engineering team address the issues in code and code annotations.

Head over to explore Horus

Leave A Comment Cancel reply

Method Fattiness | Why It Is Important?

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?

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

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

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

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

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.

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

horus-enterprise-va-e1561615709175-compressed-image

How Horus Can Transform Your Enterprise

What’s the difference between great engineering organizations that change the world, and other engineering organizations that fail?

Developers Can Prove Their True Worth With Horus Digital Enablement Tool

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.

How Horus Enables Architects To Deliver Business Results

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.

CIOs Can Cut Development Costs In Half With Horus Digital Enablement Tool

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.