[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_114":115,"_116":117},"routes/public/layout",{"_53":54},"routes/public/primary/notes",{"_11":12,"_13":14},"note",{"_16":43,"_18":43,"_19":45,"_21":46,"_23":47,"_25":26,"_27":48,"_29":30,"_31":30,"_32":49,"_34":50,"_36":51,"_13":52},"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/pursuing-technical-breath","slug","title","Pursuing Technical Breath","path","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/Pursuing Technical Breath","canonicalPath","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/pursuing-technical-breath","folder","Computer Science","tags",[],"createdAt","2026-07-26T03:12:21.719Z","modifiedAt","excerpt","Seorang Software Architect harus punya [[Technical Breath]] yang signifikan supaya dapat melihat sistem dari sudut pandang arsitektural. Bagi seorang arsitek, Breath lebih penting daripada Depth , karena arsitek harus me","html","

Seorang Software Architect harus punya Technical Breath yang signifikan supaya dapat melihat sistem dari sudut pandang arsitektural. Bagi seorang arsitek, Breath lebih penting daripada Depth, karena arsitek harus membuat keputusan yang sesuai dengan kebutuhan, dan pemahaman yang luas dari banyak macam solusi sangat bernilai untuk ini.

Walaupun begitu, sedikit bagian dari Technical Depth masih perlu dipertahankan dan itu menembus lapisan kedua dari piramida pengetahuan manusia yang menentukan seluas apa Breath Knowledge seorang arsitek.

Seorang arsitek yang kurang terampil mengolah Technical Breath dan Technical Depth dapat mengalami 2 dysfunctions associated with Architect’s knowledge.

Untuk mengejar Technical Breath, seorang Arsitek dapat menggunakan teknik The 20-Minutes Rule.

Arsitek juga harus punya alat untuk dapat mengetahui tren industri dengan cepat untuk mengambil keputusan, itu dapat diwujudkan dengan Technology Radar.

","outgoing",[40,41,42,43,44],[39],"computer-science/software-architecture/theoretical-knowledges/architectural-thinking/architectural-thinking","computer-science/software-architecture/theoretical-knowledges/expectations-of-an-architect/technical-breath","computer-science/software-architecture/theoretical-knowledges/expectations-of-an-architect/technical-depth","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/2-dysfunctions-associated-with-architect-s-knowledge","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/the-20-minutes-rule","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/technology-radar","The 20-Minutes Rule","Computer Science/Software Architecture/Theoretical Knowledges/Architectural Thinking/The 20-Minutes Rule","/notes/computer-science/software-architecture/theoretical-knowledges/architectural-thinking/the-20-minutes-rule",[],"Ide pokok dari aturan 20 menit adalah meluangkan waktu sebanyak dua puluh menit per hari untuk belajar hal baru atau mendalami hal yang sudah diketahui. Bagusnya di pagi hari, sebelum membuka email atau melihat jadwal ke","

Ide pokok dari aturan 20 menit adalah meluangkan waktu sebanyak dua puluh menit per hari untuk belajar hal baru atau mendalami hal yang sudah diketahui. Bagusnya di pagi hari, sebelum membuka email atau melihat jadwal kegiatan.

",[],[17],"profile",{"_16":55,"_56":53,"_57":58,"_59":60,"_61":62,"_63":64,"_29":65,"_66":67},"6954a19b11e7fe6da253c845","type","identity",{"_104":105,"_106":107,"_108":109,"_110":111},"contact",{"_96":97,"_98":99},"seo",{"_19":80,"_81":82,"_83":84,"_85":86,"_87":88,"_89":90},"bio",{"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":79},"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",[91,92,93,94,95],"Meta Engineer","Entrepreneur","Software Engineer","AI Developer","System Designer","email","contact@maulanahafidz.com","socials",{"_100":101,"_102":103},"github","https://github.com/imhefizh/","linkedin","https://www.linkedin.com/in/maulana-hafidz-ismail/","fullName","Maulana Hafidz Ismail","shortName","ImHefizh","titles",[112,113],"subtitle","Building systems that question the system.","Software Engineering","Entrepreneurship","nonce","7613de0c537447888dfdc7cb65fde315","language","EN"]

Linked mentions