Lemes Workspublic engineering archive
LW / HOME / 2026locale: en

Full-stack developerA portfolio of engineering,
architecture
and software.

I am Matheus Lemes, a full-stack developer focused on Java/Spring, Next.js, architecture and databases. Projects, articles and notes are recorded here as technical evidence.

Architecture Atlasareas of focus
  • ClientNext.js / React / i18n01
  • ContentMDX / Velite / Shiki02
  • EngineeringJava / Spring / Arquitetura03
  • DataPostgreSQL / SQL / NoSQL04
  • DeliveryAWS / DevOps / Observabilidade05
evidence: architecturesource: mdx
LW / CONCEPT

Engineering as structured craft.

What gets recorded here is the process: decisions, trade-offs, diagrams, code and lessons — not just the final result.

01
Foundation
Architecture, data and method before tooling.
02
Practice
Code published, read and reviewed in the open.
03
Record
Decisions versioned in MDX, with diagram and context.
LW / PROJECTS

Cases from problem to deploy

All projects
LW / PROJECT / DEMOdemonstration structure

How a case will be presented

Every project opens with the problem, shows the architecture decision that solved it and ends at what shipped to production. No case has been published yet.

problem
the context and the constraint that started the work
decision
the path chosen and the cost accepted
stack
Java · Spring · PostgreSQL · AWS

Module diagram — structural composition, not a real project.

  • LW / PROJECT / 002Second case — in preparationstatus: draft
  • LW / PROJECT / 003Third case — in preparationstatus: draft
  • The code behind the studies is already public while the cases are being written.See repositories on GitHub
LW / AREAS

Knowledge matrix

Five families, fifteen areas. Each one filters articles, notes and projects by the same slug used in the content.

LW / ARCHIVE

Technical editorial archive

Archive prepared, first edition under construction.

  • LW / ARTICLEStructure of a published articleTitle, summary, area, reading time and contents — the skeleton every MDX will fill in.
  • LW / NOTEShort study noteDirect records: a problem, a decision, a snippet of code.
$ pnpm velite
schema validated · 0 documents
articles/ notes/ projects/ empty
LW / METHOD

How I document a decision

  1. 01

    Problem

    The context, the constraint and what must be true in the end.

    evidence: issue
  2. 02

    Trade-offs

    Alternatives considered and the cost of each path.

    evidence: note
  3. 03

    Implementation

    Code, diagrams and what changed in the architecture.

    evidence: commit
  4. 04

    Deploy and review

    What worked, what broke and the lesson recorded.

    evidence: article
Matheus Lemes - Desenvolvedor de Software | Lemes Engineering