[ABOUT] Engineer · Londrina, BR · Since 2023

A full-stack engineer with an infra bias, a product instinct, and one eye on the math.

VG VITOR GABRIEL LONDRINA · BR
vitor · londrina · 2026

I build SaaS systems that keep their promises. My specialty is Laravel, but the real work happens across the stack — from the Postgres schema up to the React state tree, and the VPS that holds it all.

I started in 2023 as an intern at Clickweb, built my way up to full-stack pleno, and picked up a series of orbital skills along the way: CI/CD pipelines, Docker, Kubernetes, Nginx, Linux server hardening. If something has to survive a Friday deploy, I'm probably the one you want near it.

I also take product seriously. The best technical decisions I've made were the ones where I understood why the business needed the thing — and the worst were the ones where I optimised for code elegance over what the team actually needed to ship.

Lately I spend evenings reading about transformers: tokenisation, vocabularies, attention heads, Q/K/V. Not to jump on a trend — because the math is good, and because I want to earn the vocabulary.

"If you can't explain the decision to the person paying the bill, you probably haven't finished thinking about it."
[PRINCIPLES] How I work

Five notes I keep on my desk.

01
Boring wins in production.
The cleverest solution is the one the team can debug at 3am without me.
02
Make illegal states unrepresentable.
A schema that can't encode a broken state costs less than the test suite for catching one.
03
Observe, then optimise.
No performance work starts before the metric exists to measure it.
04
Ship the seam before the feature.
The interfaces compound. The features get rewritten. Design the interfaces first.
05
Own the whole stack, respect each layer.
Generalism isn't an excuse to be shallow — it's permission to go deep where the problem is.
[NOW] Currently

What I'm doing this quarter.

  • ● BUILDINGLaravel Fintech Core — ledger hardening + multi-tenant read models
  • ● SHIPPINGRisklog — v2 risk model, pulling authorship + file criticality
  • ● READINGTransformers from scratch — notes up on Journal
  • ● CONSIDERINGNew engagement, Q2 2026 — CLT, PJ or strategic freelance