[1] interfaces
Interfaces that behave
React and TypeScript as the daily instrument. State that stays honest, components that survive real data, and screens that do not fall apart at the edges.
00—Porto, Portugal
Elizeu Carlos
role: Software Engineer @ Mastercard
I build the interface, the API behind it, and I want to know what happens underneath both.
Engineering, to me, is the whole stack: a React front end that behaves, the services and the data model it talks to, and the layer below that — the kernel, the filesystem, the network, containers and Kubernetes. I read operating-systems books the way other people read novels, because most of the interesting failures live one level deeper than where they appear.
Occasionally I take a system apart in public and explain it from the wire up.
react· typescript· node· sql· linux· containers· kubernetes
01 — Focus
On the front, and one layer deeper than the screen.
[2] systems
System design before code
Where the boundaries go, what owns the truth, what happens on the second request and the ten-thousandth. The design decides more than the language ever will.
[3] below-the-api
Reading one layer deeper
Linux and its filesystem, processes and memory; TCP, DNS and TLS; containers and Kubernetes orchestration. When something breaks, it usually broke down there first.
[4] back-end
Back end that holds
APIs, schemas and storage. Node on the service side, Rust where performance or the operating system matters, SQL as the thing everything eventually rests on.
03 — Contact
If it needs to work, we should talk.
Questions about the course, or work that needs someone comfortable on both sides of the API.