> SYSTEM.STATUS: ONLINE
Hey,
I'm Fajar!Hey,
I'm Fajar!Hey,
I'm Fajar!
Fajar Abdi NugrahaA Software Engineer and sometimes a Solution Architect who builds and operates systems. My job is to keep production running, annual plans aligned, technical decisions made responsibly, deliveries predictable, and scope honest.GovTech / Cloud Services / Microservices
STATUS:SYSTEMS_OPERATIONAL
LOAD:42.42%
Terminal // dev_root
>
cat telemetry.json | grep engine
Language_StackJava, Node.js, Go, .NET, PHP
Primary_FocusBackend, Sometimes Frontend
>
./mount_volumes.sh --force
Mounting virtual filesystems... [OK]
>
01 // HARDWARE NODES
[VIEW_ALL_MODULES]02 // CORE PARADIGMS
01
CORRECTNESS BEFORE CLEVERNESS
Avoiding elegant solutions that obscure guarantees. Preferring explicit, sometimes verbose designs that make invariants, constraints, and failure behavior undeniable.
02
DETERMINISTIC BEHAVIOR
Building systems where outcomes are predictable under the same inputs. Minimizing hidden randomness through controlled concurrency, ordering guarantees, and reproducible execution paths.
03
SYSTEMS LIE UNTIL PROVEN OTHERWISE
Assuming every system is incorrect by default. Validating behavior through failure cases, edge conditions, and real execution paths instead of trusting design assumptions.
</>
03 // TECHNICAL ARSENAL
LANGUAGES
Java, Node.js, Go, .NET, PHP, Vue
INFRASTRUCTURE
AWS, EKS, Kubernetes, Docker
DATABASES & MESSAGING
OracleSQL, MySQL, DuckDB, Redis, Kafka, RabbitMQ
04// OPERATIONAL AXIOMS
- >Firefighting doesn't scale. Build systems that are boring in production.
- >Documentation is infrastructure. If it's not documented, it's debt.
- >Capacity must meet commitment. Optimism is not a strategy.
- >Ship safely over ship quickly. Delivery without safety is shipping problems.
RULES