Facundo Gartner
Software, interfaces & the in-betweenArgentina → Australia

A developer's mind.
A designer's eye.

I'm Facundo, a Computer Science graduate.
I care about how software works, how it feels,
and the details that bring it all together.

Explore my work
A few things I've been building

Selected work.

Beyond the interface

A little more
under the hood.

Sometimes the interesting part is what you don't see. A project exploring the foundations beneath our everyday tools.

Compiler design · Java
The person behind the pixels

A little about me.

Curious by nature.
Thoughtful by choice.

I recently graduated in Computer Science from Universidad Nacional del Sur in Bahía Blanca, Argentina. Now in Australia, I'm looking for my first opportunity to contribute, learn, and build alongside a team.

I'm especially drawn to design engineering: the meeting point of thoughtful interfaces and solid software. I like simple things done well, subtle interactions, and knowing why a detail matters.

Background
Computer Science · UNS
Currently
Australia
Drawn to
Design engineering
01 / Animation tooling

Pulse

A visual approach to animation.

  • React
  • TypeScript
  • Motion

Overview

Pulse brings visual animation authoring into React. A development editor makes it possible to work with timelines and keyframes, while a separate runtime plays the resulting animations in production.

My contribution

My work connects the editing experience to the engineering underneath it: timeline controls, element selection, reusable component animations, and the boundary between the editor and production playback.

A few decisions along the way

01

Author visually. Ship a runtime.

The development editor and production playback have different jobs. Keeping them separate avoids shipping the editing interface with the finished experience.

02

Animations that belong to components.

Scoped targets and animation sidecars let a component carry its animation with it, rather than depending on one global page timeline.

03

Make control feel direct.

The editor connects element selection, timeline navigation, and playback so that authoring feels like working with the interface itself.

A project I am continuing to shape and refine.

02 / Business software

Pilar

A foundation for everyday business.

  • Next.js
  • TypeScript
  • PostgreSQL
  • Drizzle

Overview

Pilar brings sales, inventory, suppliers, invoicing, and cash operations together for small businesses. The aim is to make everyday work easier to follow, with information that stays connected across the business.

My contribution

I work across the product interface and its business logic, connecting sales and inventory workflows with the data model, access boundaries, and supporting operations.

A few decisions along the way

01

Keep the operation connected.

A sale and its inventory changes belong to the same operation. Transactional updates keep the product record and the business workflow in step.

02

Clarity over clutter.

A restrained visual language gives products, sales, and business information room to breathe without making the interface feel disconnected.

03

Build around real boundaries.

Branches, team access, and fiscal workflows introduce constraints beyond the screen. The product needs to account for those rules, not just present a dashboard.

A project I am continuing to shape and refine.

03 / Language engineering

MiniJava Compiler

From source code to something executable.

  • Java
  • JUnit
  • Compiler design

Overview

A compiler implemented in Java for a MiniJava language. It takes source through lexical, syntactic, and semantic analysis before generating assembly for the CEI virtual machine.

My contribution

This project explores what happens underneath the languages we use: recognizing tokens, checking structure and meaning, and translating a program into instructions a machine can execute.

A few decisions along the way

01

One pipeline. Distinct responsibilities.

Source handling, lexing, parsing, semantic checking, and code generation are separate stages, each responsible for a different kind of correctness.

02

Make errors meaningful.

Lexical, syntax, and semantic diagnostics identify the offending token and source line, making failures easier to trace back to the program.

03

Follow the program to execution.

The generated stack-machine assembly can run on the CEI VM. Test cases connect source programs to their expected output.

View source

A study in the foundations of software.

A closer look