Independent Work & Craft
Personal Projects
Products I build outside work to solve real problems, from defining the requirements to shipping working software.
Motivation
Useful First
Built to solve real problems, not to try new tech
Starting Point
Problem to Requirements
The requirements come before the code
Ownership
Idea to Launch
Business rules, design handoff and delivery
Scope
Frontend to Database
Full-stack, built outside work
Open source · Live
pedrobarbosa.pt
The website you're on, built and run like a product
Project Overview
My personal website, where I show my experience and projects. I treat it like a product at work: a prioritised backlog, small focused commits, and checks that must pass before anything goes live.
Every push runs formatting and lint checks, type checks, tests and a production build, and a failing check blocks the deploy. Every page is sent with security headers that only let it load the site's own files. The code is public, so you can see how I work, not just read about it.
Key Takeaways
Quality gates
Formatting, lint, type checks, tests and a build run on every push, and nothing deploys unless they pass.
Tests that survive refactors
Tests check behaviour and edge cases through what visitors see, so they only change when the behaviour does.
Structure with rules
Folder and import rules are enforced by lint, so each file's scope is clear from its path.
Frontend Implementation
Responsive pages rendered on the server, one theme for every colour and text style, and share images and structured data for search and social links.
- Next.js
- React
- TypeScript
- Material UI
Quality & Delivery
Component and page tests on every push, with deployments that wait for them to pass, plus browser and accessibility tests in Chromium, Firefox and WebKit, run locally and against the live site.
- Vitest
- Testing Library
- Playwright
- GitHub Actions
- Vercel
Independent product · Launched, retired Jan 2026
Growth Tracker
An investment tracker that shows your real average price
Project Overview
A product I took from idea to launch. Users logged their assets, buys and sells, and Growth Tracker calculated the average price they could actually trust when deciding to sell.
Buy 3 units at 500 and sell 1 at 700, and a typical broker app shows an average of 400, even though the remaining units still cost 500. Growth Tracker kept that number accurate, so users could aim for a profit on every unit they sold.
Key Takeaways
Product ownership
Defined the business rules and requirements myself, starting from a problem I had.
End-to-end delivery
Built every layer, from the database to the interface, and took it to launch.
Making value obvious
Learned that a strong feature isn't enough if users can't see its value. I had plans to address it, but the money ran out first.
Frontend Implementation
Implemented a designer's visual design, including asset management, the transactions table, and a chart tracking how the real average price evolved with each transaction.
- React
- TypeScript
- Material UI
- Chart.js
Backend & Core Logic
Built the backend and data model, plus the complex algorithm behind the real average price, covering scenarios like sales made below it.
- Node.js
- Fastify
- Prisma
- PostgreSQL
My Approach
How I Choose What to Build
I build things because they could be useful, not just to try a new technology.
Start With a Real Problem
Every project begins with a problem worth solving, like the misleading average price behind Growth Tracker.
Define Before Building
I turn the problem into clear requirements first, so the code has a purpose from the start.
Next Inquiries & Collaboration
Want to collaborate or discuss an opportunity?
If you're hiring a Senior Frontend Engineer or planning a frontend migration, let's talk about the role and how I can help.