I’m interested in the mechanics behind reliable software — not just code that runs, but systems that scale, recover, and remain understandable under pressure.
I spend my time between mathematics, systems design, and security. My interest isn’t in collecting buzzwords; it’s in understanding the underlying structure of ideas and turning that understanding into dependable engineering.
focus = {
"mathematics": ["linear algebra", "calculus", "optimization", "logic"],
"systems": ["distributed systems", "networking", "operating systems"],
"security": ["threat modeling", "vulnerability analysis", "secure design"],
"languages": ["Python", "C++"],
"approach": "reason deeply, build carefully, verify relentlessly"
}I like problems with depth — where correctness matters, where architecture matters, and where the right answer is not just fast but principled.
| Area | Direction |
|---|---|
| 🧮 Foundations | Linear algebra, optimization, logic, abstraction |
| 🐍 Languages | Python for clarity, C++ for performance and control |
| 🌐 Systems | Fault tolerance, protocol design, networked behavior |
| 🔐 Security | Adversarial thinking, secure architecture, resilience |
| 🖥️ OS & Runtime | How software interacts with the machine beneath it |
| 🧠 Engineering | Correctness over cleverness, depth over noise |
[█████████░░░░░░░░░] Mathematics — deepening fundamentals
[███████░░░░░░░░░░░] Python / C++ — strengthening tools
[█████░░░░░░░░░░░░░] Distributed Sys — understanding coordination
[███░░░░░░░░░░░░░░░] Security — exploring edges and weaknesses
[███████████████████] Curiosity — never plateauing
I’m not chasing a polished résumé. I’m building a foundation strong enough to support real systems, real understanding, and real problem solving.
If you're building with a similar mindset — deep learning, systems thinking, and engineering with intent — I’d be glad to exchange ideas.
⚡ Currently debugging: assumptions, one iteration at a time. ⚡