Why I Build Across AI, Security, and Web3

People often ask why I do not specialize in only one track. My answer is simple: the products I care about rarely live inside one discipline.

AI tools need strong security boundaries. Security products need usable interfaces. Web3 systems need trustworthy identity and clear human interaction. Building across these areas helps me think in systems rather than silos.

AI taught me to design for uncertainty

When working with language models, outputs are probabilistic. You learn to design guardrails, not assumptions. This changed how I architect software: I now treat variability as a first-class concern.

Security taught me to design for failure

Security work improves engineering discipline. Instead of asking “Will this work?”, I ask “How can this break?”. Threat modeling makes product design more realistic and resilient.

Web3 taught me to design for trust

Blockchain systems force explicit thinking about trust boundaries, transparency, and ownership. Even outside web3, those principles improve API design and user communication.

Creativity connects everything

My creative work as Maenka influences my technical work more than people expect. Music improves my pattern recognition, patience, and emotional calibration. It reminds me that technology is only meaningful when it serves humans.

What this means for internships

I am looking for internship environments where interdisciplinary thinking is valued: teams that care about architecture quality, security basics, and user impact at the same time. I enjoy learning fast, shipping thoughtfully, and documenting decisions clearly.