Back

    Reflections

    This is a space for thoughts that live outside of titles and timelines.

    Here, I write about how I experience the world. Life, growth, uncertainty, travel, community, and the stories that quietly shaped me along the way. Some reflections are formed through building, others through failure, and some through unexpected places like anime.

    These are not polished conclusions. They are moments of clarity, written as they come.

    I believe reflection is part of how we become better builders, leaders, and humans. This page is my way of slowing down enough to notice.

    Africa
    Asia
    South America

    On Building in Public

    There's something powerful about sharing your journey as you build. Not just the polished results, but the messy process, the failures, the learnings. When you build in public, you're not just creating a product—you're creating a narrative that others can learn from and connect with.

    I've found that transparency builds trust in ways that polished marketing never can. People see the real you, the real challenges, and the real solutions. This authenticity becomes your greatest asset.

    Building in public isn't about oversharing. It's about being intentional with what you share and why. Every post, every update, every reflection should add value—either to your audience or to your own understanding of your work.

    The Art of Listening

    In developer relations, we often focus on speaking—giving talks, writing articles, creating content. But I've learned that the most valuable skill is actually listening.

    When you truly listen to developers, you hear not just their technical needs, but their frustrations, their aspirations, their context. This understanding transforms how you build products, write documentation, and create community experiences.

    Listening isn't passive. It's an active process of understanding, synthesizing, and responding. It requires setting aside your assumptions and being genuinely curious about what others are experiencing.

    The best solutions come from listening first, then building.

    Community Over Code

    Technology changes rapidly. The frameworks we use today might be obsolete tomorrow. But communities—real, human connections—endure.

    I've seen projects with mediocre code but incredible communities outlast technically superior projects with no community. Why? Because people solve problems together. They support each other. They create value beyond what any single developer could build alone.

    This isn't to say code quality doesn't matter. It absolutely does. But code without community is like a library without readers—technically impressive but ultimately unused.

    When building anything, ask yourself: am I creating code, or am I creating community? The best projects do both.