I'm a full-stack developer based in Portugal.
I've been part of teams building shared component libraries, public-sector platforms, and a connected-worker platform with a real R&D side to some of its features. It's team work, so I've learned as much from the people I build with as from the code.
I hold an MSc in Computer Engineering from the Polytechnic of Leiria.
CO2GIS is an open-source QGIS plugin for planning CO2 pipeline routes and estimating what they cost to build. It started as my master's project.
You feed it land use, terrain slope and infrastructure data. From that it builds a cost surface, finds the cheapest route across the landscape, and then works out the pipeline diameter, construction cost and booster stations based on the CO2 flow. The idea is to let researchers and planners run a first-pass study without needing to be GIS experts.
CO2 transport and storage has been getting more attention lately, so instead of leaving the plugin as a finished thesis I kept working on it in the open.
🔗 Repository · 🌐 Website
I care less about any particular stack than about the thinking underneath it. Data modelling, spotting where the real complexity actually is, reading code you didn't write, keeping things simple. That carries over between languages. If you can design a clean REST API, the framework is a detail, and moving to a new stack is mostly docs and a bit of syntax, not starting from zero.
Part of why I see it that way is having worked across a fairly wide range. At university it went from MIPS assembly and C up to Python and higher-level work. Professionally it's mostly been React, Next.js and TypeScript on the front, with GraphQL, REST and WebSocket APIs served from different stacks like .NET, Go and Node, and both NoSQL and SQL on the data side. I've also spent time in less common corners: real-time video over WebRTC-based SDKs with live drawing over the stream, and geospatial work with PyQGIS and GRASS on CO2GIS. Different labels, same fundamentals underneath.
Especially now, with AI in the loop, the parts that hold their value are problem-solving, thinking a step ahead about the consequences of a decision, and being happy to keep learning. Those are the things I try to get better at. I also like pulling apart tools I haven't used yet and building odd little side projects, which is roughly how CO2GIS got started.
