Full Stack Developer at ZeltaDavid, Chiriquí — Panama

I build operations systems that have to add up.

TypeScript end to end — web, mobile, and the API behind both — on Cloudflare Workers and PostgreSQL. I work in production where a duplicated or lost record costs money, and everything on this page links to the code behind it.

Running right now

Experience

Where I work

Full Stack Developer

Jul 2026 — Present

ZeltaChiriquí, Panamá

The whole product, inside TypeScript monorepos: database schema, the API over it, and the web and mobile clients that consume it — with types and contracts shared across all three.

Backend work on systems with shared state, where operations have to stay correct when they arrive at the same time, when a client loses connectivity, and when they get retried.

Integrations with third-party business platforms, with scheduled data sync and automated alerting when a sync stalls or fails repeatedly.

Everything ships as a pull request: CI checks, peer review, and tests that pin the rule before it reaches production.

TypeScriptReactReact NativeNext.jsHonoNode.jsPythonPostgreSQLDrizzle ORMCloudflare WorkersTurborepo

zelta.dev

Projects

Selected projects

Four projects. For each one: the problem, the decision I had to make, and where it stands now.

Vigia

C#·.NET 10·ASP.NET Core·PostgreSQL·EF Core·Docker

Role
Solo — design, backend and deployment
Problem
I run several services on a single host and had no way to know whether they were up, or when that stopped being true. Prometheus with Grafana is two more services to operate, and its pull model assumes it can reach the machine — which is precisely what fails when the machine dies.
Decision
My own ingestion engine: push-first, sized for one operator. The domain never reads, never writes, never sleeps and never asks what time it is — the instant is always a parameter — and guard tests fail the build if any file touches the ambient clock. The hot path writes through binary COPY instead of EF Core, and retention drops whole partitions rather than deleting rows.
Outcome
The ingestion path runs continuously in production, collecting metrics from the host where the Discord bot on this page lives. The read API, the alert engine and the dashboard are not built yet: the README says exactly what exists and what does not.

Last commit: Aug 16, 2026

Touristik

Next.js 15·TypeScript·Cloudflare Workers·D1·R2

Role
Solo — full stack and deployment
Problem
My own idea: a tourism site where the tours and the photos could change without redeploying the whole thing every time.
Decision
I ran Next.js 15 on Cloudflare Workers rather than a Node server: D1 for relational data, R2 for images. Nothing to keep alive, and pages are served from the edge.
Outcome
Live, with a custom admin panel that does full CRUD over the tours. My largest codebase so far.

Last commit: Jul 14, 2026

React·TypeScript·Django REST·PostgreSQL·Vite

Role
Solo — Django API and React client
Problem
My own idea: an app for logging a planted tree where the map pin, the photo and the record go in as one step instead of three.
Decision
I split it in two: Django REST Framework owns the data and authentication, React handles the map and uploads. Mobile-first from the start.
Outcome
Deployed and running, with user accounts, image uploads, and a community feed.

Last commit: Jul 19, 2026

Discord bot

C#·.NET·Discord.NET

Role
Solo — rewrite
Problem
I had already built this bot in Node.js. Rebuilding it was the point: I wanted to learn a typed, compiled runtime properly rather than read about one.
Decision
C# with Discord.NET, so the compiler would catch what JavaScript let me get away with.
Outcome
Working bot, and my first serious contact with C#. Small on purpose.

Last commit: Aug 8, 2026

Evidence

The work in numbers

github.com/MikeSs26

Twelve months of commits, and what they were written in.

Contributions · last 12 months

394

311 in private repositories83 in public repositories

Solo repositories
5
Code written
1.1 MB
Last commit
Aug 17, 2026
Languages by bytes committed
LanguageShareBytes
TypeScript
49.8%
C#
29.6%
SCSS
9.4%
Python
9.4%
JavaScript
0.6%
CSS
0.5%

GitHub data as of Aug 24, 2026

Stack

What I build with

Split by how far I have actually taken each one.

Used in production

Tools I have written code with that runs in production today.

  • TypeScript
  • React
  • React Native
  • Expo
  • Next.js
  • Tailwind CSS
  • TanStack Query
  • Node.js
  • Hono
  • Express
  • Python
  • FastAPI
  • Django REST Framework
  • PostgreSQL
  • Neon
  • Drizzle ORM
  • Zod
  • Cloudflare Workers
  • Cloudflare D1
  • Cloudflare R2
  • Docker
  • Turborepo
  • Vitest

Worked with

Built real things with it.

  • C#
  • .NET
  • ASP.NET Core
  • Entity Framework Core
  • OR-Tools
  • OSRM

About

The short version

I am a full-stack developer at Zelta, in David, Chiriquí, Panamá. I started with Java, picked up C# because I liked it, moved to Python and Django because I wanted to understand the whole request instead of just the screen, and settled on TypeScript after getting tired of learning about my mistakes at runtime.

What I am good at: taking something from an empty repository to a URL a person can open. What I am still working on: testing discipline, and reading large unfamiliar codebases quickly.

Native Spanish. Technical English — I read and write it every day.

Contact

Let’s talk

Email is the fastest way to reach me. I reply to everything.