JC Jayden Ontalan Capistrano Software developer / systems desk

Backend-leaning software developer building deployed tools, practical interfaces, and documented systems.

Current work centres on deployed full-stack apps, spreadsheet-native tools, and maintainable self-hosted systems.

View work Resume Contact
Featured
3 featured builds
Index
6 total projects
Hosted
self-hosted apps
Case studies
in progress

Selected work

Current tools and systems that show product flows, data modelling, validation, and long-running project structure.

All projects

Continuity system

Memory
Arbitration
Context

SpineFrame

Project 01

SpineFrame

live

A live production personal reflection and memory system with authenticated chat, user-scoped memory, Postgres-backed storage, and continuity review flows.

Build notes

  • Built authenticated chat, history, memory review, and account flows around a user-scoped runtime.
  • Moved the public-user path from JSON files into Postgres-backed auth, conversations, sessions, and memory stores.
  • Validated Alice/Bob isolation, memory integrity, and storage migration parity.

System focus

  • User-scoped runtime
  • Memory review
  • Storage migration

Role

Product + full-stack

Stage

Active build

Focus

User-scoped runtime

PythonFlaskPostgresAuthMemory systems

Updated Jun 2026

Case study

full-stack

VocabVerse

live

A Japanese study app that turns song lyrics into saved study items, flashcards, quizzes, and review history.

Build signal

A deployed learning app built around songs as a reason to keep returning to language study.

Next.jsReactTypeScriptPrisma

Updated Jun 2026

Visit VocabVerse Case study

data

Mage's Survival Calculator

live

A spreadsheet-native build-planning tool for Mage's Survival mages, spells, passive levels, items, custom stat increases, and stat outcomes.

Build signal

A formula-heavy Google Sheets calculator for planning Mage's Survival builds, spells, items, passives, and stat outcomes.

Google SheetsXLSXFormulasNamed ranges

Updated Jun 2026

Case study

How I work

The system work should be visible in the process, not just the interface.

  1. 01

    Understand the problem

    Map the user need, constraints, edge cases, and failure points before shaping the UI.

  2. 02

    Design the system

    Break the solution into flows, data, interfaces, and deployment boundaries.

  3. 03

    Build and refine

    Implement, test, simplify, and document the result until the workflow is clear.

Current focus

A few active threads from the Now log.

  • Polishing project pages around SpineFrame, VocabVerse, hangout-planner, and Mage's Survival Calculator.
  • Rewriting case studies around implemented flows, data models, and validation work.
  • Replacing placeholder project media with current screenshots and diagrams.

Projects, resume, or contact.

The primary recruiter path stays short: inspect the work, check the resume, then reach out directly.

Resume Contact