This is where Parham and Elaheh learn things by building them.
Every repository here is a reference we wrote for ourselves: pick a language, a database, a protocol, or a tool, then write just enough code to find out how it actually behaves. Later, when the same question comes up again, the answer is already sitting here.
Which also means these repositories are deliberately unfinished. They are not libraries, they are not meant to be copied into production, and they are not always complete or idiomatic — they are the notes we took while working something out. Read them in that spirit and they are useful; read them as finished software and they will disappoint you.
Corrections and contributions are welcome 😊
There are far too many repositories here to list, so the naming carries the load:
<something>101— a first pass at a technology, taken far enough to understand it.rust101,ebpf101,qdrant101,cilium101, and many more follow this pattern.- coding challenges and interview exercises — take-home assignments, algorithm rounds, and system-design questions from interviews we actually sat. Kept because a problem someone else chose is a good way to practise, and because it is useful to look back at how we solved something under a deadline.
- everything else — smaller experiments, toys, and things that resisted a tidy name.
Start from the repository list and sort by whatever you care about.
Material we prepared to teach other people — courses, lectures, and exercises meant to be followed start to finish — lives in 1995parham-teaching. That one is curated. This one is the workbench.
