01
Distributed systems fundamentals
worked throughThe vocabulary of why systems fail: the theory behind every architecture decision.
Stack · 27 entries, with depth stated
Everything here carries how deep it goes and how long I have used it. Four means I have taken it apart under load and know where it breaks. Two means I am productive in it and would not architect a system on that alone.
6 · what I write in
JavaScript / Node.js
3 years
Python
2 years
C++
2 years
PHP
1 year
Lua
1 year
Bash
2 years
7 · what I build on
Express
3 years
React
2 years
Vue.js
2 years
Next.js
1 year
Django / FastAPI
1 year
Laravel
1 year
Socket.IO / WebSockets
2 years
3 · where state lives
MongoDB
3 years
Redis
2 years
SQL (MySQL / PostgreSQL / SQLite)
2 years
4 · where it runs
AWS
2 years
Cloudflare R2
1 year
Docker
1 year
Firebase / Vercel / Hostinger
2 years
3 · the attacker's side
Penetration testing (eJPT)
1 year
OWASP API security
1 year
Network engineering (CCNA-level)
2 years
4 · the part that is not a library
System design & architecture
2 years
API design (REST, 178-request scale)
3 years
Payment integration (Stripe, Qcard, Zain Cash, SindiPay)
2 years
Team leadership & mentoring
1 year
9 areas
The deliberate list, worked through in order rather than picked up incidentally. Each area has a goal and the specific things it covers, so it can be checked in an interview rather than taken on faith.
01
The vocabulary of why systems fail: the theory behind every architecture decision.
02
Beyond sockets into durable, replayable event streams.
03
From "it works on my machine" to declarative, self-healing deployments.
04
Logs, metrics and traces as one debugging workflow, not three dashboards.
05
Beyond REST: contracts, versioning and transport chosen deliberately.
06
Every commit proves itself before it ships.
07
The testing pyramid as practice, not diagram.
08
From using AWS to architecting on it.
09
The eJPT foundation, weaponized for defense at the architecture level.
Kafka, outbox relays, optimistic concurrency and connection-pool arithmetic are on this list because a system broke and taught them. The systems index says which one, and the decisions index says what each choice cost.