Engineering & technical experience

Software, Systems, and the Things I'm Teaching to Think.

My background started in IT infrastructure and systems administration. Since then, I've moved deeper into software engineering, AI systems, automation, and experimental robotics.

I like projects that require several different technologies to work together, especially when those systems have to respond to people or changing environments in real time.

My current work combines practical systems experience with independent AI development and ongoing engineering studies.

Discuss Collaboration

Areas of practice

Different Technologies. Connected Problems.

01 / Software & backend engineering

Tools, Services & Integrations

Python, C#, JavaScript, and SQL form part of my software toolkit. I build tools and backend applications that connect APIs, automation, real-time events, and user interactions.

02 / AI & agent systems

The Architecture Around the Model

Local language models and LLM application integration are part of my practical work. Agent orchestration, memory, context, tool use, latency, and external events are ongoing development concerns, alongside experiments in model customization and training workflows.

03 / Infrastructure & systems

A Practical Operational Foundation

Infrastructure support and systems administration taught me to work across server hardware, networks, dependencies, troubleshooting, documentation, and system integration, with reliability and real users in mind.

04 / Robotics & mechatronics

From Software to Physical Systems

I'm studying electronics, sensing, control, and robotics while assembling a lab. The industrial arm has been acquired but is not commissioned. End effectors and embodied AI are development interests, not completed industrial integrations.

05 / Audio & creative technology

Voices, Audio & Performance Tools

Vocal synthesis, audio processing, custom voicebanks, and DAW workflow tools connect my software work to music production and live performance. I handle the composition, vocal tuning, mixing, and production of my releases.

Engineering evidence

Four Problems I've Been Working On.

These examples show the problem, the technical work, and the current result. Public source and project descriptions are linked separately; not every project has public code.

01 / Interactive AI systems

AuroraChan AI

Operational / Ongoing development

Problem
How can a locally operated AI system respond to real-time stream events and communicate through a virtual performer?
What I built
An interactive AI VTuber combining LLM integration, event handling, agent behavior, software tools, supported game interactions, and virtual performer output. The model's behavior is one component; the surrounding application coordinates the interaction.
Technical challenges
Managing context, response timing, external events, and tool interactions while keeping behavior observable and controllable. Memory and behavioral adaptation remain areas of experimentation.
Current result
Aurora participates in conversations, supported game interactions, and live entertainment. The operational performer continues to evolve; improved memory, reliability, and additional integrations remain active development.

02 / Python, Discord & moderation utilities

Discord LinkBot

Public-source software

Problem
Discord links often need additional handling for safety checks, useful previews, and platform-specific formatting.
What I built
A modular Python bot with link handling, suspicious-link checks, optional external security scanning, richer previews, and per-server configuration.
Technical challenges
Coordinating external services, permissions, configuration, rate limits, and message handling. Security checks provide additional signals, not a guarantee that every malicious URL will be detected.
Current result
A publicly available Discord utility combining link handling and enrichment features. Its documentation and source are available for inspection.

03 / Synthetic voice research & open source

ALIZARIN Engine

Experimental voicebank beta / Framework in development

Problem
How can a distinctive synthetic voice be developed from computationally generated sound instead of recordings of an existing performer?
What I'm building
A synthetic voice research project exploring algorithmic sound generation, formant-inspired synthesis, machine learning experiments, and voicebank development for speech and singing applications.
Technical challenges
Turning synthetic source sound into a useful vocal identity, then developing tools and a reusable framework around it. Broader speech, singing, and compatibility goals are still research and development work.
Current result
An experimental primary voicebank is available by inquiry. The wider open-source framework remains in development, not a finished synthesis package.

04 / AI, gameplay systems & integration

Game Integrations

Mixed / Functional integrations and ongoing experiments

Problem
How can an external AI agent interpret a game's state and perform supported actions in an interactive environment?
What I built
Integration experiments connecting Aurora with game information and supported actions. The work involves game-state interfaces, external events, and action routing; available interfaces and implementation differ between games.
Technical challenges
Working within each game's available API or mod interfaces, representing useful state, and coordinating response timing. An integration that works in one environment doesn't imply support for every game.
Current result
  • Balatro: functional Aurora interaction
  • Schedule I: functional Aurora interaction
  • Minecraft: testing
  • Voices of the Void: partial integration

Functional AI interaction is distinct from a publicly downloadable game mod.

Professional systems background

A Foundation in Systems That Have to Work.

Practical IT infrastructure and systems administration experience taught me to diagnose problems across hardware, software, networks, and their dependencies, rather than assuming the fault belongs to one component.

Supporting real systems and users also means making technical problems understandable, documenting what matters, and considering maintenance and reliability alongside the immediate fix.

  • Hardware and software troubleshooting
  • Networks, connectivity, and dependencies
  • System integration and maintenance
  • Technical communication and documentation
  • Operational support and reliability

Education & engineering direction

Formal Study Meets Independent Research.

  1. Earlier study

    A Software Foundation

    Earlier college-level study in programming and general education provided a foundation for continued work in software and engineering.

  2. Currently pursuing

    Mechatronics & Computer Science

    Ongoing studies connect software with electronics, control, and physical systems, with mathematics as an additional area of interest.

  3. Longer-term direction

    Robotics & Embodied Intelligence

    Learning how intelligent systems can interact with physical environments safely and observably. This is a research direction, not a completed robotic integration or an existing graduate research appointment.

Tools & technologies

A Toolkit With Context.

These groupings distinguish established use from development experiments and areas I'm still learning.

Used in projects or professional work
Python, C#, JavaScript, SQL, API and event integrations, server hardware, systems administration, networking, and diagnostics. Audio work includes UTAU, Vocaloid, Synthesizer V, vocal tuning, and production workflows.
Current development & experimentation
Local LLM applications, agent orchestration, memory and context management, tool calling, game interfaces, synthetic voice tools, and DAW automation. Model customization, dataset preparation, and fine-tuning workflows are experimental work, not claimed benchmarked training results.
Academic & longer-term interests
Mechatronics, sensing, control, electronics, end effectors, and embodied AI. ROS and PLC concepts belong here as learning areas, not demonstrated professional robotics expertise. Industrial-arm commissioning remains ahead.

Engineering approach

How I Approach Difficult Systems.

I tend to build systems in layers, starting with the behavior I need, then figuring out which components have to cooperate to make it work. Testing, debugging, and documenting those connections is as much a part of the project as writing the code.

  1. Define the Interfaces

    Break the problem into smaller components and make the inputs, outputs, and dependencies explicit.

  2. Test the Connections

    Iterate on behavior, inspect failures, and choose tools that fit the task. Integrate existing technologies where they help.

  3. Keep It Understandable

    Design for observation and maintainability, and document limitations and current status instead of hiding uncertainty.

Follow the evidence

Public Work, Source & Further Reading.

Opportunities & collaboration

Interested in Building Something Together?

I'm interested in opportunities involving software engineering, AI systems, infrastructure, robotics, and the technology behind interactive media.

If my work overlaps with what your team is building, I'd be interested in hearing about it.

View GitHub