[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_157":158,"_159":160},"routes/public/layout",{"_96":97},"routes/public/primary/notes",{"_11":12,"_13":14},"note",{"_20":44,"_22":44,"_23":87,"_25":88,"_27":89,"_29":30,"_31":90,"_33":91,"_35":91,"_36":92,"_38":93,"_40":94,"_13":95},"backlinks",[15,16,17,18,19],{"_20":76,"_22":76,"_23":77,"_25":78,"_27":79,"_29":30,"_31":80,"_33":81,"_35":82,"_36":83,"_38":84,"_40":85,"_13":86},{"_20":66,"_22":66,"_23":67,"_25":68,"_27":69,"_29":30,"_31":70,"_33":71,"_35":71,"_36":72,"_38":73,"_40":74,"_13":75},{"_20":55,"_22":55,"_23":56,"_25":57,"_27":58,"_29":30,"_31":59,"_33":60,"_35":60,"_36":61,"_38":62,"_40":63,"_13":64},{"_20":45,"_22":45,"_23":46,"_25":47,"_27":48,"_29":30,"_31":49,"_33":34,"_35":34,"_36":50,"_38":51,"_40":52,"_13":53},{"_20":21,"_22":21,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":34,"_36":37,"_38":39,"_40":41,"_13":42},"id","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/frozen-caveman-antipattern","slug","title","Frozen Caveman Antipattern","path","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/Frozen Caveman Antipattern","canonicalPath","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/frozen-caveman-antipattern","folder","Computer Science","tags",[],"createdAt","2026-07-26T03:12:21.719Z","modifiedAt","excerpt","Frozen Caveman [[Antipattern]] mendeskripsikan seorang Arsitek yang kembali kepada kekhawatiran dia yang tidak rasional untuk setiap arsitektur, umumnya karena trauma di masa lalu karena pernah mengambil keputusan yang t","html","

Frozen Caveman Antipattern mendeskripsikan seorang Arsitek yang kembali kepada kekhawatiran dia yang tidak rasional untuk setiap arsitektur, umumnya karena trauma di masa lalu karena pernah mengambil keputusan yang tidak tepat.

Penilaian Resiko memang penting, tapi tetap harus realistis. Berpikir seperti seorang Arsitek berarti handal dalam mengatasi Antipattern ini, melihat solusi lain, dan bertanya pertanyaan yang relevan.

","outgoing",[44],[43],"computer-science/software-architecture/theoretical-knowledges/architectural-thinking/2-dysfunctions-associated-with-architect-s-knowledge","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/antipattern","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/bottleneck-trap-antipattern","Bottleneck Trap Antipattern","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/Bottleneck Trap Antipattern","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/bottleneck-trap-antipattern",[],"[[Antipattern]] ini terjadi ketika seorang arsitek mengambil kepemilikan yang kuat untuk suatu kode di project (umumnya framework) sehingga menjadi hambatan bagi tim.","

Antipattern ini terjadi ketika seorang arsitek mengambil kepemilikan yang kuat untuk suatu kode di project (umumnya framework) sehingga menjadi hambatan bagi tim.

",[44],[54],"computer-science/software-architecture/theoretical-knowledges/architectural-thinking/balancing-architecture-and-coding-practices","computer-science/software-architecture/practical-knowledges/modularity/spaghetti-architecture","Spaghetti Architecture","Computer Science/Software Architecture/Practical Knowledges/Modularity/Spaghetti Architecture","/notes/computer-science/software-architecture/practical-knowledges/modularity/spaghetti-architecture",[],"2026-07-26T03:12:21.716Z","[[Antipattern]] ini merujuk pada sistem yang jadi kusut dan kompleks karena perencanaan integrasi yang buruk, sistem warisan, dan akumulasi dari hutang teknis di masa lalu.","

Antipattern ini merujuk pada sistem yang jadi kusut dan kompleks karena perencanaan integrasi yang buruk, sistem warisan, dan akumulasi dari hutang teknis di masa lalu.

",[44],[65],"computer-science/software-architecture/practical-knowledges/modularity/granularity","computer-science/software-architecture/practical-knowledges/modularity/distributed-monolith","Distributed Monolith","Computer Science/Software Architecture/Practical Knowledges/Modularity/Distributed Monolith","/notes/computer-science/software-architecture/practical-knowledges/modularity/distributed-monolith",[],"2026-07-26T03:12:21.714Z","[[Antipattern]] ini merujuk pada sistem yang terbagi menjadi beberapa service yang masih mempertahankan sifat interkoneksi dari traditional monolith . Ini biasanya ditemukan pada arsitektur Microservices. Secara rancanga","

Antipattern ini merujuk pada sistem yang terbagi menjadi beberapa service yang masih mempertahankan sifat interkoneksi dari traditional monolith. Ini biasanya ditemukan pada arsitektur Microservices.

Secara rancangan, service-service tersebut seharusnya hadir secara terpisah tapi malah berperilaku seperti satu unit yang saling bergantung karena terlalu banyak ketergantungan, memaksa deployment yang berurutan dan melemahkan skalabilitas. Kelemahan utama yang disorot dari antipattern ini adalah latency chain.

",[44],[65],"computer-science/software-architecture/practical-knowledges/modularity/big-ball-of-distributed-mud","Big Ball of Distributed Mud","Computer Science/Software Architecture/Practical Knowledges/Modularity/Big Ball of Distributed Mud","/notes/computer-science/software-architecture/practical-knowledges/modularity/big-ball-of-distributed-mud",[],"2026-07-26T03:12:21.711Z","2026-07-26T03:12:21.712Z","[[Antipattern]] ini merujuk pada sistem yang telah membesar dan berevolusi menjadi kekacauan yang kusut dan tidak terkelola seiring waktu, sehingga tampak tidak memiliki struktur arsitektur yang jelas. Ini dapat muncul k","

Antipattern ini merujuk pada sistem yang telah membesar dan berevolusi menjadi kekacauan yang kusut dan tidak terkelola seiring waktu, sehingga tampak tidak memiliki struktur arsitektur yang jelas.

Ini dapat muncul ketika Developer/Engineer mengutamakan perubahan jangka pendek daripada desain dan perencanaan arsitektural jangka panjang. Hasilnya, codebase menjadi sulit untuk dipahami, dipelihara, dan diperluas, meningkatkan biaya pengembangan dan mengurangi reliability dari sistem.

",[44],[65],"Antipattern","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/Antipattern","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/antipattern",[],"2026-07-26T03:12:21.717Z","Andrew Koenig mendeskripsikan Antripattern sebagai sesuatu yang tampak seperti ide bagus di permulaan, namun dapat membawa kita ke dalam masalah di masa depan.","

Andrew Koenig mendeskripsikan Antripattern sebagai sesuatu yang tampak seperti ide bagus di permulaan, namun dapat membawa kita ke dalam masalah di masa depan.

",[],[76,66,55,45,21],"profile",{"_20":98,"_99":96,"_100":101,"_102":103,"_104":105,"_106":107,"_33":108,"_109":110},"6954a19b11e7fe6da253c845","type","identity",{"_147":148,"_149":150,"_151":152,"_153":154},"contact",{"_139":140,"_141":142},"seo",{"_23":123,"_124":125,"_126":127,"_128":129,"_130":131,"_132":133},"bio",{"_111":112,"_113":114,"_115":116,"_117":118,"_119":120,"_121":122},"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",[134,135,136,137,138],"Meta Engineer","Entrepreneur","Software Engineer","AI Developer","System Designer","email","contact@maulanahafidz.com","socials",{"_143":144,"_145":146},"github","https://github.com/imhefizh/","linkedin","https://www.linkedin.com/in/maulana-hafidz-ismail/","fullName","Maulana Hafidz Ismail","shortName","ImHefizh","titles",[155,156],"subtitle","Building systems that question the system.","Software Engineering","Entrepreneurship","nonce","99d715f1d239471cab814b521364bf92","language","EN"]

Linked mentions