Vadim Lysenko

Mod collections that arrive the way the curator built them, and stay that way.

Problem

A Vortex collection is a list of mods. Installing one rarely reproduces the curator's setup: file conflicts resolve differently, the load order drifts, and mods vanish from Nexus.

What I built

A package format that is a snapshot of a working setup, rebuilt and then proved: every archive hashed against a manifest, the curator's load order pinned and watched, a Collection Doctor that explains each problem with its repair, and an installer that follows a mod's whole requirement chain.

Result

Proven on a 1,900-mod Skyrim SE profile and a 950-mod Fallout 4 collection. On a 1,753-mod collection, 17,159 of 17,161 contested files go to the curator's winner; the other two are files the game never loads. Backed by 2,600+ tests.

I taught a 48k-star code-intelligence engine to read the JavaScript world: about 33,000 lines across eleven merged pull requests.

Context

GitNexus turns a repository into a graph of calls, routes and references that AI agents query. When the graph is wrong, agents are told live code doesn't exist.

What I built

JavaScript support on GitNexus's new scope-based engine, including CommonJS require, JSDoc types and class fields, then Vue single-file components on top of it. React in TypeScript: calls through JSX, hooks and higher-order callbacks, and components wrapped in forwardRef or memo. Server code too: NestJS routes, HTTP clients behind route tables, and Next.js build output kept out of the graph.

Result

JavaScript and Vue run on code I wrote, and React projects get a far more complete graph. All eleven pull requests were merged to the maintainers' review standard, in a codebase I didn't start.

My Alienware x16 R2 has four speaker amplifiers. Out of the box, Linux drove none of them.

Problem

The known workaround drove two amps, without their firmware, so the speakers ran unprotected and thin. Nothing about the other two was documented anywhere.

What I did

Decoded Dell's Windows driver configuration to find all four amps and how they are wired. Traced the missing firmware to an SPI clock left at 3 kHz, which the kernel already fixes for a sibling Dell laptop. Wrote an ACPI table override for four amps, a kernel fixup and the clock quirk, and mapped Dell's own amp tunings to the names Linux loads.

Result

All four amps running Dell's tuning. A DKMS package rebuilds the fix for every kernel update from that kernel's exact, signature-checked sources, and falls back to two amps rather than silence. Submitting it upstream is next.

Face unlock for the lock screen, sudo and polkit, designed so a face is never the only key.

What I built

A lock screen that runs face recognition as its own PAM service beside the password and fingerprint, on an infrared-only engine. Face can also approve sudo and polkit prompts.

The careful part

The password stays the authority: face pauses after five failures and asks for the password again every 48 hours, and the screen shows exactly what face unlock is doing at each moment.

Linux desktop apps people install from a store, each through a security review.

What they are

A status hub, air-raid alerts, a Telegram client, a window overview, a dictation front end, screen time, battery history and more, each with its own bar widget, panel and settings.

Result

Seventeen listed, fifteen verified. The marketplace's review sets a high bar: absolute tool paths, safe temporary files, bounded reads, deadlines on every process, no secrets in arguments. One app went through five rounds before it was listed.