Frontend Engineer · Luanda, Angola
Frontend Engineer crafting scalable React experiences for real-world products.
06 — Open source
Repositories and activity from GitHub—where I experiment and contribute.
07 — Community
I engage on LinkedIn with technical discussions—GraphQL, React Query, security, and frontend craft.
Technical writing and community posts are part of how I lead: clarify hard problems, share what worked in production, and invite better solutions.
02 — Philosophy
Not a checklist of tools—a set of principles I use when trade-offs matter in production.
I treat performance as a feature users feel before they read a metric. That means measuring what matters in production—interaction latency, cache hit rates, and bundle boundaries—not chasing Lighthouse scores in isolation. I design data layers and rendering paths so the UI stays responsive when networks and devices are not ideal.
Accessible interfaces are not a polish pass; they are how we prove the product works for everyone. I build with semantic structure, predictable keyboard flows, and contrast that holds in varied environments. When accessibility is embedded in component APIs and review habits, teams ship faster because regressions surface early.
Codebases outlive launches. I favor explicit boundaries—feature modules, typed contracts, and documentation that explains why decisions were made. Maintainability is the ability for another engineer to change behavior confidently.
Scalability is how quickly a team can add a locale, a workflow, or a new surface without rewiring the entire app. I invest in design systems, internationalization, and GraphQL cache strategies so product growth does not force frontend rewrites.
Great DX compounds. Tooling, lint rules, and architecture docs reduce the tax of every pull request. When developers spend less time fighting the setup, they spend more time on user problems.
03 — Writing
Publications on GraphQL, React Query, security headers, and the craft of debugging—evidence of how I communicate with teams.
Practical approaches for integrating GraphQL and React Query while implementing secure communication through modern security headers.
Foundational guide covering React Query integration with GraphQL and cache management strategies.
Advanced continuation of caching strategies, performance improvements, and production considerations.
A practical and engaging article discussing browser developer tools, debugging techniques, and lessons learned through frontend development.
04 — Selected work
Problem, architecture, and outcomes—not screenshot galleries without context.
Liquidity Radar — collaborative ATM cash map
In Angola, finding an ATM that actually has cash can send anyone into “search mode.” Many people rely on WhatsApp groups to learn where machines still have money—fragmented, noisy, and easy to miss.
Read case study →Live product ↗Feature Intelligence & Execution Replay
Teams see whether tests pass or fail, but not whether a feature actually worked as a real user experience—or where and why execution broke across UI, API, and runtime.
Read case study →Live product ↗AI-Powered Agricultural Marketplace
Agricultural trade in emerging markets often runs on guesswork: opaque pricing, weak trust between parties, and no single place to list, negotiate, buy, and settle payments with clarity.
Read case study →Live product ↗05 — Expertise
Composable systems where routes, state, and UI boundaries align with how teams ship features.
Measured improvements across rendering, bundles, and data paths—not vanity metrics.
Inclusive interfaces built into components, reviews, and release criteria.
Typed data layers with cache design that matches how products actually fetch information.
Tooling and documentation that reduce friction so teams focus on users.