Gabriel AlmirPT

Hello, I’m Gabriel Almir.

I turn constraints into reliable paths.

I investigate limits, dependencies, and failures to turn technical decisions into systems other people can operate and evolve.

Explore systems and decisions↓Open dossiers ↗
Editorial portrait of Gabriel Almir
Between systems, ideas, and good questions.
scroll down

00 / brief

What you should know in 30 seconds

01−90%

I cut a critical system’s loading time

A measured result approved for disclosure.

02REGULATED

I work within real boundaries

I have experience with integrations and applications in regulated environments.

03OPEN

I collaborate on PhotoGIMP

I contributed to its evolution and now take part in organization and review.

02 / systems atlas

Systems, decisions, and consequences.

Architectural plates grounded in public code: context, forces, decisions, consequences, evidence, and known limits.

system / boundary / evidence

Architecture dossiers

Three systems examined in depth.

01

Architecture for legacy PHP

Maybe

implemented

Errors and absence become explicit states, adopted gradually at the edges of PHP 7.4 systems.

Decision

Result and Option make failure and absence part of the contract.

Versioned types and examples in the repository.

Open dossier →Public demo ↗

02

Architecture evolution

Pimbas

implemented

A tool for organizing friendly table-football matches and tournaments.

Decision

Consolidate Fastify and Next.js into one application.

The matches, rankings, and tournaments domain is publicly implemented.

Open dossier →

03

Product architecture

Saturno

implemented

A modern Laravel/Inertia monolith with a modular boundary for work management.

Decision

Laravel and Inertia keep delivery, domain, and operation close.

Laravel/Inertia code and modular organization.

Open dossier →Public demo ↗

Technical laboratories

Focused experiments with explicit boundaries.

L01

implemented

Hush

What must a RESP-compatible server make explicit about memory and concurrency?

No persistence, authentication, or clustering.

Inspect laboratory →

L02

experimental

MCP AnimagineXL

How can image generation be exposed through MCP and REST without hiding the GPU boundary?

A laboratory, not a product or production service.

Inspect laboratory →

L03

experimental

MCP Qwen3-TTS

Where are the boundaries between synthesis, batching, and voice cloning?

Caching and operations remain planned.

Inspect laboratory →

L04

implemented

Resulta

How can a total API and explicit errors stay ergonomic across ESM and CJS?

The library exposes errors; it does not choose application recovery policies.

Inspect laboratory →

01 / trajectory

The path explains the work too.

Career, education, and community did not happen on separate lines. Each stage added a new way to observe, decide, and build.

  1. DiolinuxTechnology and collaboration
  2. SenacInformation Technology technical program
  3. Independent workDevelopment and support
  4. FATEC ItapiraMultiplatform Software Development
  5. Laboratório CristáliaMid-level Systems Analyst and backend developer
Explore the complete trajectoryEducation, contests, documents, and public work

Career

  1. Technology and collaboration

    Diolinux

    The first professional chapter grew around Linux, communication, and community.

  2. Development and support

    Independent work

    Varied projects expanded autonomy, listening, and end-to-end responsibility.

  3. Mid-level Systems Analyst and backend developer

    Laboratório Cristália

    Applications and integrations in a regulated environment. I reduced one critical flow’s loading time by 90% — measured and approved for disclosure; technologies and systems remain confidential.

Education & community

  1. Information Technology technical program

    Senac

    Technical education that turned curiosity about computers into method and practice.

  2. Multiplatform Software Development

    FATEC Itapira

    A technology degree from São Paulo’s public state college system, completed in 2025.

  3. Competitor

    FATEC Itapira Minimaratona

    A local competitive-programming round: algorithmic problems, team strategy, and a ticking clock.

    Editorial illustration of a notebook with algorithmic problems
    FATEC Itapira Minimaratona · Mar 15, 2025AI-generated illustration

  4. Competitor

    InterFatecs

    A contest among FATEC colleges, where teams combine algorithms, task division, and decisions under pressure.

    Editorial illustration of a competitor at a programming contest
    InterFatecs · participation and venue · Aug 16, 2025AI-generated illustration

  5. Event document

    InterFatecs · venue

    The place that brought together teams from São Paulo state’s public technology colleges.

    Editorial illustration of a public college welcoming teams
    InterFatecs venue · Aug 16, 2025AI-generated illustration

  6. Competitor

    SBC Programming Marathon

    The Brazilian university competitive-programming event organized by the Brazilian Computer Society (SBC).

    Editorial illustration of a university programming marathon desk
    SBC Programming Marathon · Sep 13, 2025AI-generated illustration

↳ branch / public

In public

Open source · PhotoGIMP

Contribution, issue organization, and review in the community project.

Visit ↗
Editorial illustration of a photography and visual diary workspace

Instagram · @momentoalmir

Photography and a visual diary on Instagram, with process and fragments of everyday life.

Visit ↗
Editorial illustration of a small video creation studio

YouTube · Instagram · @avlye

Videos about technology, ideas, and learning, published on YouTube and Instagram.

Visit ↗

03 / behind the scenes

My process leaves marks.

I begin by asking and measuring. I draw states, note risks, and look for the smallest decision that moves the system forward. Then I return: test, document, and share what I learned.

  1. 01

    Observe

    I follow the whole flow before choosing a tool.

  2. 02

    Decide

    I make constraints and trade-offs visible.

  3. 03

    Verify

    I compare evidence and design recovery.

  4. 04

    Share

    I write so the work does not depend only on me.

Gabriel among visual process marks
Thinking is also a way of building.

04 / personal layer

Curiosity is a method too.

Open source, writing, design, and learning shape how I work. I like taking ideas apart, understanding their edges, and assembling something clearer in their place.

Coffee

An idea almost always begins with coffee.

Programming

Code is a means; clarity is part of delivery.

Anime

I enjoy stories built one frame at a time.

Games

I learn, save, and try again.

Linux

I prefer understanding the layers before abstracting them.

05 / writing

I write to think more precisely.

Performance · 4 min

How I cut a critical system’s loading time by 90%

An anonymized account of measuring before deciding.

↗Decisions · 4 min

How I choose backend technology without paralysis

Context, reversibility, and informed movement.

↗Work · 3 min

Software work is not all or nothing

The technical and human trade-offs between extremes.

↗Process · 3 min

I stopped chasing the perfect portfolio

Why evolution and authenticity represent me better.

↗

06 / contact

Shall we understand a problem together?

If you have a difficult system, a delicate integration, or simply want to exchange ideas about work and learning, write to me.

Send an email ↗