I’m Dominque — Director of Software Engineering by day, solo builder by night. I ship AI-assisted dev tools, sports apps, and systems that help me (and other devs) move faster without losing quality.
Every Monday starts a fresh sprint. Every Sunday, something ships — code, content, tooling, or a small experiment. No bloated roadmaps. Just focused reps.
It’s like being locked in the studio: headphones on, distractions off, track after track until the vision sounds right.
Read the Appaveli Mode story →I treat AI as a teammate — not a threat. These tools live in my terminal and browser, helping with code analysis, refactors, security, and content.
Open-source AI assistant for code analysis, refactoring, test generation, and security scanning across Java, Kotlin, Swift, Dart, C++, PHP, and JavaScript.
A growing suite of Python-based AI agents (CLI + web) for code refactors, code conversion, investing research, and creator tooling.
Internal CLIs and generators I use to keep my solo pipeline lean: scaffolding Java backends, native mobile projects, and boilerplate structures.
A shared platform powering all AppaveliTech tools: Java core services for auth and data, Python AI agents for intelligence, and native Swift/Kotlin apps on top.
I started with sports playbook tools and budgeting apps. Many of these are still live in the stores and evolve as I do.
Digital playbook apps for coaches and players. Basketball, hockey, and more — used to draw, organize, and share plays efficiently.
I also build tools around planning, budgeting, and personal systems — extending Appaveli Mode into everyday life workflows.
These ship in small iterations: new features added in weekly sprints, driven by real usage, not theory.
Personal systems Solo-builtI write about solo development, leadership as a Director of Software Engineering, and the mindset behind Appaveli Mode.
I’m Dominque, Director of Software Engineering by day, solo builder by night. I run AppaveliTech Solutions, LLC as my lab for AI agents, dev tooling, and sports / planning apps.
Some days I’m deep in architecture and leadership. Other days I’m in the terminal, running CLIs I built for myself. Either way, I stay in motion: learning, shipping, and documenting the journey along the way.