Lack of Cohesion of Methods: What Is This And Why Should You Care?
blog.ndepend.com · 2,482 words · saved by 1 readers
Today we take a look at lack of cohesion of methods in your codebase. What does this mean? How do you measure it? Why does it matter?
May 14, 2026 9 minutes read Lack of cohesion of methods (usually shortened to LCOM) is one of those things that sits fairly high up on the software hierarchy of needs. What’s the “software hierarchy of needs?” It’s a thing that I just made up, shamelessly copying Maslow’s Hierarchy of Needs . (Though in a quick search to see how effectively I’ve planted this flag, I see that Scott Hanselman had the idea before me . But mine looks a little different than his because I’m talking about the software, rather than the humans writing it.) Anyway, here’s
related reading
- Cognitive load is what mattersminds.md
- Coupling and Cohesion - Software Engineering - GeeksforGeeksgeeksforgeeks.org
- Coupling, Cohesion & Connascence | Khalil Stemmlerkhalilstemmler.com
- How To Do Lessalexturek.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- Coupling (computer programming) - Wikipediaen.wikipedia.org
- How to write complex softwaregrantslatton.com
- How To De-Slop A Codebase Ruined By AI (with one skill)youtube.com
- Mistakes engineers make in large established codebasesseangoedecke.com
- programming practices - How to comprehend abstraction in code? - Software Engineering Stack Exchangesoftwareengineering.stackexchange.com
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Notes on software qualityanthonyhobday.com