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 π.
I care about correctness, performance, and understanding what's actually happening underneath the abstraction.
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
rmwith an undo button. A reversible file-deletion TUI built with Go and Bubble Tea.
Your filesystem, locally classified.
A file organiser using local ML inference to classify and move files without sending them to the cloud.
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.
Warning
If you're building your backend in Python, please don't contact me.
I've had three startups speedrun the same conversation:
"We built the backend in Python." "It's getting difficult to maintain." "Can you fix it?"
I am tired. I am not cleaning up another vibe-coded Python backend. π
Email: nurysso [at] proton.me
Discord: nurysso



