Skip to content
yangetze
ESLet's talk
Systems Engineer & Software Developer

Designing the digital engines businesses run on.

I'm Yangetze. I model the minimum system that solves 80% of a problem with 20% of the effort. Not every problem needs code — sometimes the right fix is a process.

See projects Get in touch
$ status --site
✓ architecture defined
✓ domain connected
◐ case studies — in progress
10 years
building software
2 formal jobs
long tenures, nothing left unfinished
2 stacks
.NET and JavaScript, in parallel
Remote
from Venezuela, for Chile

Professional Experience

Almost seven years at one, four and counting at the current one — long enough to live with the consequences of every decision. No screenshots here: these are internal systems under confidentiality. What I can show is how the decisions were made.

4 years and counting

ProGarantía

ProGarantía (holding, Chile — remote)
Financial guaranteesInsurance brokerageCampaign managementC# / .NETSQL Server
Almost 7 years

Galac CRM

Galac Software

A CRM integrated with Galac's administrative system. Modules: quoting, client management, sales follow-up.

Projects

Built end to end, and I can show all of it.

See all work
somosedificadigital.com

Edifica Digital

Own project · with Isaac Delgado

A multi-tenant, bilingual (ES/EN) SaaS platform for donation traceability at nonprofits and churches. Covers the full cycle — receive, transform, document impact — with verifiable audit trails.

React 19 + Vite 8Tailwind CSS 4Supabase
creahabita.com

CreaHabitat

Own project · with Ricardo Yánez

Full case study — coming soon.

ibe.org.ve

Iglesia Bautista Emanuel (ibe.org.ve)

Client · Since 2024

An institutional site migrated from Webflow to a custom Next.js build. It solves getting a first-time visitor to know when and where to go with no friction, and lets them contact the church without a phone call.

Currently buildingBocadoApp

The 80/20, applied on purpose.

A tournament manager I ran with a printed Excel sheet — not an app — is the clearest proof of that last point. Tournament Manager →

  1. 01

    Model the problem

    Before any code: what's the actual shape of this problem, and what's the minimum that solves 80% of it?

  2. 02

    Build the minimum

    Ship the smallest system that's correct and honest about its data — not the biggest one that's impressive.

  3. 03

    Know when not to code

    Sometimes the right answer is a process change, not a system. A well-designed spreadsheet beats an app nobody asked for.

Two stacks, in parallel.

Not one as the future of the other. Levels are transcribed honestly, not inflated.

Microsoft

10 years of formal experience
  • C# / .NETcore
  • SQL Servercore
  • Blazorcore

JavaScript

Real production, six projects
  • React / Next.jsworking
  • TypeScriptworking
  • Tailwind CSSworking
  • Postgres (Supabase)working
  • Node.js / Expressexploring

coreworkingexploring

Have a process that should be a system?

Tell me about it. I'll answer with what I'd build — and what I wouldn't.

Write to me hello@yangetze.dev