---
title: "El-Perintis"
url: "https://ridwaanhall.com/projects/el-perintis"
markdown: "https://ridwaanhall.com/projects/el-perintis.md"
summary: "A small Python piece on building from scratch versus inheriting a legacy, told as two simulations."
---

# El-Perintis

> A small Python piece on building from scratch versus inheriting a legacy, told as two simulations.

- Category: Education
- Status: Completed
- Started: July 31, 2025
- Built with: FastAPI, Python, pytest
- Source: https://github.com/ridwaanhall/el-perintis

## About

### The problem

Choosing between building something new and carrying a legacy forward is one of the hardest calls in software, and it is usually argued in the abstract.

### The approach

I wrote the choice as code. The perintis branch (the pioneer) builds from zero with modular, non-OOP scripts: an idea, an execution and a narrative. The pewaris branch (the heir) continues an existing legacy with classes such as Legacy, Pewaris and Simulator. The idea is adapted from the philosophy of Ryu Kintaro.

- Simulated outcomes: success, failure, viral and pivot.
- A reflective narrative generated from each result.
- Automatic logging to log_perintis.txt and log_pewaris.txt, and unit tests for both flows.

### The result

El-Perintis is a compact teaching piece that makes an architectural decision concrete, useful for discussing procedural and object-oriented design.

## Features

- **Two Paradigms**: A non-OOP pioneer branch and an OOP heir branch for the same story.
- **Simulated Outcomes**: Success, failure, viral and pivot, chosen by the simulation.
- **Reflective Narrative**: Each outcome produces a short narrative of what happened.
- **Logs and Tests**: Automatic log files and unit tests for both branches.

## Tags

Cultural Commentary, El Perintis, Perintis, Python Oop, Ryu Kinarto

## Elsewhere

- This page for people: https://ridwaanhall.com/projects/el-perintis
- Index of every page as Markdown: [llms.txt](https://ridwaanhall.com/llms.txt)
