From rough idea to working thing
I can take a project through the UI, API, database, integrations, and deployment. It means fewer handoffs and fewer places for the original idea to get lost.
A bit about me
I like figuring out how things work and making them work better.
I'm Jorge. I've been building software for more than twelve years - some for clients, some in open source, and quite a few side projects that started with 'I wonder if I can make this.'
The Short Version
Hello, I'm Jorge.
I'm usually the person brought in somewhere between “we have an idea” and “why is this doing that?”
I started using The Code Raccoons in 2015 as a home for freelance work and side projects. Since then I've built web and mobile apps, internal tools, APIs, integrations, and a few things that are difficult to fit into a tidy category.
Before that I worked on HoloLens applications at the Microsoft Innovation Center and helped build a nationwide mobile CRM at Sorteos Tec. Since joining Skyrocket in 2021, I've contributed to more than eighteen client projects. These days I'm based in Vancouver, still making client work and still finding excuses to build tools of my own.
How I Tend to Work
Fix before rewriting
Most existing code does not need to be set on fire. I like finding the part that is actually causing trouble and improving it without turning the whole project upside down.
Explain the weird parts
Every codebase has a few decisions that make sense only after someone explains them. I leave tests and notes around those parts so the next developer is not left guessing.
The side-project habit
If I solve the same problem twice, I start building a tool.
That is how projects like WebTricks happen. It started as a place for the small JavaScript fixes I kept needing on Webflow projects and grew into an open-source library. The blog works the same way: if I had to dig around to understand something, I write down what finally made it click.
Have a project, a technical question, or something behaving strangely?