Samuel Caetité // Senior Software Engineer
I turn complex context into sustainable software, connecting product, architecture, and people to deliver without losing the ability to evolve.
KPIs that actually matter
1 principle I won't compromise on
Technology in service of people.
Before the code
People feel the problem. Product translates an intention. Business creates consequences. Systems carry dependencies, constraints, and previous decisions. Understanding is not waiting to know everything. It is knowing enough to decide consciously.
Product × Engineering Sometimes both sides had a point. First, the torches had to come down.
Case 01 · Saveadd
The product already used React. Even so, class components, concentrated responsibilities, and an interface that was hard to evolve showed that adopting current technology does not complete modernization.
Transformation happened progressively: understanding existing behavior, reorganizing components, adopting Hooks where they made sense, and preserving what still worked well.
Modernization is not replacing the stack. It is restoring the system's ability to evolve.
1.457 km · 26h Laptop on my lap, the open road, and curiosity. That's how Meteor.js entered my toolkit.
Case 02 · E-commerce
Campaigns and experiences often arrived with intentions that seemed incompatible with the platform, timeline, or stability. Constraints were not ignored, but they did not become an automatic veto either.
Intent comes first. Then constraints, alternatives, cost, and risk. Technically possible does not necessarily mean viable, responsible, or desirable. Sometimes the final recommendation is still no.
Creativity is engineering, too.
1 year of experience The expectation was already senior. My experience had to catch up.
Case 03 · VCASOFT · Vivo / Telefónica
An active operation distributed across South America and Europe brought together users, dependencies, and technologies from different generations. Stopping everything and starting over was not an option.
Modernizing meant understanding critical flows, building bridges, and replacing parts progressively while operations continued.
Contextual constraint operational continuity
Sometimes contributing to the team meant writing code. Sometimes it meant translating the meeting.
Independent products
Independent projects with their own context, open source code, and, where available, a product page to explore before entering the repository.
A desktop command center for knowing what is happening in the Git repositories already on your machine.
Current branch, local changes, upstream, and project reference appear as separate, readable facts.
It observes and refreshes when you ask. It does not commit, checkout, merge, pull, or push on its own.
v0.1.0 public · Linux · .deb · AppImage
Open the same website in isolated sessions, preserving each identity's accounts, cookies, and context in native Firefox Containers.
Compose, template, send, and track replies through Gmail while keeping messages, attachments, and credentials under local control.
A local dashboard that monitors career pages, identifies new opportunities, and preserves history.
A desktop app for managing Git identities and GitHub accounts without manually editing configuration, with tokens protected by the system keychain.
Workout tracking with gamification that values real effort. An experience built to encourage consistency without turning difficult days into failure.
A modular build system for static landing pages, with compilation, image optimization, cache busting, and SEO automation from the first delivery.
The pattern
Context before the answer
People feel the problem. Product translates an intention. Business creates consequences.
Decision before delivery
Technically possible does not necessarily mean viable, responsible, or desirable.
Capability after delivery
An intervention can leave behind tools, knowledge, autonomy, and better conditions for the next decision.
A new way of working
Research, implementation, review, and testing no longer depend on a strictly linear sequence. Agents expand what can be done; context, judgment, safety, and technical decisions remain human responsibilities.
01Context and hypothesishuman responsibility
02Research · implementation · review · testsamplified execution
03Judgment and decisionhuman responsibility
Capacity to evolve
An intervention can deliver a feature. It can also leave behind tools, knowledge, autonomy, and better conditions for the next decision.
No onboarding I cleared the trail alone. When three people arrived, they didn't stumble in the same places.
People, knowledge, and team
Explaining decisions, documenting context, reviewing, pairing, and teaching reduce dependence on individual knowledge. Technical leadership also happens through work that makes other people more autonomous.
Few days left, weeks of work An open Meet call all weekend. No one had to figure it out alone.
Experience as evidence
Tools change. Judgment remains.
Current
2024
2024
2021 to 2023
2021 to 2022
2020 to 2021
2017 to 2020
Back to the beginning
Software development is human, too.
I enjoy interesting problems and good people to solve them with.
Message sent
I received your message and will reply as soon as possible.