I build EdTech, structured-data workflows, and digital products for education teams that need clarity, traceability, and usable interfaces.
|
Knowledge systems Learning tools, institutional memory, archives, and research operations designed for long-term use. |
Auditable data workflows Public-data maps, reproducible methods, source review, evidence trails, and clear documentation. |
Product prototypes Interfaces and dashboards that turn complex education routines into usable digital products. |
|
Auditable mapping of Brazilian public universities with History programs and institutional contact evidence.
|
Dashboard-style interface for cataloging documents, people, reports, and historical records.
|
Public product brief for academic workflows, archive operations, and institutional memory.
|
How I approach projects
- Map the real workflow: people, data, documents, decisions, and constraints.
- Structure the evidence: sources, assumptions, edge cases, and reproducible methods.
- Build the interface: practical tools that make complex information searchable and usable.
- Document the system: READMEs, operating notes, and clear repository metadata.
What I care about in software
- Readable implementation before unnecessary abstraction.
- Interfaces designed for repeated use, not just first impressions.
- Data workflows that make uncertainty explicit instead of hiding it.
- Documentation that helps the next person understand what is true, current, and safe to change.
Current profile narrative
My public work sits between education, data strategy, and software engineering: public data maps, institutional systems, dashboards, and prototypes that help teams understand complex information and act on it.
Education workflows deserve the same rigor as production software.