Proof point → Anyone can claim fundamentals. Mine are 68 repositories deep, four paradigms wide, and a decade long.

🩻 Problem

Tech leadership fails when it’s held by people who talk technology but never did the unglamorous work of learning it properly. The question any builder should answer: where is the proof of your foundations?

🔨 Solution

This collection is that proof - 68 repositories archived in one deliberate sweep (May–June 2021) and still receiving updates as recently as 2026:

The layers

  1. High school (~2014–2015) - AP Computer Science Java labs and VB.NET applications (inventory systems, calculators) - the earliest preserved layer.
  2. University (Swansea, UK) - a complete degree archive: modules from Programming Fundamentals through HCI, Concurrency, Software Engineering, Databases, Computer Graphics, Algorithms, and Formal Languages & Automata, including the CS-230 group project Artatawe.
  3. Four paradigms - 34 Java repos (imperative/OO), 16 Prolog repos (logic: N-queens, ancestry trees, train routing, cuts and negation), 7 Haskell repos (functional: types, IO, concurrency), plus assembly and batch scripting.

Highlights

  • java_vision-3d - a volumetric medical-image renderer over the classic 113-slice CThead dataset: Swing GUI, maximum-intensity-projection mode, x/y/z slice navigation. Real computer-graphics coursework, not a toy.
  • java_vision-algos - image-processing algorithms (histogram equalisation, gamma correction, correlation) - revived and re-documented in May 2026, a decade after the era it came from.
  • java_concur / haskell_concur - the same thread-coordination problem solved in two paradigms.

📜 Philosophy

Fundamentals compound. The discipline to archive ten years of coursework - and the curiosity to revive an image-processing lab a decade later - is the same discipline real talent development must instill at scale.

🎓 Key learnings

  • Multi-paradigm fluency: the imperative, functional, logic, and low-level views of the same computational problems.
  • Graphics, concurrency, databases, and automata theory as studied subjects, not Wikipedia summaries.
  • How a structured curriculum builds an engineer - firsthand knowledge that directly informs designing one for others.

📈 Output & impact

  • 68 repositories, ~284 MB of preserved coursework, spanning roughly 2014–2026.
  • A documented, inspectable record of formal CS training from high school through degree completion.

🌍 Why this matters

Talent & Education. Whoever designs technical training - for a bootcamp, an academy, or a team - should know from lived, documented experience what rigorous education contains, which parts compound, and which parts are ceremony. This archive is that knowledge, in version control.

🚀 Hire me

Designing a technical curriculum or hiring bar? Let’s talk → · See also: TDA Academy · The thesis