[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_117":118,"_119":120},"routes/public/layout",{"_56":57},"routes/public/primary/notes",{"_11":12,"_13":14},"note",{"_16":41,"_18":41,"_19":46,"_21":47,"_23":48,"_25":26,"_27":49,"_29":50,"_31":50,"_32":51,"_34":52,"_36":53,"_13":54},"backlinks",[15],{"_16":17,"_18":17,"_19":20,"_21":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":30,"_32":33,"_34":35,"_36":37,"_13":38},"id","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/balancing-architecture-and-coding-practices","slug","title","Balancing Architecture and Coding Practices","path","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/Balancing Architecture and Coding Practices","canonicalPath","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/balancing-architecture-and-coding-practices","folder","Computer Science","tags",[],"createdAt","2026-07-26T03:12:21.718Z","modifiedAt","excerpt","Menjaga keandalan dalam praktek sembari mempertahankan peran arsitek perlu dilakukan. Hal ini dapat dijadikan solusi untuk [[Bottleneck Trap Antipattern]] dengan cara menyerahkan bagian kritis dari suatu project ke tim p","html","

Menjaga keandalan dalam praktek sembari mempertahankan peran arsitek perlu dilakukan. Hal ini dapat dijadikan solusi untuk Bottleneck Trap Antipattern dengan cara menyerahkan bagian kritis dari suatu project ke tim pengembang dan hanya fokus praktek pada hal kecil dari project tersebut.

Hal tersebut akan membawa 3 dampak positif:

Arsitek tersebut akan mendapatkan pengalaman nyata dengan menulis kode produksi tanpa menjadi hambatan tim.
Bagian kritis dari project diserahkan ke tim pengembang sehingga mereka dapat bekerja dengan lebih nyaman.
Arsitek tersebut menulis source code yang juga terkait dengan bisnisnya bersama dengan tim pengembang, membuatnya dapat paham pain-point yang dirasakan tim pengembang.

Berikut adalah beberapa teknik, tips, dan praktek terkait hal ini:

","outgoing",[40,41,42,43,44,45],[39],"computer-science/software-architecture/theoretical-knowledges/architectural-thinking/architectural-thinking","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/bottleneck-trap-antipattern","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/frequent-proof-of-concept","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/tackle-technical-debt","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/fix-bugs","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/automate","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/do-code-reviews","Frequent proof-of-concept","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/Frequent proof-of-concept","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/frequent-proof-of-concept",[],"2026-07-26T03:12:21.719Z","Pengadaan [[Proof of Concept]] membuat seorang arsitek perlu menulis source code. Semakin banyak POC yang dimiliki seorang arsitek maka semakin banyak referensi dan rasa percaya diri yang dia punya dalam melakukan tade-o","

Pengadaan Proof of Concept membuat seorang arsitek perlu menulis source code. Semakin banyak POC yang dimiliki seorang arsitek maka semakin banyak referensi dan rasa percaya diri yang dia punya dalam melakukan tade-off analysis.

",[55],[17],"computer-science/software-architecture/theoretical-knowledges/architectural-thinking/proof-of-concept","profile",{"_16":58,"_59":56,"_60":61,"_62":63,"_64":65,"_66":67,"_29":68,"_69":70},"6954a19b11e7fe6da253c845","type","identity",{"_107":108,"_109":110,"_111":112,"_113":114},"contact",{"_99":100,"_101":102},"seo",{"_19":83,"_84":85,"_86":87,"_88":89,"_90":91,"_92":93},"bio",{"_71":72,"_73":74,"_75":76,"_77":78,"_79":80,"_81":82},"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",[94,95,96,97,98],"Meta Engineer","Entrepreneur","Software Engineer","AI Developer","System Designer","email","contact@maulanahafidz.com","socials",{"_103":104,"_105":106},"github","https://github.com/imhefizh/","linkedin","https://www.linkedin.com/in/maulana-hafidz-ismail/","fullName","Maulana Hafidz Ismail","shortName","ImHefizh","titles",[115,116],"subtitle","Building systems that question the system.","Software Engineering","Entrepreneurship","nonce","1d653a2e19d749ac8b0c48ee44634b8f","language","EN"]

Linked mentions