Seeking wisdom. Building interfaces. Leaving traces.
I'm a product-minded frontend engineer, builder and occasional wanderer based in Madrid.
I work somewhere between software, interfaces, systems, AI, and the strange human rituals that happen around them.
Not everything needs to be explained. Some things should just feel like a door left slightly open.
const peppoasap = {
base: "Madrid",
language: ["TypeScript", "broken Spanish", "late-night thoughts"],
domains: ["frontend", "product", "AI", "data", "automation", "systems"],
pattern: "turning messy signals into usable things",
currentQuest: "building tools that feel less dead",
quote: "Only a Sith deals in absolutes"
}I build digital products, internal tools, platforms and experiments.
Mostly with:
- TypeScript
- Angular / React / Next.js
- Node.js / NestJS
- design systems
- data visualization
- AI-assisted workflows
- automation layers
- strange prototypes that sometimes become real
I like software that has structure, but not stiffness.
I like interfaces that reduce noise.
I like teams that think before they scale chaos.
The best tools are not the ones that show off.
They are the ones that quietly change how people move.
Some themes keep coming back:
technology as leverage
interfaces as thinking spaces
AI as a companion for cognition
software as a cultural object
work as something we still need to redesign
small teams doing unusually ambitious thingsI’m interested in the invisible parts of building:
coordination, attention, incentives, language, trust, momentum.
Code is rarely just code.
Most bugs start somewhere else.
A talk about product teams, ownership, collaboration and the moment development stops being “just implementation”.
A talk on Angular developer experience, new control flow syntax and the small revolutions hidden inside DX improvements.
- frontend architecture as product infrastructure
- AI inside real workflows, not just demos
- browser-based intelligence
- data interfaces that don’t punish the user
- CRMs and business software with less existential dread
- automation as a way to recover human attention
- how small teams can punch above their weight
- why most “digital transformation” still feels spiritually offline
Build things that are useful.
Make them understandable.
Keep them human.
Don’t worship complexity.
Don’t confuse polish with meaning.
Don’t let process become a temple.
Design for the person who is tired.
Code for the person who arrives after you.
Question the default before optimizing it.
Stay technical.
Stay naive.
Stay dangerous in the right rooms.
The expert knows the rules.
The beginner doesn’t know which walls are sacred.
That can be a weakness.
Sometimes it is the whole advantage.
I like building from that edge:
serious enough to ship, naive enough to ask why, weird enough to try anyway.
- LinkedIn: Giuseppe Ettorre
Build useful things. Keep them human. Leave enough mystery for the next version of yourself.