A good developer doesn't always need to write more code.
Sometimes the best decision is:
Let's not build this.
If a feature doesn't solve an important problem, improve the user experience, or create business value, adding it only makes the product more complicated.
Over time, I've learned that knowing what not to build is just as important as knowing how to build it.
I wanted to make a photography website that felt more like an experience than a portfolio.
So I built CINÉRA — a cinematic photography studio website with a 3D gallery, interactive archive, real availability, and a complete booking flow.
You can explore the work, pick a date and time, add your shoot details, and get booked without the usual back-and-forth.
On the studio side, there’s a dashboard to manage bookings and inquiries, plus automatic booking confirmations to take a bit of the repetitive work off the photographer’s plate.
This was built for an appointment-based business challenge, and honestly, I had way too much fun making it.
Twenty-five years of credits, finally on a website that looks the part.
Just take a look at what kind of web we create ✨👇
Reflection of the brand history with taste, precision, and premium branding.
Scroll responsibly: https://productionportugal.com 😉🔥
One problem. Two design directions. Which would you choose?
For AEGIS / 001.05 . Traffic Operations, we explored two approaches to the same challenge: helping city operators understand congestion, incidents and network-wide disruptions without overwhelming them with information.
Both solve the same operational problem. Different approaches to hierarchy and interaction.
If you were behind the control desk . Option A or Option B?