I work where messy technical systems become products: protocol mechanics, market structure, AI workflows, launch operations, and the interfaces that make them usable.
Led the perps surface from pair-level risk modeling to execution rebuild: funding scripts, OI limits, collateral work, and order placement cut from 18s to under 3.
Fifty Moving Pieces, part 5: what release management is product management taught me about shipping technical products when risk, users, partners, and release pressure all show up at once.
Fifty Moving Pieces, part 4: what production blockers are product problems taught me about shipping technical products when risk, users, partners, and release pressure all show up at once.
Fifty Moving Pieces, part 3: what routing part-time seniors taught me about shipping technical products when risk, users, partners, and release pressure all show up at once.
Fifty Moving Pieces, part 2: what junior-heavy teams need systems taught me about shipping technical products when risk, users, partners, and release pressure all show up at once.
I work close to the machinery: protocol mechanics, risk, indexing, launch pressure, weird edge cases, and the product decisions hiding underneath.
At Dexlyn, the work moved from early AMM experiments into CLMM liquidity, perps, routing, bridge flows, launch operations, and the less glamorous systems that decide whether users trust a product after the first click.
Embersity is the independent version of the same instinct: take a messy idea, get close enough to the technical shape to make real decisions, then turn it into something with a surface, a release path, and a reason to exist.
Dexlyn Labs@DexlynLabs
terminally onλine εngineer@tekbog
@jaysbuildingg
OpenAI@OpenAI