Santiago rincorpes

Hi, I'm Santiago Rincón 👋

👋 About me

I'm a software engineer who likes building platforms, tools, frameworks, and abstractions that make complicated systems easier to work with.

Most of my public work lives somewhere between:

developer tooling
Python libraries
AI and agent systems
APIs and real-time infrastructure
creative technology
games and simulation
software architecture

I tend to gravitate toward problems where there are too many moving parts, too much repetition, or too much hidden complexity.

Then I try to turn that mess into something reusable.

I build the systems behind other systems.

⚙️ What I like building

🧰 Developer Tools

CLIs, SDKs, shared libraries, registries, logging systems, automation, and infrastructure that makes building other software easier.

🧠 AI Systems

Agents, structured knowledge, tool integration, evaluation, real-time state, and experiments around software that can reason and act.

🎮 Creative Systems

Game frameworks, DCC tooling, pipelines, rendering abstractions, and software for creative or highly interactive environments.

🌌 Featured experiment

Endr

An AI-native Minecraft project used to explore agents, structured knowledge, real-time environments, and autonomous software.

Minecraft
    │
    ▼
Runtime ──────── Agents
    │               │
    ▼               ▼
Clients         Knowledge Platform
                    │
          ┌─────────┼─────────┐
          ▼         ▼         ▼
         API       SDKs      ETL

Endr is where I'm currently exploring questions like:

How should agents interact with changing environments?
What knowledge belongs in structured APIs instead of prompts?
How do you separate reasoning, runtime state, tools, and domain knowledge?
What does good developer experience look like for agent systems?
How do you make autonomous software observable and debuggable?

Current pieces include:

FastAPI knowledge services
WebSocket runtime
Minecraft state integration
AI agents and tools
version-aware structured knowledge
ETL pipelines
Python and JavaScript clients

Endr is currently private R&D, but I use it as a sandbox for ideas that often become reusable patterns elsewhere.

🧪 Open source

Project	What I'm exploring
Sable	Modular game and systems architecture, runtime services, rendering backends, CLI tooling, and reusable Python patterns.
Onomasticon	Typed implementation registries for plugin architectures and interchangeable components.
Relict	Reusable logging infrastructure for Python applications, packages, and command-line tools.
Limen	Small Python framework for building structured command line applications.
ParadoxJS	Lightweight JavaScript abstractions for interactive interfaces without a large frontend framework.

🔬 Current interests

🧰 Core Stack

currently_exploring = {
    "developer_platforms": [
        "reusable tooling",
        "plugin architectures",
        "automation",
        "observability",
    ],
    "ai_systems": [
        "agents",
        "knowledge APIs",
        "evaluation",
        "tool orchestration",
        "real-time environments",
    ],
    "creative_tech": [
        "game frameworks",
        "DCC integrations",
        "rendering systems",
        "production workflows",
    ],
}

I'm especially interested in the space where these overlap.

Things like:

AI + developer tooling AI + games AI + creative software platform engineering + developer experience framework design + real production constraints

🧰 Tools I reach for

Usually somewhere in the mix:

Python • FastAPI • JavaScript • TypeScript • Node.js • WebSockets • Docker • GitHub Actions • PostgreSQL • MySQL • MongoDB

And depending on the problem:

Google ADK • OpenAI APIs • Qt / PySide • C++ • SDL2 • Maya • Houdini • Blender • Unreal Engine • DaVinci Resolve

I care more about the system than the stack, though.

🧭 Engineering principles

Build for reuse.

Prefer clear boundaries over clever abstractions.

Make important systems observable.

Automate recurring friction.

Treat developer experience as product design.

Keep simple things simple.

Ship, learn, refactor.

🛠 How I tend to work

def build_system(problem):
    understand_the_domain(problem)
    find_the_repeated_friction(problem)
    design_clear_boundaries()
    make_it_observable()
    automate_the_boring_parts()
    ship()
    learn()
    simplify()

✍️ Writing & building in public

Things I like writing or thinking about:

Python architecture
developer platforms
API and SDK design
AI infrastructure
agent systems
knowledge systems
observability
game architecture
creative technology
building reusable software

LinkedIn · Portfolio · DEV

Curiosity · Systems · Tools · Software that helps build software

Navigation Menu