About Me
I'm a software developer currently hacking on personal and open-source projects in Ruby and Go. Over the years I've messed around with JavaScript, PHP, Python, and plenty of other tools and languages.
Main interests: systems programming, building scalable systems, and the full software growth cycle — from early prototypes through to production and beyond.
Work Experience
Developed an automated fuel price data collection system using official APIs, with scheduled scraping routines and cloud-based processing infrastructure. Built geographic mapping logic, PostgreSQL data pipelines, and monitoring workflows using Cloudflare tools.
Tech stack: Node.js, Cloudflare Workers, PostgreSQL, NeonDB, APIs REST, Data Scraping
Developed an MVP platform for managing Boletos for solar energy companies, including PDF data extraction, automated validation, notifications, and cloud storage integration. Implemented recurring alerts, weekly financial summaries, and scalable storage architecture with automated backup workflows.
Tech stack: Ruby on Rails 8, ActiveJob, SolidQueue, PostgreSQL, ActiveRecord, Google Drive API, Cloudflare R2, Mailgun, RSpec, FactoryBot, AuthenticationZero, CSS-ZERO
Worked on a Laravel-based platform used to manage users, wallets, campaigns, and games across multiple clients. Implemented features such as deposit bonus campaigns, alternative wallets, usage analytics (active users heatmap), and game statistics like most-played games. Improved performance on the games page, refactored controller logic into services for better modularity, and fixed multiple production bugs.
The system uses PHP (Laravel 11), MariaDB with Eloquent ORM, Blade, Bootstrap, and PHPUnit for testing. Code was maintained and reviewed using Bitbucket.
Built the MVP from day 0 within a team of 4 engineers, did all the logic of Condominiums, Residents, Deliverers and Packages. From register of Condominium to notification in the Resident whatsapp. Also did integration with whatsapp bot microservice that was built using golang.
Tech stack: TypeScript, JavaScript, Node.js, Adonisjs, MySQL, Prisma-ORM
Volunteer Work
I've been working with other programmers through Slack and GitHub issues/PRs to ship changes in the stocks-in-the-future codebase. The system uses Rails 8, Pundit for authorization, and PostgreSQL as the database.
The team was already following the "expand and contract" pattern, and I received guidance from a more experienced developer to implement changes with that approach in mind. One of the features was intentionally split into two PRs so the system could support both versions at the same time, with all existing and new tests passing, before removing the old path.