Selected work from a long career.

Graphics and engine programming

The challenge. Real-time three-dimensional graphics were hard problems in the late 1980s, long before commercial engines made them routine.

Mark's work. Mark developed an early three-dimensional, ray-traced game engine, working across graphics programming, rendering, performance optimization, and engine architecture.

Why it matters. It is evidence that Mark was solving difficult graphics and performance problems by hand, years before the tools and hardware made that work ordinary.

Engine-level graphics and animation

The challenge. Arcade titles of the era pushed the hardware hard, demanding fast, memory-efficient sprite handling and animation.

Mark's work. Mark contributed to sprite-engine and game technology associated with the Mortal Kombat project, working at the level of engine graphics, animation, sprite handling, and performance.

Why it matters. It reflects deep, performance-critical work on technology behind a widely recognized title — the kind of low-level discipline that still informs how Mark evaluates systems today.

Development leadership

The challenge. Moving fax traffic reliably across networks and the early internet required careful software architecture and communications engineering.

Mark's work. Mark led development of the Harmony Fax Server and Client, spanning software architecture, networking, communications, and internet-based fax technology.

Why it matters. The technology was later acquired or rebranded by UUNET as UUFAX — a product built well enough to be adopted by a major telecommunications organization.

Combat systems and game mechanics

The challenge. A deep role-playing title needs combat that is responsive, balanced, and believable across countless situations.

Mark's work. Mark worked on combat-engine technology associated with Baldur's Gate, involving combat systems, artificial-intelligence patterns, game mechanics, graphics algorithms, and performance.

Why it matters. It is complex interactive-systems work where correctness, behavior, and performance all have to hold together at once.

Chief Information Officer / Chief Technology Officer

The challenge. Utility billing and payment demand secure banking connectivity, accurate customer records, and workflows that cannot afford to be wrong.

Mark's work. Mark directed the design and development of Utiligate, an online utility payment and account system, covering payment processing, secure banking connections, customer systems, databases, integrations, and executive project leadership. Utility payment implementations were associated with Orlando Utilities Commission, Florida Power and Light, and the City of Austin, Texas.

Why it matters. It combined executive technology leadership with real financial-systems complexity, security, and utility-industry workflows.

Behavioral systems for a persistent world

The challenge. A large, persistent online world needs combat behavior that stays coherent and balanced as thousands of players interact.

Mark's work. Mark worked on combat artificial-intelligence and game mechanics associated with Star Wars Galaxies — behavioral logic, gameplay balance, and interactive systems within a large persistent world.

Why it matters. Keeping complex behavior coherent at scale is exactly the kind of systems thinking that separates working software from software that only demos well.

Consulting, custom software, databases, and web systems

Across more than a decade of independent engagements, Mark delivered custom software, database design, web systems, e-commerce, media processing, accessibility work, data synchronization, and operational improvement. A few representative projects:

E Job Agent. A desktop and web employment-search system using layered keyword logic with filtering by location, category, date, and relevance — helping job seekers cut through volume to relevant listings.

Big Poppa's. Business discovery, website redevelopment, and internal business systems, including a custom replacement for an existing point-of-sale system tailored to how the business actually operated.

Bayside Flooring. A backend ordering platform and website-creation system capable of producing Section 508 accessible websites through a visual editor — accessibility built in rather than bolted on.

Studio 39. A client-and-server media platform involving video streaming, channel mixing, encoding, conversion, media creation, and third-party integration, adapted to run under Windows.

Find Any Floor. A custom customer system with an online shopping cart supporting a retail flooring operation.

VARITRAK. A field-data synchronization system supporting laptop downloads, daily updates, central-database synchronization, CSV generation, and file transfer for distributed field work.

SCS. Interface programming, database design, network administration, and support for a tiered application environment.

NWAFT. Broad responsibility spanning programming, system administration, ISP operations, networking, hosting, email, DNS, user authentication, server migration, and telecommunications circuits.

Why it matters. The through-line is full-system ownership: understanding the business problem, building the solution, and keeping it running — not just writing code to a spec.

Diagnosis and recovery

The challenge. Mark entered a troubled internet service provider engagement in which the customer-facing client had become a liability to the operation.

Mark's work. He rewrote the customer-facing client to restore stability and usability, stabilizing a system the business depended on.

Why it matters. It is a clear example of technical diagnosis under pressure, decisive action, and protecting a business that could not afford continued failure.

Deep technical screening

The challenge. Hiring the wrong technical person is expensive, and interviews often reward rehearsed answers over real depth.

Mark's work. Mark conducted deep technical screening of candidates across a very broad range of technologies, evaluating genuine depth and fit.

Why it matters. It sharpened a skill clients still rely on: telling real expertise from performance, and matching people to the roles they can actually do.

Correction, integration, and validation

The challenge. Existing systems needed correction, integration, and reliable validation to perform as intended.

Mark's work. Mark handled software correction, database integration, hardware adaptation, systems analysis, testing, validation, and performance improvement.

Why it matters. It is the unglamorous, essential discipline of making existing systems actually work — measured, tested, and verified.

Product design and full system ownership

Alongside client engagements, Mark has built his own tools and products — evidence of continued technical curiosity, product thinking, and end-to-end ownership.

Data Form Wizard. A tool that connected to Microsoft SQL Server, selected database tables, and generated ASPX pages with code-behind files.

Resume Cloud. A dynamic HTML5 resume platform using object-based construction, drag-and-drop controls, templates, web fonts, visibility settings, and downloadable documents.

Pixelmon Servers List. A dynamic server-listing and public-voting platform that reached first-page search visibility for relevant search phrases.

UOLoot. A virtual-item marketplace built around a complex search system.

Game servers and launchers. Custom server integrations, Java extensions, launchers, patching systems, and community tooling.

Custom database applications. A range of data-driven applications built from the schema up.

Voice-driven personal AI assistant

Active Development

Problem. Consumer assistants depend on fixed commands, isolated apps, constant cloud, and a user who can reach a device — not enough for someone who lives alone in a rural area with mobility and vision limitations.

Architecture. A modular voice environment: local speech recognition and text-to-speech, wake-word interrupt, a deterministic local “guardian” safety spine, and cloud model routing (OpenAI, Claude, others) selected by availability, speed, cost, and task.

Mark's role. Owner, architect, and developer.

Impact. Extends independence and keeps help within reach without depending on physically reaching a phone or button — presented as engineering goals and prototypes, not a medical device.

Mobile robotic extension of the AI environment

Planned / Research

Problem. Even a capable voice assistant cannot see or move. A mobile unit could locate a person, respond to a spoken call, and establish contact without the user reaching a device.

Architecture. One or more mobile robotic units with cameras, microphones, speakers, distance sensors, LiDAR, local and remote processing, and charging/docking — feeding a secure status portal and emergency-communication workflows.

Mark's role. Owner, architect, and researcher.

Impact. A potential additional safety and communication layer — explicitly not a replacement for professional medical monitoring, and with no claim of guaranteed detection or automated emergency calling.

Supervised multi-agent software production

Active Development

Problem. AI agents left unsupervised wander, rewrite unrelated code, declare victory without testing, and silently change architecture.

Architecture. A controlled work-order queue (Inbox → In Progress → Review → Validating → Completed) with explicit requirements and validation, plus watcher services (ClaudeWatcher and companions) that track state, builds, tests, and risks for human review.

Mark's role. Owner, architect, and final approver — agents provide labor, review, and documentation.

Impact. Lets one experienced architect direct work that would normally need several specialists — without surrendering judgment, testing, or approval.