[{"data":1,"prerenderedAt":77},["ShallowReactive",2],{"term-s\u002Fsolid":3,"related-s\u002Fsolid":60},{"id":4,"title":5,"acronym":5,"body":6,"category":39,"description":40,"difficulty":41,"extension":42,"letter":43,"meta":44,"navigation":45,"path":46,"related":47,"seo":53,"sitemap":54,"stem":57,"subcategory":58,"__hash__":59},"terms\u002Fterms\u002Fs\u002Fsolid.md","SOLID",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"eli5-the-vibe-check","ELI5 — The Vibe Check",[15,16,17],"p",{},"SOLID is five rules for writing code that doesn't turn into a nightmare over time. Each letter stands for a different rule. Follow them and your future self will thank you. Ignore them and you'll spend Fridays at 5pm untangling spaghetti.",[10,19,21],{"id":20},"real-talk","Real Talk",[15,23,24],{},"SOLID is an acronym for five object-oriented design principles: Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Introduced by Robert C. Martin, they guide the creation of maintainable, flexible, and scalable software.",[10,26,28],{"id":27},"when-youll-hear-this","When You'll Hear This",[15,30,31],{},"\"This class violates SOLID principles.\" \u002F \"Let's refactor this to follow SOLID before adding more features.\"",{"title":33,"searchDepth":34,"depth":34,"links":35},"",2,[36,37,38],{"id":12,"depth":34,"text":13},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"architecture","SOLID is five rules for writing code that doesn't turn into a nightmare over time. Each letter stands for a different rule.","intermediate","md","s",{},true,"\u002Fterms\u002Fs\u002Fsolid",[48,49,50,51,52],"Single Responsibility","Open-Closed","Liskov Substitution","Interface Segregation","Dependency Inversion",{"title":5,"description":40},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fs\u002Fsolid",null,"kTND88BC0XKoDMkJIKPXtqu3gZn1RvDe9N5bikBtVf0",[61,64,67,70,73],{"title":52,"path":62,"acronym":58,"category":39,"difficulty":41,"description":63},"\u002Fterms\u002Fd\u002Fdependency-inversion","Dependency Inversion says high-level code shouldn't depend on low-level code — both should depend on abstractions.",{"title":51,"path":65,"acronym":58,"category":39,"difficulty":41,"description":66},"\u002Fterms\u002Fi\u002Finterface-segregation","Interface Segregation means don't force classes to implement methods they don't need.",{"title":50,"path":68,"acronym":58,"category":39,"difficulty":41,"description":69},"\u002Fterms\u002Fl\u002Fliskov-substitution","Liskov Substitution says if class B extends class A, you should be able to swap B in everywhere A is used without anything breaking.",{"title":49,"path":71,"acronym":58,"category":39,"difficulty":41,"description":72},"\u002Fterms\u002Fo\u002Fopen-closed","Open-Closed means your code should be open for adding new features but closed for editing old working code.",{"title":48,"path":74,"acronym":58,"category":39,"difficulty":75,"description":76},"\u002Fterms\u002Fs\u002Fsingle-responsibility","beginner","Single Responsibility means every class or function should do ONE thing and do it well.",1776518310060]