Thomas Cayne

Thomas Cayne · Hands-on product engineering

Principal Software Engineer

Principal-level engineering judgment built across 36+ years, with current hands-on delivery spanning architecture, implementation, deployment, professional AI model training, and agentic code evaluation.

AI model training & code evaluation

I define repository-grounded requirements, constraints, acceptance criteria, and evaluation rubrics, then assess agent-generated implementations for correctness, instruction adherence, technical reasoning, security, accessibility, testing, and maintainability. I reproduce failures and direct corrective iterations until the implementation and evidence agree with the intended behavior.

Core Stack: TypeScript | React | Angular | Next.js | PostgreSQL | Node.js

Review engineering evidenceView selected workInspect public source
GitHubStack Overflow

Engineering across eras

From xBase systems to modern product architecture

A working history that runs from xBase data systems and enterprise .NET applications to framework libraries, cloud delivery, and AI-enabled TypeScript platforms.

Primary today

Used across current products, libraries, and deployment work.

  • TypeScript
  • JavaScript
  • Python
  • Angular
  • React
  • Next.js
  • SvelteKit
  • Node.js
  • PostgreSQL
  • Docker
  • GitHub Actions

Extensive production experience

Applied across enterprise applications, APIs, data, and cloud delivery.

  • C#
  • .NET
  • RxJS
  • Express
  • SQL Server
  • MySQL
  • Microsoft Azure
  • AWS
  • Azure DevOps
  • GitLab

Currently refreshing

Languages under deliberate review through current implementation practice.

  • C
  • C++

Historical foundation

Earlier data and application systems that established the engineering foundation.

  • Visual FoxPro
  • Clipper
  • dBASE
  • ColdFusion

These groups highlight representative technologies by recency and depth; the three-row engineering history below carries the broader working stack and is not an exhaustive inventory.

  • TypeScript
  • C
  • HTML5
  • Clipper
  • React
  • RxJS
  • Sass
  • .NET
  • Electron
  • ColdFusion
  • MySQL
  • TypeORM
  • Microsoft Azure
  • Azure DevOps
  • Vitest
  • WebdriverIO
  • JavaScript
  • C++
  • CSS
  • dBASE
  • Next.js
  • NgRx
  • Figma
  • NestJS
  • GraphQL
  • PostgreSQL
  • Drizzle ORM
  • Sequelize
  • AWS
  • GitLab
  • Jest
  • C#
  • Python
  • Visual FoxPro
  • Angular
  • SvelteKit
  • Tailwind CSS
  • Node.js
  • Express
  • FastAPI
  • SQL Server
  • Prisma
  • Docker
  • GitHub Actions
  • Playwright
  • Cypress

Selected Work

A founder-led product, a published open-source ecosystem, a live source-available college system, and active private-product engineering.

Gravity English platform landing page introducing its English fluency infrastructure

Founder · Product architecture, implementation, testing, and delivery · Active proprietary product

Gravity English

A live, multi-tenant English-learning product with server-defined courses, queued curriculum generation, and white-label delivery.

  • I replaced the legacy Angular/AnalogJS application with SvelteKit 5 because the active product needed server-driven behavior without the former SSR and build constraints
  • I kept curriculum in typed server-defined content so course structure can change independently from page deployments while the application still validates tenancy and rendering
  • I retained relational authority in PostgreSQL and Drizzle while placing larger blueprint and media payloads in S3, with a database fallback when object storage is unavailable
  • I separated long-running curriculum generation into Gravity Swarm Architect and accepted queue latency and additional operational complexity to keep AI work outside learner requests
Read project case studyView architecture diagram & data flow

Technology

  • SvelteKit
  • Svelte 5
  • TypeScript
  • Node.js
  • PostgreSQL
  • Drizzle ORM
  • Clerk
  • AWS S3

Open-source architecture

View Slashand on GitHub

SDUI Blade

SDUI Blade is a public TypeScript architecture with a framework-independent core and native Angular, React, and Svelte adapters.

Explore the architectureOne typed protocol · Three framework-native adapters
JRKC Bookstore catalog showing filters, ratings, pricing, and paginated book inventory

College project · Sole architecture and implementation · Live deployment · Public source

JRKC Bookstore

An end-to-end bookstore system I selected from professor-provided options and delivered during a five-week Colorado Technical University course.

  • I replaced the unavailable paid hosted backend with application-owned authentication and typed Drizzle routes so identity and PostgreSQL access remain under the application's control
  • I isolated the bookstore in its own Docker Compose project, private database network, named volume, and explicit Oracle port so it cannot collide with other workloads
  • I placed Caddy at the public boundary and health-gated deployment restarts so releases touch only the bookstore Compose project
  • I rejected live Stripe credentials in deployment, preserving the completed checkout integration without accepting real payments from portfolio visitors
Read project case study

Technology

  • Next.js
  • React
  • TypeScript
  • PostgreSQL
  • Drizzle ORM
  • Docker
  • Stripe
Coverlay Studio landing page presenting its AI-assisted video creation suite

Founder · Product architecture and active implementation · Private product in development

Coverlay Studio

An actively developed browser-based editor for reversible timeline operations, media composition, overlays, and AI-assisted production workflows.

  • I centralized editing state in one typed model, accepting greater store complexity to keep timeline, canvas, properties, assets, and assembly behavior consistent
  • I modeled linked and compound clip relationships as explicit data so editing operations update related media deliberately instead of relying on visual conventions
  • I separated the browser studio from an Express persistence boundary so interface behavior and application-owned storage can evolve independently while Clerk identity is mirrored into local records
Read project case studyView architecture diagram & data flow

Technology

  • React
  • Next.js
  • TypeScript
  • Zustand
  • Zundo
  • Express
  • PostgreSQL
  • Drizzle ORM
  • Clerk

Documented delivery

Engineering evidence beyond job titles.

Selected outcomes from enterprise modernization, product delivery, testing, and independently owned software lifecycles.

enterprise applications developed, modernized, and supported at AT&T
11
automated tests repaired, refactored, or replaced at LCPtracker
2,000+
customers across 115 countries served by the Park Place portal
13,000+
reduction in estimation time from an independently delivered workflow
83%

Start a focused conversation.

Share the role, engineering problem, or product context you want to discuss through a private, spam-protected contact path.

Use secure contact formReview complete resume