That's Eulix parsing the Linux kernel.

I build software for people who have to understand systems that are too large to keep in their head.

I'm Nurysso a systems engineer interested in compilers, code analysis, developer tooling, and software that has to deal with reality rather than toy examples or basic curds 🍛.

Current master piece of work

Open-source · Polyglot · Fast Most code retrieval systems treat a repository like a collection of documents. Eulix treats it like a program. Given a question, Eulix progressively builds context through:

Exact symbol
    ↓
Keyword search
    ↓
Semantic retrieval
    ↓
Call graph expansion

The cheap path runs first. The expensive path only runs when necessary.

Polyglot Resolution via Inverted Symbol Maps PRISM resolves cross-file relationships through a parallel five-phase pipeline built with Rayon. Instead of throwing a huge pile of text at an LLM and hoping it figures out the architecture, Eulix tries to determine which code actually matters first. That's the interesting part. → Explore Eulix

rm with an undo button. A reversible file-deletion TUI built with Go and Bubble Tea.

Your filesystem, locally classified.

Hyprland configuration with opinions.

systems
├── compilers & parsers
├── static analysis
├── code intelligence
├── developer tooling
├── local inference
└── Linux

And occasionally things that exist purely because they seemed fun to build.

Rust · Go · TypeScript · Python · Bun
Linux · MySQL · MariaDB

I'm open to remote or on-site opportunities across EMEA / APAC. I'm particularly interested in teams working on:

• systems software
• developer infrastructure
• compilers / language tooling
• static analysis
• large-scale developer platforms
• performance-critical software If your codebase is large, messy, old, fast-moving, or all four — that's usually where I want to be.

Email: nurysso [at] proton.me
Discord: nurysso