2020
UFPB
I started Information Systems determined to do my best. I left in 2024 with academic honours — not because I aimed for the award, but because I never learned how to deliver half of something.
ABOUT
Who is Kawhan?
I write code for two reasons: to solve a problem, and to prove the idea was possible. That has been my job for four years now — desktop, back-end, front-end, and today systems that talk to real machines.
2021
42 São Paulo
A month of immersion with no teacher, no lectures and no ready answers. I learned C the hard way and found out I can find my way when nobody hands me the path.
2022
Two years as an intern
ISystems, on an agile team of up to 12 devs, across very different projects. On Calix, an AI product for demand planning, I worked both ends: front-end in Angular and TypeScript, back-end in Python. On LEAF, an Industry 4.0 automation project, desktop in C and C++ with Qt. I also wrote Go during this period. Front, back and desktop in two years.
2024
Public systems
At SES-PE, fullstack .NET on healthcare systems used by real people. I gathered requirements, refactored legacy code, onboarded new teammates, and learned that architecture decisions have consequences.
TODAY
Industrial automation
Stefanini Manufacturing, as a mid-level developer. APIs in .NET and ASP.NET for industrial automation, with event-driven architecture and communication over OPC and OPC UA. Process data goes into time-series databases — TimescaleDB and QuestDB. Unit tests and end-to-end tests with Playwright.
I enjoy writing code for two reasons, and they are really the same reason from different angles: solving a problem that actually exists, and proving an idea of mine could become something real. Until it runs, it is still a guess.
Right now that means building software for industry, with scalability and security considered from the start. But the technology is a detail — .NET today, Python yesterday, C at 42. The job underneath is always the same: solve the problem.
I started solving real problems back in university and never stopped. I went through desktop, back-end and front-end until I understood where I am strongest — the back-end, close to where technical decisions carry weight.
Badges
I love collections, and one of my current collections is badges on Credly.