Portrait · Henrique A. Lavezzo

An engineer who leads, and a leader who still builds.

I'm an engineering leader born and living in Brazil, working across software architecture, developer tools, and AI-assisted engineering. I turn ambiguous problems into systems people can understand, change, and trust.

Code Alchemist is the playful name. The practical work is architecture, technical direction, team clarity, and careful experimentation.

Class
Code Alchemist
Discipline
Systems Cartography
Henrique A. Lavezzo
Henrique A. Lavezzo · Brazil

Operating principles

How I work

  1. Make the system legible

    Map constraints, boundaries, and decisions until the next useful move is clear.

  2. Stay close to the material

    Keep leadership in contact with code, tools, incidents, and friction.

  3. Design for change

    Leave room to evolve without making every decision expensive.

  4. Keep judgment human

    AI extends attention and reduces repetition; evidence, responsibility, and final decisions remain with people.

A craft in motion

Four transformations

Chapter 01

Origins · curiosity before credentials

Apprentice

Learning the language of machines

Delphi opened the first door. Final Fantasy VII quietly taught me English, and games taught me that every complicated world can become legible through rules, feedback, and a little wonder.

Curiosity · games · first programs

Chapter 02

Craft · code as a material

Artificer

Making boundaries you can hold

Ruby became my favorite workbench. I learned architecture by untangling real businesses, then made small, dependency-light tools such as Fluxus so the useful patterns could travel.

Ruby · architecture · open source

Chapter 03

Leadership · systems made of people

Guildmaster

Helping teams stay in motion

Engineering leadership expanded the system boundary. Clarity, trust, and healthy constraints matter as much as good interfaces; the work is creating conditions where people can make good decisions together.

Teams · strategy · sociotechnical systems

Chapter 04

Now · intelligence as a collaborator

Technomancer

Conducting a party of familiars

I am exploring AI-assisted engineering as orchestration, not spectacle: routing the right model to the right problem, keeping judgment human, and publishing what survives contact with real work.

AI agents · model routing · experiments

Quest chronicle

The work, in sequence

  1. Director of Engineering

    ElectionBuddy Inc.

    From to PresentActive quest

  2. Lead Developer

    ElectionBuddy Inc.

    From to

  3. Software Engineer

    ElectionBuddy Inc.

    From to

  4. CTO

    Adimplere

    From to

  5. Software Engineer

    Adimplere

    From to

  6. Software Engineer

    Varitus

    From to

  7. Software Engineer

    devCoffee Business Solutions

    From to

  8. Freelance software work and Computer Science degree

    Independent

    Freelancing while completing a university degree in Computer Science.

    2014 — mid-2015

  9. Software Engineer

    Koya Design

    From to

  10. Robotics Specialist Intern

    SESI

    From to

  11. Software Engineer

    Compsoft

    From to

  12. Support Analyst

    Microleme Sistemas

    From to

  13. Software Engineer

    ViaConnect - TCCOM

    From to

Personal facts reviewed .

Workbench inventory

What I keep near the workbench

Proficiency

Programming Languages

  • Ruby
  • Rust
  • JavaScript
  • Clojure

Proficiency

Architecture & Design

  • Clean Architecture
  • Domain-Driven Design
  • Monolithic Architecture
  • Agentic Orchestration

Open correspondence

Compare notes?

If you are untangling a difficult system, shaping an engineering team, or experimenting with AI without surrendering judgment, write to me.