They usually start from a problem of my own. WealthWatcher exists because I wanted all my finances in one place without handing that data to someone else's application, which is why it's self-hosted and will stay that way. I'd rather build something that serves me first: if it holds up for my case, it stands a fair chance of holding up for someone else.
Before I open the editor I want a clear picture: requirements pinned down, stack chosen, architecture in order. It's the phase I care about most, because that's where you decide whether a project will hold up or has to be rebuilt, and it's the one where, on team projects, I usually end up holding the overall picture together. When it comes to writing, I watch the details and keep things minimal: the least that makes them work, without layers nobody will enjoy reading later.
I work with Claude Code and other AI tooling as part of the stack: I use it to automate the repetitive work, keep tests and documentation in step and get to something working sooner. What comes out of it I check myself, and that is where knowing the technology matters: "it works" and "it holds" are two different things, and the difference has to be caught before the code reaches production.
I'm finishing my MSc in Information Engineering in Trento and looking for somewhere to keep building things like these: a team that argues about decisions rather than just executing them, and a field to go deep enough in to become the person others come to, without losing sight of the rest of the stack. In Italy or abroad.
- Based in
- Belluno, Italy
- Languages
- Italian — nativeEnglish — advanced