[{"data":1,"prerenderedAt":73},["ShallowReactive",2],{"term-c\u002Fcohesion":3,"related-c\u002Fcohesion":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fc\u002Fcohesion.md","Cohesion",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"Cohesion is how well the things inside a module belong together. High cohesion means all the stuff in a class is related — like a toolbox full of tools. Low cohesion means the class is a junk drawer — a random mix of unrelated stuff. High cohesion = good.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Cohesion measures how strongly related the responsibilities within a single module are. High cohesion means a module focuses on a single purpose with all its elements contributing to that purpose. Low cohesion indicates the module does too many unrelated things.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"This service has low cohesion — it handles users, payments, AND emails.\" \u002F \"High cohesion and low coupling is the golden goal.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"architecture","Cohesion is how well the things inside a module belong together. High cohesion means all the stuff in a class is related — like a toolbox full of tools.","intermediate","md","c",{},true,"\u002Fterms\u002Fc\u002Fcohesion",[49,50,51,52],"Coupling","Single Responsibility","Separation of Concerns","Refactoring",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fc\u002Fcohesion","Ns9w6Jga7C3P8GTM1rTovhSS2PhSanu9PMD7uZEK8ck",[60,63,67,70],{"title":49,"path":61,"acronym":6,"category":40,"difficulty":42,"description":62},"\u002Fterms\u002Fc\u002Fcoupling","Coupling is how much two pieces of code depend on each other. Tight coupling means changing one breaks the other — like Siamese twins.",{"title":52,"path":64,"acronym":6,"category":40,"difficulty":65,"description":66},"\u002Fterms\u002Fr\u002Frefactoring","beginner","Refactoring is improving the internal structure of code WITHOUT changing what it does from the outside.",{"title":51,"path":68,"acronym":6,"category":40,"difficulty":65,"description":69},"\u002Fterms\u002Fs\u002Fseparation-of-concerns","Separation of Concerns means different parts of your code should handle different concerns and not step on each other's toes.",{"title":50,"path":71,"acronym":6,"category":40,"difficulty":65,"description":72},"\u002Fterms\u002Fs\u002Fsingle-responsibility","Single Responsibility means every class or function should do ONE thing and do it well.",1776518267291]