Damilare Osibanjo

To whoever found this —

I'm 17. I've been building software seriously for about five years. What started as scripting game logic in Lua evolved into writing OS kernels in C and building compilers in Go.

I don't build projects to fill a portfolio. I built karion_os because I wanted to understand what actually happens beneath the OS abstraction — bootloader sequences, memory paging, context switching. I wrote carv because I wanted a language with ownership semantics and pipe operators that compiled to C. I wrote gim because the existing monitoring tools were too heavy.

The pattern is always the same: I run into a ceiling, I don't accept it, I build through it.

TypeScript for speed of thought. Rust when correctness isn't negotiable. Go when I need to ship something that just runs. C when I need to be exact.

I'm not looking for someone to teach me fundamentals. I'm looking for hard problems — distributed systems, runtimes, compilers, infrastructure — and a team that ships real software.

If you're building something that actually matters, let's talk.

— Damilare