Skip to content
View anstosa's full-sized avatar
🥔
🥔

Block or report anstosa

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
anstosa/README.md

Ansel Santosa

Product-focused software engineer · Full-stack architecture, applied AI, and developer tooling

I design and build products end to end, from interfaces that make complex decisions understandable to the infrastructure, data pipelines, and reliability mechanisms behind them. My work spans React, TypeScript, Python, applied machine learning, and production systems engineering. I care most about clear product experiences, evidence-backed technical decisions, and software that behaves responsibly when the real world gets messy.

I'm currently building at Potato. Previously: Carbon Robotics, Pioneer Square Labs, and ExtraHop.

Engineering decisions & impact

Shipping ML without adding a model-serving platform

For my weather platform, I separated Python-based model development from deterministic TypeScript inference rather than introducing a dedicated model server. Exported model artifacts keep training dependencies out of the request path, while validation and raw-forecast fallback prevent a correction model from becoming an availability dependency.

The recorded temperature evaluation showed 19.54% lower mean absolute error across 25,968 events. That result comes from a frozen-forward replay using development data, not an independent prospective production trial.

Architecture, evaluation, and limitations → (https://github.com/anstosa/weather#4-applied-machine-learning)

Extending existing workflows instead of replacing them

For Remote Agent Console, I built around existing coding-agent CLIs and tmux rather than creating another execution runtime. I separated agent, worktree, and conversation identities, while centralizing terminal effects and target validation behind a shared runtime boundary.

This preserves established CLI workflows while giving integrations a common place to enforce delivery, authorization, and recovery behavior. The architecture deliberately targets one trusted operator rather than introducing distributed infrastructure or implying multi-tenant guarantees.

Design constraints and architectural decisions → (https://github.com/anstosa/remoteagents#1-problem-statement-and-design-constraints)

Selected engineering work

image

A ferry-planning platform combining real-time transportation data, capacity forecasting, and computer vision. It explores how to make useful recommendations without confusing predictions with verified facts.

Engineering focus: Full-stack product architecture, React/TypeScript, PostgreSQL, forecasting, computer vision, AWS, and failure-aware UX.

image

A self-hosted control plane for supervising terminal-native AI coding agents across live sessions, Git worktrees, prompt queues, and reviews.

Engineering focus: Developer experience, React/TypeScript, AI orchestration, durable coordination, security boundaries, and human-in-the-loop workflows.

image

A hyperlocal weather intelligence platform joining sensor measurements, regional forecasts, and controlled ML-based forecast correction into web and Android experiences.

Engineering focus: Data provenance, causal evaluation, Python-to-TypeScript model delivery, PostgreSQL, native Android, and production release engineering.

image

An earlier open-source browser extension project making custom styling and scripting more approachable. An example of my longstanding interest in user agency and product interface customization.

What I like working on

  • Product engineering: Complex capabilities presented through simple, well-considered interfaces.
  • Engineering architecture: Typed boundaries, observable behavior, graceful failure, and production reliability.
  • Applied intelligence: Practical forecasting, machine learning, and AI systems that make uncertainty and human control explicit.
  • Developer tools: Workflows that reduce friction without hiding critical system state.

LinkedIn · Personal website

Pinned Loading

  1. ferry.fyi ferry.fyi Public

    Production ferry planning platform combining real-time data, capacity forecasting, computer vision, and full-stack product engineering

    TypeScript 13 3

  2. remote-agents-console remote-agents-console Public

    Self-hosted AI coding-agent control plane with live sessions, Git worktrees, prompt orchestration, and guided code review

    TypeScript 1

  3. Ballydidean-Weather Ballydidean-Weather Public

    Hyperlocal weather intelligence platform with sensor ingestion, ML forecast corrections, and production web/Android clients

    JavaScript

  4. Minimalist-Everything Minimalist-Everything Public archive

    A chrome extension that makes HTML, CSS, & JavaScript injection easy for beginners and experts.

    JavaScript 103 31