Victoria's Code STA / 01
Victoria's Code

Software engineer._

Building reliable software across defense, finance, and healthcare.

Years
25+
Sectors
6
Build logs
4
Blog entries
28
Last entry
2026.08.24
Capability

What I do

AI

AI & Intelligent Systems

RAG, local LLMs, agentic workflows, and secure AI for air-gapped environments.

MC

Mission-Critical Software

High-reliability systems aligned with defense and aerospace standards.

ARCH

Architecture & Integration

Clean Architecture, microservices, event-driven systems, and system-of-systems integration.

RT

Real-Time Platforms

Telemetry, GPS tracking, simulation systems, and distributed data pipelines.

Sector experience

Where the systems ran

SectorWork
Defense & AerospaceMission systems, tactical communications, geospatial data, and standards-based engineering — MOSA-aligned, including FACE conformance and ICD-based interface design
FinanceEnterprise applications, backend services, secure data processing, business-critical systems
HealthcareData systems, analytics, reporting, regulatory-aware software
Industrial AutomationProcess control, real-time systems, plant operations
Real-Time SystemsGPS tracking, telemetry, simulation, event-driven applications
Consulting & IntegrationCross-domain solutions, rapid delivery, system modernization
From the blog

Latest entries

Pulled straight from the posts folder — this list is never hand-edited.

2026.08.24

Whodunit: The Case of the Crashing Computer

An evening of pilot testing where everything kept crashing. The GPU was framed by a ghost, the AI had an alibi with receipts, and the real culprit was me — running every project at once on hardware I'd forgotten was finite. Also: the one-command triage tool this mess earned.

NARRA Honest FailureDebugging
Latest
2026.08.15

The EMERGENCY button that did nothing

A command came back REJECTED with no reason given. Chasing it down led me to a button labelled EMERGENCY that had never worked on that aircraft type — not broken, not disabled, just quietly incapable while looking exactly like a working control. The bug was one word in a list.

GCS Deep DiveSafety
2026.08.14

A number is not a measurement

The console said the drone was at 394. Four hundred what, measured from where, and as of when? A bare number on an operations screen is three questions pretending to be an answer. Today I shipped the unit, the reference frame, and the age — and a test caught me quietly widening a safety limit while converting between them.

GCS StatusTelemetry
2026.08.13

Hardware first, AI later

The plan for a device-agnostic validation framework for autonomous systems. Starting where it matters: can we talk to a drone and listen to the spectrum? Simulation is running; the physical hardware goes on the bench next.

SDR HardwareRTL-SDR
2026.08.11

A Dead Drone That Looked Alive

This is the most important safety bug I've fixed on this project, and the scariest kind: the drone lost its link, and the console kept showing it flying. Frozen position, frozen battery — a calm, healthy-looking asset that was no longer talking to anyone. Silence has to look like silence.

GCS Build LogSafety
Contact

Let's build something impactful