Roots, disciplines, and experiences weaving into one practice
About / inspection as a creative practice
Every thread I pull should reveal more of what people can become.
I am a Houston-based builder with Cameroonian roots. The throughline is not technology for its own sake. It is amplification: understand the system deeply enough that a person, a team, or a generation can move with more agency.
HoustonCameroonian roots
00
One thread, four scales
The biography and the metaphor are the same drawing.
Every system I build makes something survive a handoff. I learned each form of that thread at a different scale, in order.
Weave · Cameroonian roots
Meaning has to survive translation.
The same thing carries different weight depending on context, history, and who is interpreting it. Inspect the structure before trusting the surface.
Registration · Rice → DermaShift → clinical production
At the human boundary, a dropped handoff costs a person.
Bioengineering, then healthcare systems under HIPAA: risk made visible, rollout reversible, evidence attached — because the boundary is where consequence lives.
Branch · Figma & Chill
One thread, many hands, nothing lost in the fork.
A community built through shared making instead of talk — each person keeping their own strength while the thing held together. Figma platformed the result.
Memory knot · OrgX
The decision returns as a receipt the next run inherits.
The continuity layer itself: memory, authority, execution, and proof for governed agent work. The thread, shipped as infrastructure.
01
The root system
Multidisciplinary from the first serious problem.
My Cameroonian roots are not a moodboard. They are an early lesson in translation: the same thing can carry different meaning depending on context, history, and the people interpreting it. I learned to inspect the structure before assuming the surface told the whole story.
Bioengineering at Rice gave that instinct technical rigor. With DermaShift, our team built a low-cost way to detect pressure-ulcer risk and won a national undergraduate design competition. The work joined a human need, clinical collaboration, sensing, product design, and proof. That pattern never left.
Music and dance stay in the background of the practice: timing, tension, counterpoint, release, and the feeling that a technically correct composition can still be unresolved.
A real person. A physical system. A device that had to earn belief.
Pressure-ulcer formation is not a dashboard problem. The team had to understand the clinical need, create a portable diagnostic device, make the economics credible, and explain the evidence clearly. That is still how I want engineering to meet the world.
02
The practice
Inspect deeply. Locate the boundary. Compose the intervention. Leave a stronger system.
Challenges become useful when they reveal the mechanism underneath them. I prefer the kind of collaboration where disagreement sharpens the model and evidence settles the next move.
One practice / different materials
A bend can become a break. A break can reveal the next weave.
Before / tension
A technical problem can look complete while the person living with it still carries the cost.
The knot / decision
Start with the human consequence, then combine the disciplines the intervention actually requires.
After / consequence
Bioengineering became a durable product instinct: understand the system, build the mechanism, prove the outcome.
Rice bioengineering · DermaShift
03
The questions got harder
Each environment added a boundary I could no longer ignore.
This is one evolving practice—not a list of unrelated roles.
01 / Capital One · scale
Can data be trusted before it starts moving?
Regulated finance made data quality, lineage, and reliable ingestion part of the system—not cleanup after the pipeline.
I started Figma and Chill because talking about making was not enough.
What began as an empty Clubhouse room grew into a global BIPOC design community where people made things together in real time. At Config 2021, our team shared how play, connection, community, and culture became a repeatable creative practice.
Building in public where AI infrastructure becomes a human operating system.
I am most interested in founder collaborations and senior/staff work where systems depth, product judgment, and AI-native execution all matter at once.
Connection → community → culture