[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_129":130,"_131":132},"routes/public/layout",{"_68":69},"routes/public/primary/notes",{"_11":12,"_13":14},"note",{"_17":41,"_19":41,"_20":59,"_22":60,"_24":61,"_26":27,"_28":62,"_30":63,"_32":63,"_33":64,"_35":65,"_37":66,"_13":67},"backlinks",[15,16],{"_17":46,"_19":46,"_20":47,"_22":48,"_24":49,"_26":27,"_28":50,"_30":51,"_32":51,"_33":52,"_35":53,"_37":54,"_13":55},{"_17":18,"_19":18,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29,"_30":31,"_32":31,"_33":34,"_35":36,"_37":38,"_13":39},"id","computer-science/software-architecture/theoretical-knowledges/experts-quotes/experts-quotes","slug","title","Experts’ Quotes","path","Computer Science/Software Architecture/Theoretical Knowledges/Experts' Quotes/Experts’ Quotes","canonicalPath","/notes/computer-science/software-architecture/theoretical-knowledges/experts-quotes/experts-quotes","folder","Computer Science","tags",[],"createdAt","2026-07-26T03:12:21.731Z","modifiedAt","excerpt","[[Larry Constantine]] [[Mark Richards]] [[Neal Ford]] [[Rich Hickey]] [[Glenford J. Myers]]","html","

","outgoing",[41,42,43,44,45],[40],"computer-science/software-architecture/software-architecture","computer-science/software-architecture/theoretical-knowledges/experts-quotes/larry-constantine","computer-science/software-architecture/theoretical-knowledges/experts-quotes/mark-richards","computer-science/software-architecture/theoretical-knowledges/experts-quotes/neal-ford","computer-science/software-architecture/theoretical-knowledges/experts-quotes/rich-hickey","computer-science/software-architecture/theoretical-knowledges/experts-quotes/glenford-j-myers","computer-science/software-architecture/practical-knowledges/modularity/customer-and-order","Customer & Order","Computer Science/Software Architecture/Practical Knowledges/Modularity/Customer & Order","/notes/computer-science/software-architecture/practical-knowledges/modularity/customer-and-order",[],"2026-07-26T03:12:21.714Z","Diberikan sebuah modul seperti berikut: Haruskah 2 entri terakhir dipisahkan jadi modul baru bernama Order Maintenance? Atau cukup dibiarkan jadi satu disana? Hasilnya mungkin seperti ini: Sesuai hukum pertama Softect ya","

Diberikan sebuah modul seperti berikut:

Haruskah 2 entri terakhir dipisahkan jadi modul baru bernama Order Maintenance? Atau cukup dibiarkan jadi satu disana? Hasilnya mungkin seperti ini:

Sesuai hukum pertama Softect yaitu Everything in Software Architecture is a trade-off, maka jawabannya adalah “Tergantung”. Berikut pertimbangannya:

Apakah dua entri tersebut hanya satu-satunya operasi untuk modul Order Maintenance? Jika iya, mungkin lebih baik digabungkan saja dengan Customer Maintenance.
Apakah Customer Maintenance tampak akan berkembang jadi lebih besar? Jika iya, mungkin memang lebih baik untuk dipisah jadi module baru.
Apakah Order Maintenance membutuhkan banyak informasi dari Customer? Sehingga jika kita pisahkan maka akan menghasilkan coupling yang sangat kuat supaya dia berfungsi? Jika iya, mungkin lebih baik digabungkan saja untuk mencegah coupling yang tidak perlu. Ini punya hubungan dengan apa yang disebutkan oleh Larry Constantine yaitu Attempting to divide a cohesive module would only result in increased coupling and decreased readibility.

",[57,41,58],[56],"computer-science/software-architecture/practical-knowledges/modularity/study-cases","computer-science/software-architecture/theoretical-knowledges/laws-of-software-architecture/everything-in-software-architecture-is-a-trade-off","unresolved:attempting-to-divide-a-cohesive-module-would-only-result-in-increased-coupling-and-decreased-readibility","Larry Constantine","Computer Science/Software Architecture/Theoretical Knowledges/Experts' Quotes/Larry Constantine","/notes/computer-science/software-architecture/theoretical-knowledges/experts-quotes/larry-constantine",[],"2026-07-26T03:12:21.732Z","Berikut adalah beberapa kutipan dari Beliau terkait Software Architecture: [[Attempting to divide a cohesive module would only result in increased coupling and decreased readibility]]","

Berikut adalah beberapa kutipan dari Beliau terkait Software Architecture:

Attempting to divide a cohesive module would only result in increased coupling and decreased readibility

",[58],[46,18],"profile",{"_17":70,"_71":68,"_72":73,"_74":75,"_76":77,"_78":79,"_30":80,"_81":82},"6954a19b11e7fe6da253c845","type","identity",{"_119":120,"_121":122,"_123":124,"_125":126},"contact",{"_111":112,"_113":114},"seo",{"_20":95,"_96":97,"_98":99,"_100":101,"_102":103,"_104":105},"bio",{"_83":84,"_85":86,"_87":88,"_89":90,"_91":92,"_93":94},"2025-12-31T04:07:55.862Z","updatedAt","2026-07-28T08:55:52.260Z","p1","Maulana Hafidz Ismail is an engineer who believes technology isn't just about efficiency. It's about resistance.","p2","While the world optimizes for profit, he builds to question the system itself: in education, work, and how we define value.","p3","His background blends engineering precision with entrepreneurial instinct. He has worked across software development, database systems, and AI, always driven by one goal: to make tools that actually serve people, not the hierarchy itself.","closing","This site is his lab. He writes journals to document a process, articles to share thought, and papers to formalize the things he learns.","tagline","Some ideas fail, some evolve, all of them teach.","callToAction","If you're building, rebelling, or just thinking about how to make things better, you're already part of the conversation.","Maulana Hafidz","description","Technical articles, engineering notes, system design explorations, and project documentation by Maulana Hafidz Ismail, an Engineer documenting real software systems.","shortDescription","Maulana Hafidz Ismail is an Engineer and Entrepreneur in training. Redefining fairness in education, work, and governance.","url","https://maulanahafidz.com","image","https://maulanahafidz.com/og-image.jpg","keywords",[106,107,108,109,110],"Meta Engineer","Entrepreneur","Software Engineer","AI Developer","System Designer","email","contact@maulanahafidz.com","socials",{"_115":116,"_117":118},"github","https://github.com/imhefizh/","linkedin","https://www.linkedin.com/in/maulana-hafidz-ismail/","fullName","Maulana Hafidz Ismail","shortName","ImHefizh","titles",[127,128],"subtitle","Building systems that question the system.","Software Engineering","Entrepreneurship","nonce","319181be5717485499e59f2e6f61fb29","language","EN"]

Linked mentions