<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Irwansyah on Medium]]></title>
        <description><![CDATA[Stories by Irwansyah on Medium]]></description>
        <link>https://medium.com/@irwansyah?source=rss-cc5dcf750225------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*swxJERZUE2EbqTYKzzSiIg.png</url>
            <title>Stories by Irwansyah on Medium</title>
            <link>https://medium.com/@irwansyah?source=rss-cc5dcf750225------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:39:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@irwansyah/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Bagaimana Sebuah E-Wallet Besar Indonesia yang Didukung Alibaba Ant Kehilangan Pembayaran Cicilan…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://irwansyah.medium.com/bagaimana-sebuah-e-wallet-besar-indonesia-yang-didukung-alibaba-ant-kehilangan-pembayaran-cicilan-a516149f6995?source=rss-cc5dcf750225------2"><img src="https://cdn-images-1.medium.com/max/1780/1*Y68QPC74Av_MWg_th8a5_A.png" width="1780"></a></p><p class="medium-feed-snippet">Saya biasa membayar cicilan mobil lewat aplikasi e-wallet (dompet digital) besar di Indonesia, rutin setiap tanggal 25. Berbulan-bulan&#x2026;</p><p class="medium-feed-link"><a href="https://irwansyah.medium.com/bagaimana-sebuah-e-wallet-besar-indonesia-yang-didukung-alibaba-ant-kehilangan-pembayaran-cicilan-a516149f6995?source=rss-cc5dcf750225------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://irwansyah.medium.com/bagaimana-sebuah-e-wallet-besar-indonesia-yang-didukung-alibaba-ant-kehilangan-pembayaran-cicilan-a516149f6995?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/a516149f6995</guid>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 02:24:43 GMT</pubDate>
            <atom:updated>2026-10-27T02:42:54.236Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How a Major Indonesian E-Wallet Backed by Alibaba Ant Lost My Car Payment — and How to Fix It Using…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://irwansyah.medium.com/how-a-major-indonesian-e-wallet-backed-by-alibaba-ant-lost-my-car-payment-and-how-to-fix-it-using-a81e0f8ba9bb?source=rss-cc5dcf750225------2"><img src="https://cdn-images-1.medium.com/max/1780/1*Y68QPC74Av_MWg_th8a5_A.png" width="1780"></a></p><p class="medium-feed-snippet">I used to pay for my car installment through a major E-wallet app in Indonesia regularly every 25th every month. It was working smoothly&#x2026;</p><p class="medium-feed-link"><a href="https://irwansyah.medium.com/how-a-major-indonesian-e-wallet-backed-by-alibaba-ant-lost-my-car-payment-and-how-to-fix-it-using-a81e0f8ba9bb?source=rss-cc5dcf750225------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://irwansyah.medium.com/how-a-major-indonesian-e-wallet-backed-by-alibaba-ant-lost-my-car-payment-and-how-to-fix-it-using-a81e0f8ba9bb?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/a81e0f8ba9bb</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[money]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 15:43:16 GMT</pubDate>
            <atom:updated>2026-10-27T02:08:29.812Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[TaroDomain: This is the way to build scalable and beautiful system]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://irwansyah.medium.com/tarodomain-this-is-the-way-to-build-scalable-and-beautiful-system-959d6ecd0cdb?source=rss-cc5dcf750225------2"><img src="https://cdn-images-1.medium.com/max/600/1*BGcNgvGeALZ8qR_S60qQNw.jpeg" width="600"></a></p><p class="medium-feed-snippet">What Is an Aggregate?</p><p class="medium-feed-link"><a href="https://irwansyah.medium.com/tarodomain-this-is-the-way-to-build-scalable-and-beautiful-system-959d6ecd0cdb?source=rss-cc5dcf750225------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://irwansyah.medium.com/tarodomain-this-is-the-way-to-build-scalable-and-beautiful-system-959d6ecd0cdb?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/959d6ecd0cdb</guid>
            <category><![CDATA[domain-driven-design]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-design-patterns]]></category>
            <category><![CDATA[clean-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 07:43:30 GMT</pubDate>
            <atom:updated>2026-10-11T07:43:30.824Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From ERD to DDD: 40 Years of Software Architecture (And Why I am Building TaroDomain)]]></title>
            <link>https://irwansyah.medium.com/from-erd-to-ddd-40-years-of-software-architecture-and-why-i-am-building-tarodomain-bae68c53ec8c?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/bae68c53ec8c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[domain-driven-design]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 12:26:49 GMT</pubDate>
            <atom:updated>2026-10-08T12:26:49.729Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*IKejJwGfJTppWUNEmrxydA.jpeg" /></figure><p>This morning Bude Ti asked me a question while I was sipping Tubruk coffee at Pak Slamet’s warkop. “Taro, you’ve been in IT for 20 years. Why do kids these days argue so much about React vs Angular, or Monolith vs Microservices? Isn’t there one right answer?”</p><p>I sipped my coffee. “Bude, those are just tools. Software architecture is like a pendulum. You swing left, right, back to the left. Searching for the perfect balance between business agility and technical scalability.”</p><p>Bude Ti stirred her rice. “Pendulum? That pendulum on the wall clock is just there to cover up a nail hole.”</p><p>Literal. Bude Ti is indeed the most literal interpreter of instructions on earth. But she’s not wrong. For 40 years, the software industry has been treated like a pendulum. Swinging back and forth.</p><p>Here is the unvarnished history of how we got here, the trade-offs of each era, and why I finally decided to build a new framework: TaroDomain.</p><h3>The 80s: ERD is King, OOP is an Afterthought</h3><p>In the 80s and early 90s, designing software was viewed entirely from the database’s perspective. We used DFDs (Data Flow Diagrams) to track how data moved, and ERDs (Entity-Relationship Diagrams) to design the database schema. Because databases were the most expensive and critical part of the system, the ERD became the de facto blueprint for the entire application.</p><p>Then Object-Oriented Programming (OOP) arrived. IT folks back then struggled to translate these data-centric diagrams into objects. This birthed Object-Oriented Analysis and Design (OOAD). Pioneers like Grady Booch created rigorous modeling techniques, notably the Use Case Document. By 1997, they unified their methods into UML (Unified Modeling Language). We meticulously drew Class Diagrams before writing any code. Around the same time, the Gang of Four (GoF) published their book on Design Patterns.</p><p>OOAD and UML gave us a rigorous, standardized way to bridge business requirements and code. Use Cases structured our requirements. Design Patterns gave us a shared vocabulary.</p><p>UML quickly devolved into a heavy, jarring waterfall artifact. Developers spent months drawing Class Diagrams that became obsolete the moment code was written. And because the ERD was still the foundation, developers simply created objects that mirrored database tables. OOP devolved into “classy procedural code” where objects were just dumb data bags and UML was just a pretty picture of a database schema.</p><h3>The Three-Tier Era and the ORM Trap</h3><p>In the late 90s and early 2000s, web apps grew massive. The tight coupling between UI, logic, and database made our heads nge-hang. The industry adopted the Three-Tier Architecture (Presentation, Application, Data) to enforce Separation of Concerns.</p><p>To help developers, Martin Fowler published Patterns of Enterprise Application Architecture (PoEAA). The crown jewel was the Domain Model pattern. Objects shouldn’t be dumb data bags. Objects should encapsulate both state and behavior. A User object shouldn’t just have getters and setters; it needs a lockAccount() method that enforces business rules internally.</p><p>To save and load these smart objects, developers turned to ORMs (Object-Relational Mapping). Hibernate or Entity Framework promised to seamlessly translate objects into relational database rows and back.</p><p>ORMs ran headfirst into the Object-Relational Impedance Mismatch. OOP is about graphs and encapsulation; databases are about flat tables. Mapping a rich, behavioral object to a table was a mbulet (convoluted) nightmare of lazy-loading issues and N+1 queries.</p><p>Developers took the easy way out: they stripped the behavior from objects to make the ORM’s job easier. The Anemic Domain Model (ADM) anti-pattern was born. Objects became dumb again, and business logic was shoved back into “Use Case” services. The Three-Tier Architecture became hollow, serving as little more than a pass-through for the ORM and the ERD.</p><h3>The Rails Revolution and the Triumph of ActiveRecord</h3><p>Just as we were drowning in ORM configurations, Ruby on Rails arrived in 2004 and conquered the web. Rails popularized the ActiveRecord pattern.</p><p>ActiveRecord threw architectural purity out the window for unprecedented developer velocity. It flattened the Three-Tier Architecture and embraced the Impedance Mismatch. Instead of fighting to map objects to tables, ActiveRecord fused them: your database table is your object.</p><p>Rails proved that for 80% of web apps (simple CRUD), ActiveRecord was a superpower. Features were built in days, not weeks. The pattern was copied into every major language (Laravel in PHP, JPA in Java, GORM in Go).</p><p>ActiveRecord was the ultimate enabler of the Anemic Domain Model. Because the object was tied to the table, putting complex business logic inside it created “Fat Models” (It also can create Fat Controllers or God Objects). Over years of rapid iteration, these monoliths inevitably devolved into a Big Ball of Mud — a tangled, tightly coupled mess where every controller talked to every table.</p><h3>The Microservices Illusion and the Distributed Big Ball of Mud</h3><p>As monolithic “Big Balls of Mud” became impossible to scale, the industry looked for an escape hatch. Enter Microservices. The promise was seductive: break the monolith into small, independent services.</p><p>Engineers eagerly carved up their monoliths without a principled guide. They didn’t use DDD; they just grouped services by technical function or arbitrarily sliced the ERD.</p><p>Without Bounded Contexts, the services were still tightly coupled. They shared databases, made synchronous HTTP calls, and introduced distributed transactions. We traded a local Big Ball of Mud for a Distributed Big Ball of Mud. A single user request now required five network hops, introducing latency, cascading failures, and debugging nightmares. Uncle Bob’s SOLID principles couldn’t save us. We needed a way to define true, decoupled business boundaries.</p><h3>The Paradigm Shift: DDD, CQRS, and Event Sourcing</h3><p>We finally realized the database is just an implementation detail, and network boundaries must align with business boundaries. Enter Domain-Driven Design (DDD). DDD emerged to rescue the rich Domain Model and provide the boundaries microservices desperately needed. It discarded the ERD-first approach, enforcing a Ubiquitous Language and Bounded Contexts.</p><p>But DDD had a fundamental tension: we used the exact same data model to enforce complex business rules (writes) and render complex UI dashboards (reads). This mismatch caused the “Fat Models.” Enter CQRS (Command Query Responsibility Segregation), introduced by Greg Young. A radical split:</p><ul><li><strong>Write Model (Commands)</strong>: Handles complex DDD Aggregates, enforcing business invariants and transactions. Optimized for consistency, completely ignoring how the UI wants to see the data.</li><li><strong>Read Model (Queries)</strong>: Stripped of all business logic. Optimized purely for fetching data fast, using flat tables or NoSQL documents that perfectly match the UI.</li></ul><p>Alongside CQRS came Event Sourcing.</p><p>DDD aligned code with business boundaries. CQRS solved the read/write tension permanently. Event Sourcing made the event the source of truth, providing 100% auditability — a lifesaver for Fintech. By focusing on events rather than state, we bypassed the ORM Impedance Mismatch entirely.</p><p>The cognitive load of DDD, CQRS, and Event Sourcing is massive. You don’t need CQRS for a simple admin panel; CRUD and ActiveRecord are still 10x faster to build. Event Sourcing introduces eventual consistency, complex schema versioning, and hard-to-debug projections. It is a heavy weapon that will make a team mbledos (explode) if misused.</p><h3>The Missing Link: Event Storming and the Rise of AI</h3><p>To bridge the gap between domain experts and developers, Alberto Brandolini created Event Storming. Instead of writing static Use Case documents or staring at ERDs, we look at domain events (“Order Placed”, “Payment Verified”). Business and engineers finally speak the same language to discover Bounded Contexts in real-time.</p><p>And what I’ve felt strongly lately: the rise of AI. Wooo, imagine this… Building DDD used to take a lot of works, writing boilerplate Aggregates and Event Sourcing until you went bald. Now? AI makes implementing domain models and DDD quick. What used to take months of thinking about the base framework, AI now helps scaffold quickly. We can focus on business logic without typing repetitive base code. DDD, which used to be heavy, is now much easier to execute.</p><h3>TaroDomain Framework</h3><p>TaroDomain is a DDD + Event Sourcing framework designed to be polyglot and cloud-agnostic. It provides a clean domain model architecture that allows you to persist aggregates using either State-Based or Event Sourcing mechanisms, depending on the bounded context’s needs.</p><p>The Design Principles of TaroDomain:</p><ul><li><strong>Persistence Agnostic</strong>: Define your Aggregates and Domain Events once. You can change which storage to use easily via interfaces.</li><li><strong>Polyglots</strong>: The core architecture is designed to be implemented in any language. We are starting with TypeScript, but the design patterns allow for easy porting to Elixir, C#, or Go.</li><li><strong>Platform Agnostic</strong>: The initial implementation is heavily optimized for Cloudflare services and using TypeScript because CloudFlare is the cheapest platform compare to other cloud platforms. Later on any one can implement the adapters for other cloud platforms.</li></ul><p>In the next part 2 I will wrote about the framework design and implementation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bae68c53ec8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Two Factor Authentication Using Formal Methods]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/practical-software-craftsman/implementing-two-factor-authentication-using-formal-methods-c2d62a996ecf?source=rss-cc5dcf750225------2"><img src="https://cdn-images-1.medium.com/max/2550/0*HoVuERdYRzJg64HE.jpeg" width="2550"></a></p><p class="medium-feed-snippet">Well, every one knows Two Factor Authentication (TFA). Most probably already implemented it in their own system. So what are the&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/practical-software-craftsman/implementing-two-factor-authentication-using-formal-methods-c2d62a996ecf?source=rss-cc5dcf750225------2">Continue reading on Practical Software Craftsman »</a></p></div>]]></description>
            <link>https://medium.com/practical-software-craftsman/implementing-two-factor-authentication-using-formal-methods-c2d62a996ecf?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2d62a996ecf</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[tla-plus]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[formal-verification]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Sun, 25 May 2025 09:35:03 GMT</pubDate>
            <atom:updated>2025-05-25T09:54:01.027Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Logic — Part 2]]></title>
            <link>https://medium.com/practical-software-craftsman/logic-part-2-17654f864957?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/17654f864957</guid>
            <category><![CDATA[logic]]></category>
            <category><![CDATA[arguments]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Tue, 06 May 2025 08:51:44 GMT</pubDate>
            <atom:updated>2025-05-06T08:51:44.503Z</atom:updated>
            <content:encoded><![CDATA[<h3>Logic — Part 2</h3><p><strong>Proposition</strong></p><p>When we are expressing our thought into a sentence, the meaning of the sentence is called proposition. A proposition must have a subject and a predicate and it must be able to be verified as true or false. Examples of proposition:</p><ol><li>Most bicycles have two wheels</li><li>Burj Khalifa is over 600m tall</li><li>John is a priest</li></ol><p>If we remove the subject or the predicate of the statements above then we can’t know what’s the meaning of the sentence:</p><ol><li>Most bicycles</li><li>Is over 600m tall</li><li>John</li></ol><p>Two or more sentences can express the same proposition:</p><ol><li>John is a priest</li><li>John is a pastor</li></ol><p>Both if expressed in Indonesian:</p><ol><li>John adalah pendeta</li><li>John adalah pastor</li></ol><p>All four statements in different languages above refers to the same proposition.</p><p>We can use the class diagram below to organize our understanding of proposition:</p><figure><img alt="Summary of proposition in a class diagram" src="https://cdn-images-1.medium.com/max/1024/1*jau8LSRC0x-QNKIbi8sgtQ.png" /></figure><p><strong>Arguments</strong></p><blockquote>All rivers in the world flow downhill</blockquote><p>How do we know? How can we convince everyone to believe that all rivers in the world flow downhill? We can make an argument for it:</p><blockquote>Premises:</blockquote><blockquote>A ball release from the air fall to the ground</blockquote><blockquote>There is force that pulls the ball to the ground</blockquote><blockquote>That force is called gravity</blockquote><blockquote>Conclusion:</blockquote><blockquote>Gravity pulls the ball to the ground</blockquote><blockquote>Premises:</blockquote><blockquote>A bucket of water flows from higher ground to lower ground</blockquote><blockquote>There is force that pulls the water from higher ground to lower ground</blockquote><blockquote>That force is called gravity</blockquote><blockquote>Conclusion:</blockquote><blockquote>Water flows from higher ground to lower ground because of gravity</blockquote><blockquote>Premises:</blockquote><blockquote>River flows from higher ground to lower ground</blockquote><blockquote>There is force that pulls the river from higher ground to lower ground</blockquote><blockquote>That force is called gravity</blockquote><blockquote>Conclusion:</blockquote><blockquote>River flows from higher ground to lower ground because of gravity</blockquote><p>That last conclusion is the same proposition as:</p><blockquote>All rivers in the world flow downhill</blockquote><p>An argument is a set of premises and a conclusion. A premise is a proposition that supporting a conclusion. A conclusion is a proposition that inferred from the premises.</p><p>There are two types of argument, inductive and deductive. In inductive the scope is increasing from specific to general. While deductive, the scope is decreasing from general to specific.</p><p><strong>Deductive Argument</strong></p><p>One characteristic of a deductive argument is the conclusion will always be true when we accept the premises to be true. We can’t accept the premises but reject the conclusion. This is called validity, a deductive argument can be valid or invalid. A valid deductive argument is when it is impossible for the premises to be true but the conclusion false. When a deductive argument is valid and the premises true then we called the argument is sound. An example of deductive argument:</p><blockquote>All waters flows downhill</blockquote><blockquote>All rivers in Taiwan are water</blockquote><blockquote>Therefore, all rivers in Taiwan flow downhill</blockquote><p><strong>Inductive Argument</strong></p><p>Inductive arguments have many forms. But usually it is used for generalization from observation of some samples. But the conclusion of inductive argument can’t be guaranteed to be true. One famous example is the black swan case. In inductive argument there is no validity. Since the conclusion can’t be guaranteed to be true then an inductive argument is measured by it strength. It can be strong or weak or in between. If an inductive argument is strong and the premises are true then we call it cogent.</p><p>Below is the summary of inductive and deductive argument in a class diagram:</p><figure><img alt="Summar of deductive and inductive argument in a class diagram" src="https://cdn-images-1.medium.com/max/1024/1*pgXOkC3v8XkR_TMZjRvMYA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17654f864957" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-software-craftsman/logic-part-2-17654f864957">Logic — Part 2</a> was originally published in <a href="https://medium.com/practical-software-craftsman">Practical Software Craftsman</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up TLA+ Toolbox]]></title>
            <link>https://medium.com/practical-software-craftsman/setting-up-tla-toolbox-96c58fb3f79f?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/96c58fb3f79f</guid>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[formal-verification]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[tla-plus]]></category>
            <category><![CDATA[concurrency]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Mon, 05 May 2025 05:58:59 GMT</pubDate>
            <atom:updated>2025-05-05T05:58:59.676Z</atom:updated>
            <content:encoded><![CDATA[<p>TLA+ is a very popular formal methods language. It is based on Temporal Logic of Actions which is a logic developed by <a href="https://lamport.azurewebsites.net/">Leslie Lamport</a> to create specification for concurrent systems. Since I will be writing series of articles on TLA+, let’s start with setting up the toolbox.</p><p>You just need to download the toolbox from this <a href="https://lamport.azurewebsites.net/tla/toolbox.html">url</a>. Choose the one that matched your operating system, then install it. You can then run the toolbox and it will display the splash screen:</p><figure><img alt="TLA+ Toolbox’s splash screen" src="https://cdn-images-1.medium.com/max/886/1*KCAUvSc031LQ-MI-oA4zTg.png" /></figure><p>After it finished initializing then it will display the main screen. An Eclipse based desktop application:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DDCXXzPgEbO2aUmuBBioxQ.png" /></figure><p>Please be aware that your TLA+ Toolbox’s left screen will be different than mine since I already wrote several specs there.</p><p>Test Drive</p><p>To make sure the installation is successful, let’s create a simple spec. Click File &gt; Open Spec &gt; Add New Spec…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tgJCK0ca4L9P0YD_yM_rKg.png" /><figcaption>Add New Spec menu item</figcaption></figure><p>The New TLA+ Specification dialog will appear:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayXP5H6DFiyFtvzObq110g.png" /></figure><p>Click Browse… and create a new folder for the new specification. Let’s name it as TestDrive and click the Create button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0sUwplV4ea8TTcYJfGiXSA.png" /></figure><p>The TestDrive folder will be created. Make sure the TestDrive folder is selected and Enter TestDrive.tla as the file name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olVT21UnXK2wNI6_ZrRokw.png" /></figure><p>TestDrive.tla will be created insidet the TestDrive folder. Click the Finish button to start writing the spec.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZcQSNIf0rZP-TGodkriMQ.png" /></figure><p>Your main window will show the new empty TestDrive.tla spec.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5uiCNK0_fkM7OcNKxToLkg.png" /></figure><p>Enter these PlusCal codes starting on line 2 above:</p><pre>EXTENDS Integers<br><br>(* --algorithm test_drive<br><br>variables i = 0;<br><br>begin<br>    i := i + 1;<br>end algorithm;<br><br>*)</pre><p>Then click File &gt; Translate PlusCal Algorithm:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ied_YXJvGk-QaTbdEj1emg.png" /></figure><p>The toolbox then translated the PlusCal code into TLA+:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-YG_wCFobKoUpJiLM4nwDA.png" /></figure><p>To run it, we need to create a new model. Right click on the TestDrive module node on the left tree and choose New Model…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPVrVGfuO2o5XQFUxGAKJQ.png" /></figure><p>Just use the default Model_1 name then click the OK button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbyf7Js30Vb3Ku4_tD8zLA.png" /></figure><p>Make sure the Temporal Formula option is selected and the value set to Spec.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hyOBxqMznwDYSxInRqmvdQ.png" /></figure><p>Also make sure the Termination properties is selected. Then continue to click the green play button to run the model checker. The model checker will finished with error:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HQOilcySb4aHOcmO4qlHzg.png" /></figure><p>This mean you’re TLA+ Toolbox has been installed successfully.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96c58fb3f79f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-software-craftsman/setting-up-tla-toolbox-96c58fb3f79f">Setting Up TLA+ Toolbox</a> was originally published in <a href="https://medium.com/practical-software-craftsman">Practical Software Craftsman</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logic — Part 1]]></title>
            <link>https://medium.com/practical-software-craftsman/logic-part-1-af2faebf1f2e?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/af2faebf1f2e</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[logic]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Thu, 24 Apr 2025 11:47:26 GMT</pubDate>
            <atom:updated>2025-04-24T15:37:25.493Z</atom:updated>
            <content:encoded><![CDATA[<h3>Logic — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ZtFdlp7Tjb1LiUWZlpUb8g.jpeg" /></figure><p>What’s the point of learning logic?</p><p>One of it is to be able to find answers without complete information. Below story is an example:</p><blockquote>Diego has a meeting to attend. He wants to go there by train and taxi. If the train arrives late and there are no taxis at the station then Diego is late for the meeting. Diego is not late for the meeting and the train arrived late.</blockquote><blockquote>Were there taxis at the station?</blockquote><p>We do not need to go to the station at the same time Diego arrived with the train to know the answer. We can conclude, by logic, there were taxis at the station.</p><p>What we’ve done above is also called reasoning. <strong>Reasoning is a process of thought in which we make inferences: starting with information we already have, an inference draws some further conclusion based on that information [The Art of Reasoning]</strong>.</p><p>Another important benefit of logic is to have proper discussion in collaborative environment. Suppose a team arguing about abortion. One member argues that it’s wrong to treat abortion merely as medical procedure, like removing appendix, because the fetus is a potential person. Another member might argue that a woman should have the right to make decisions concerning her own body. Both are discussing two different issues on the same topic. The first one concerning on morality while the second one is about legality of abortion. Logic can help the team members to know the difference and find agreements.</p><p>To have proper discussion we need to be able to communicate and get our ideas across successfully. Especially if we have to communicate in writings where the readers can’t ask questions directly. We have to rely on logic as a shared framework to communicate properly. We also need to be able to listen to what others say. To put ourself on other people shoes. We need to be objective. <strong>Objectivity requires that you give a fair hearing to the evidence and arguments for the other side. Even if you reject them in the end, knowing why you reject them will give you a better understanding of your own position [The Art of Reasoning]</strong>.</p><p>When we are reasoning we are thinking. <strong>Thinking is a cognitive process we use in the attempt to gain knowledge or to understand something, as distinct from our emotional responses to things [The Art of Reasoning]</strong>. In a narrower sense, however, thinking is a particular kind of mental activity, the kind involved in solving a problem, planning an action, studying for a test, or defending your position on a controversial issue <strong>[The Art of Reasoning]</strong>.</p><p>Thinking is a skill that we can all improve. To improve our thinking skill we can do it by learning logic. <strong>Logic is the study of the methods and standards of inference [The Art of Reasoning]</strong>. There are different kinds of inferences that can be chosen for different kind of situations.</p><p>To communicate we need to use a language. We use the language to do groupings. <strong>Organizing a set of things into groups is called classification, and a word that stands for such a group expresses a concept [The Art of Reasoning]</strong>. For example, if we build an e-commerce web site we will classify the products into several categories like Electronics, Clothings, Pets, etc. Those names are called concepts. <strong>Concepts are ideas that represents classes of things we have grouped together</strong>. It is like folders. Definitions describe what is in the folders. A definition can clarify the boundaries of a concept. By having definitions we can prevent meaningless discussion.</p><p>There are six rules to build a definition:</p><ol><li>A definition should include a genus and a differentia.</li><li>A definition should be neither too broad nor too narrow.</li><li>A definition should state the essential attributes of the concept’s referents.</li><li>A definition should not be circular.</li><li>A definition should not use negative terms unnecessarily.</li><li>A definition should not use vague, obscure, or metaphorical language.</li></ol><p>Where did logic started?</p><p>Human came from primates, from animal. Animal only concerns with their own survival, mostly to fulfill their basic needs of hunger. Once their stomach is full, they feel peace and enjoy life. But human is different, once our basic survival has been fulfilled our brain continuous to find problems and answers. We call this pursuit to seek truth as philosophy.</p><p>At first, human use intuition to have understanding in philosophy. Then the students of Aristotle wrote a series of book called Organon which means tool. It contains formulation of Aristotle’s logic as a tool of thought to help philosopher to understand the world better. One famous idea from Aristotle is called syllogisms which are argument structure that appear to be indisputably valid. In a syllogism the structure contains premises and conclusion. The premises and conclusions fit together in such a way, that once we accept them as true then we must accept the conclusions as true. Example below:</p><blockquote>Premises:</blockquote><blockquote>All men are mortal</blockquote><blockquote>Socrates is a man</blockquote><blockquote>Conclusion<strong>:</strong></blockquote><blockquote>Socrates is mortal</blockquote><p>After Aristotle, logic continues being developed and one of milestone was from Euclid. Euclid used a logical method called <em>indirect proof</em> also called <em>proof by contradiction</em> or <em>reductio ad absurdum</em>. This method starts by assuming the opposite of what we want to prove and then continue to show the assumption leads to a conclusion that’s obviously incorrect. This method is widely used in math to proof whether a statement is true or false. The simplest example to remember reductio ad absurdum is:</p><blockquote>Statement: All people in Indonesia love coffee.</blockquote><p>We contradict the statement into: There are people in Indonesia who doesn’t love coffee.</p><p>Then we continue to proving the contradict statement. Let say by surveying my neighbors I found several people who doesn’t love coffee. So the contradiction is true that means we can conclude the original statement is false because both can’t be true.</p><p>The Stoics develop a little bit different kind of logic as Aristotle. They focused on conditional statements that take the form of <em>if…then…</em>:</p><blockquote>Premises:</blockquote><blockquote>If clouds are gathering in the west, then it will rain.</blockquote><blockquote>Clouds gathering in the west.</blockquote><blockquote>Conclusion<strong>:</strong></blockquote><blockquote>It will rain</blockquote><p>Even though there are similarities between Aristotle and Stoics kind of logic but the two school continue to develop friction which in turn causing logic to develop in two different ways. But in the end they both merged into one.</p><p><strong>Formal Logic</strong></p><p>Formal logic or also known as symbolic logic is the study of logic by using symbols to replace words. There are three key contributors to symbolic logic: George Bool with his boolean algebra, Georg Cantor with his set theory and Gottlob Frege with his prepositional and predicate logic.</p><p>Traditional logic is light read since it doesn’t use symbols (even though Aristotle tried to develop his own symbolic logic). We can say, (traditional) logic was not math, it was like literature or poetry. But we need the compact version of logic or symbolic logic to be able to manipulate them like mathematician manipulate numbers and equations.</p><p>One important take away that we should remember is symbolic logic is a way to turn words and sentences into arithmetic. Once we have them in the form of symbols then we can do calculation to them. We can do the calculation manually or use computing device such as an electronic computer to do the calculation. Then we have build our own automation system that can help us to do real work. This is the fundamental theory of building an electronic computer.</p><p>What is logic then?</p><p><strong>Logic is the study of the methods and standards of inference</strong> <strong>[The Art of Reasoning]</strong>.</p><p>In this first part, we have discussed the overview of logic, its benefits, and histories and how it contributed to development of computers. We will continue on the second part to get more deeper into it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af2faebf1f2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-software-craftsman/logic-part-1-af2faebf1f2e">Logic — Part 1</a> was originally published in <a href="https://medium.com/practical-software-craftsman">Practical Software Craftsman</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to level up our software development skill and craft?]]></title>
            <link>https://medium.com/practical-software-craftsman/how-to-level-up-our-software-development-skill-and-craft-2494636e94d0?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/2494636e94d0</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Tue, 22 Apr 2025 10:57:31 GMT</pubDate>
            <atom:updated>2025-04-22T10:57:31.169Z</atom:updated>
            <content:encoded><![CDATA[<p>Based on <a href="https://shiftmag.dev/unhappy-developers-stack-overflow-survey-3896/">2024 survey</a>, 80% software developers are unhappy. They are unhappy because they have no control and no progress. That is why as a software developer we have to take control of our craft and level it up.</p><p>How to level up our craft? First, we have to divide our knowledge into abstract knowledge and concrete skills. Abstract knowledge can be applied into multiple areas. It stands through time and doesn’t change. It doesn’t need any tooling. While concrete skills depends on current standard, current trends of tooling. Employers will hire us based on our concrete skills because that’s where the job gets done. But the most valuable is the abstract knowledge because if trends are moving we can follow it along.</p><p>An example of abstract knowledge is logic. The concrete skills are TLA+, TypeScript, and many others. Another ones are OOP, UML, Design Patterns, DDD. The concrete skills are StarUML, TypeScript, Ruby on Rails, and other OO languages. The more we get better at the abstract knowledge the easier to use it in the concrete skills. It is better if the concrete skills that we choose is not changing so it is also improve over time. Ruby on Rails is one example.</p><p>A little bit about myself. I started my programming journey when I entered university on 1997. The world was dominated by IBM PC and Microsoft. It was in transitioning period from DOS to Windows 95. I was using Turbo Pascal for DOS as my first IDE and programming language. I learned about coupling, cohesion, etc.</p><p>Then the world move to visual GUI programming. Visual Basic taken the world by storm and followed by Delphi. It was fun to dig into MSDN documentations and calling Windows API. Active Server Pages (ASP) was also getting popular to build server side applications. It hides the complexities of CGI. It was a headache to maintain sphagetty ASP codes especially it allows to declare the same name for function and variable. I was scratching my head scrolling pages-of-pages of ASP codes and found a function declared above but below it was assign a value.</p><p>And it is changing again. Microsoft pushed the usage of .Net to replace Visual Basic and many others of its own languages and tooling into one ecosystem. There was no startup but there was ISV (Independent Software Vendor). JVM and Java has matured first before .Net and C#. Strict code architecture and conventions was applied by many teams.</p><p>Suddenly iPhone took over the world. Building apps using weird syntax in Objective-C. Surprisingly, Objective-C offered so much better experience in coding compared to others OO languages like Delphi, C#, and Java. It was very fun to program in Objective-C. I even tried to build an OS for Nintendo DS and that’s where I learned that core of OS features is came from the microprocessors.</p><p>Then came Nodejs and the startup movement. I joined one of the famous startup in Indonesia and that is the first time I worked with a product manager. I used to have waterfall mindset then I realized how the game was played different by the startups using lean and MVP. Unfortunately, the devs are controlled by the PM and it might be okay if the PM is great but most PMs are not great. The startup have too many people working to solve easy problem like technical support. I decided to build a chatbot using RiveScript to solve all the existing problems once and for all. I didn’t followed the PM direction and following the CTO direction and proving there is a better way that can solve the organization existing problems.</p><p>Fortunately, I joined another company where I can have freedom to handle a client directly and help them build a startup from scratch. It was fun but I faced growth problem and didn’t knew how to solve it. I’ve read the growth hacking book by Sean Ellis but didn’t understand what it means.</p><p>In another startup I finally found the answer to the growth problem. I finally knew how growth hacking works. How to use the Northstar and the metrics. Unfortunately, the product team didn’t understand. I decided to took action and asked permission later (as directed by the COO) and it was creating tension and I got fired.</p><p>Based on my experiences, developers are problem solvers. They want to solve problems. They will not happy if they believe they can solve problems but they don’t have the chance to solve them. This is aligned with <a href="https://www.svpg.com/developer-powered-innovation/">modern project management</a> taught by Marty Cagan.</p><p>Developers are builders. We want to build something and change the world. But without the proper knowledge it will be hard to do it. So beside the technical abstract knowledge and concrete skills we also need to know product management and marketing and other knowledge required to make change happen.</p><p>I created <a href="https://medium.com/practical-software-craftsman">Practical Software Craftsman</a> publication as a place where developers around the world can hone their craft and acquired the knowledge and skills to build something and change the world and make it a better place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*2VwxJT_h08_PXwuPbM3ZwQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2494636e94d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-software-craftsman/how-to-level-up-our-software-development-skill-and-craft-2494636e94d0">How to level up our software development skill and craft?</a> was originally published in <a href="https://medium.com/practical-software-craftsman">Practical Software Craftsman</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Empty Software Craftsmanship]]></title>
            <link>https://medium.com/practical-software-craftsman/the-empty-software-craftsmanship-cefd04ed67dc?source=rss-cc5dcf750225------2</link>
            <guid isPermaLink="false">https://medium.com/p/cefd04ed67dc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Irwansyah]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 06:42:55 GMT</pubDate>
            <atom:updated>2025-04-21T06:42:55.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QzWKOn-efkZFThQ7kTc07g.jpeg" /></figure><p>There was a movement signed in manifesto, <a href="https://manifesto.softwarecraftsmanship.org/">The Software Craftsmanship Manifesto</a> on April 2009. It focuses on practicing software development as a craft and to build well-crafted software. It was a very good intention. I proudly joined the movement and called myself a software craftsman. Because I value quality and want to have satisfaction as a craftsman working his craft.</p><p>But The Software Craftsmanship Manifesto is an empty movement. Nothing happened ever since. Only several books got written which contains nothing practical. Nothing that I as a software developer can take my skill and craft to another level. In fact the based on <a href="https://shiftmag.dev/unhappy-developers-stack-overflow-survey-3896/">2024 survey</a>, 80% software developers are unhappy. They have no control and have no progress. Both are contradicting with what a craftsman really is. A craftsman has control and his craft kept progressing and getting better with time.</p><p>Now, the question is, how can we improve our craft significantly?</p><p>Stay tune! The answer is coming!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cefd04ed67dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-software-craftsman/the-empty-software-craftsmanship-cefd04ed67dc">The Empty Software Craftsmanship</a> was originally published in <a href="https://medium.com/practical-software-craftsman">Practical Software Craftsman</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>