QuetiemalsUnity · C#
Match-3 RPG and the origin point of the Eyuforyia universe. ScriptableObject-driven content pipeline, gacha economy, encrypted saves.
Google Play →
Software · Games · Web · Mobile · Bossier City, LA · Teq Vault LLC
One person, ten shipped products — four titles live on Google Play, a suite of web and desktop tools, and browser games running without an engine. I write code, direct AI tooling hard against specs I write, and own the architecture, the review, and the whole build-and-release chain that gets it to a store.
Status is current, not aspirational.
Match-3 RPG and the origin point of the Eyuforyia universe. ScriptableObject-driven content pipeline, gacha economy, encrypted saves.
Google Play →
Real-time multiplayer over Relay/Lobby, leaderboards, seasonal trophy ladder, non-consumable IAP with server-side receipt reconciliation. Also submitted to Amazon Appstore.
Google Play →
Narrative match-3 built on the same content architecture, with a story layer that shares canon with the novels and the planned series.
Google Play →
Course platform I write and maintain: Java, Python, Git, Unity, embedded systems, PLC programming, cybersecurity fundamentals.
Open teqvault.study →
Multi-provider AI platform with server-side entitlement verification and model gating. Frontend and backend deployed separately.
LivePuzzle-adventure falling-block RPG written without an engine — full audio system, offline PWA infrastructure, then wrapped for Android and ported to Fire tablets.
Play in browser →
Music app with background playback and a Supabase-backed supporter tier, shipped to Google Play as a signed AAB.
Google Play →
Document reader and editor in parallel Electron, web, and student-desktop builds — docx rendering, Windows file association, native context menu.
Open TeqDocs →
Canvas tower defense with a deck-building layer — towers are cards drawn from an unlockable pool, with meta-progression persisted between runs. Every map is declared as a list of entry lanes converging on one exit, so single-, dual-, and triple-lane boards all run through one geometry path, and projectiles carry real travel time with a fallback impact point when their target dies mid-flight.
Play in browser →
Video player for local and remote sources — scrubbing, fullscreen, picture-in-picture, background playback. Built and ready to launch.
In testingMy own backend platform, replacing third-party BaaS across every product. Own-table auth with argon2, files on disk, Caddy in front, restic backups, self-hosted.
Offline-first developer tools sharing one design system — sprite slicer with magic-wand and flood-fill masking, atlas packer, palette and font utilities.
LiveFile-recovery tool with sector-aligned Windows raw device access; and a remote-desktop app with a custom signaling server and Windows agent.
OngoingWhere the leverage comes from, and where it stops.
Ten products from one person needs leverage, and I'd rather name it than have you wonder. AI tooling drafts a lot of implementation from specifications I write, and I write plenty of code directly — the systems work, the parts with real constraints, and anything I'd rather understand than inherit. What the tooling buys is throughput. What it costs is that nothing arrives trustworthy by default, so architecture, review, and the entire build chain stay mine.
Data model, module boundaries, economy math, where state is authoritative, what ships and what waits. A model doesn't get these calls, because it can't see the consequences three releases out.
I write the code that carries real constraints and hand off the rest against tight, single-concern specs. Vague prompts produce plausible code that quietly does the wrong thing, so the specification is itself the engineering work.
Every line read, then run on a device, then built and signed and submitted by hand — npm and Expo toolchains, Gradle, keystores, Play Console. The audit below is what the reading catches: XOR passed off as encryption, probability math that looked right and wasn't, cooldowns trusting a clock the user controls.
Four decisions, and why they went that way.
I went back through a shipped match-3 RPG assuming it was wrong somewhere. Save data was XOR'd and labelled encryption — replaced with AES. The soft-pity gacha math was subtly incorrect and under-rewarding players. Cooldowns trusted the device clock, so a settings change skipped them. Three real vulnerabilities in code that ran fine and looked fine. Fixed in the live build.
BaaS pricing scales against you and the exit cost grows the longer you wait, so I specced TeqBase to replace it: Postgres, Node LTS, a thin Fastify layer, argon2 auth I own, files on disk, restic backups. Nothing novel, nothing I can't debug at 2 a.m., no vendor with a say in my margins. Currently building it.
The Connect 4 CPU was beatable in a way that felt cheap. Rewrote the evaluation with depth-adjusted scoring so near-term threats outweigh distant ones, and added center-first move ordering to prune harder. Better play at the same search cost.
Electrical fault isolation on base means paper schematics and guesswork. I'm building a PWA that pairs the one-line diagram with an interactive map for pin placement, cached through a service worker so it works with no connectivity — which is exactly when you need it. In progress, and the constraint drives the design.
Things I've shipped with, not things I've read about.
Where the discipline came from.
Every line of product code, every store submission, every backend decision. Publishing games under the Average Jude Games label.
Airfield and facility electrical systems. Wrote a full airfield lighting training course for incoming airmen from official technical references.
Software Engineering concentration. 4.00 GPA, President’s List. Computer graphics with OpenGL, embedded systems on Raspberry Pi, data structures and algorithms.
Four doors into the same body of work.
The parts nobody sees: sector-aligned raw device reads in Python, a WebRTC signaling server, server-side entitlement checks and receipt reconciliation, a backend platform I'm building to replace rented infrastructure, and a security audit that caught three real vulnerabilities in shipped code.
Three Unity titles live, plus one built engine-free in plain JavaScript. Gameplay systems, content architecture, economy math, opponent AI, IAP and store release.
Unity and React Native / Expo, both shipped as signed AABs through Play Console. Comfortable with the unglamorous half — signing, tracks, testing rollout, store policy.
Next.js and React front ends, Fastify and Postgres behind them, offline-first PWAs, and a self-hosted deployment I run myself rather than rent.
One design system across the whole Teq Vault tool suite, and interfaces built for real constraints — a sprite slicer that has to feel precise, a fault-isolation map used with no signal.