Full-Stack Developer | TypeScript · React · Next.js · Node.js
Full-stack developer working in TypeScript/React/Next.js on the front end and Node.js (Fastify, Clean Architecture, SOLID) on the back. At StarSeg I unify system architecture and integrate ESP32 hardware over MQTT and WebSockets. On my own time I build and maintain Git Assets, a micro-SaaS, and write about SOLID and the engineering practices behind maintainable code.
Atibaia, São Paulo — Brazil
Author and maintainer
Micro-SaaS that turns GitHub profiles into dynamic SVG assets. I rebuilt it as a pnpm/Turborepo monorepo with strictly scoped packages — database, core, api and web — so Next.js Server Actions call the business logic directly, without an HTTP hop in the middle.
Taken from a v1 hypothesis test to a modular v2 architecture
Creator and developer
A gamified bottle-cap collector — scored like an arcade basketball hoop — built to make recycling worth doing in schools. ESP32/Arduino count the caps in real time and stream to a web dashboard. It was my capstone project and the basis of my undergraduate research.
Top capstone grade; field survey of 135 people, 98.5% would recycle through the gamified flow
Full-stack developer
Full-stack app for setting and tracking weekly goals, built during Rocketseat's Next Level Week (intermediate JavaScript full-stack track).
Full-stack developer
SaaS education platform in a Next.js/NestJS monorepo. Heavy media is processed off the request path through Redis-backed BullMQ queues, transcription runs on Whisper AI, and IndexedDB keeps the app usable when the connection drops.
Full-stack developer
Platform for Python coding challenges. Submissions are graded automatically by an isolated PHP validator, with an admin panel for managing challenges and test cases.
Developer
Retrieval-Augmented Generation app for legal documents, built in a GDG workshop on Google Cloud: Cloud Storage plus Firestore as the vector database, Cloud Run triggered by Eventarc, and Vertex AI with LangChain orchestrating the LLM.
Makes the case for dropping auto-deploy-on-merge in favour of a real release pipeline on GitHub Actions, where only annotated SemVer tags ship — through six validation stages, including tests, migrations verified against a disposable database, and smoke tests.
Business modules should not depend on concrete external tools, but on abstractions you own — so an implementation can be swapped without touching the core logic.
Interfaces should be small and specific instead of forcing classes to implement methods they never use. Splitting a fat interface into well-defined contracts leaves the code modular and loosely coupled.
A parent class must be replaceable by any of its children without breaking the application — no subclass that throws on inherited behaviour or quietly drops it. Getting that right is a hierarchy design problem, not a coding one.
Code should be open for extension and closed for modification. Polymorphism and abstraction replace growing if-else and switch chains, so new behaviour gets added without editing what already works.
Each class should have exactly one reason to change. Shows how God Classes accumulate responsibilities and how to split them into specialised classes that fit architectures like Clean Architecture.
The five SOLID principles as practical guidelines for quality, scalability and maintainability, with TypeScript examples contrasting the anti-pattern and the fix for each one.