ebendttl
Software Engineer @Gamr | Full-stack React & Next Developer | AI/ML | Alumni @stackslabs | Open Source Contributor | Open to Freelance & Remote Roles
JavaScript
•
TypeScript
•
React
•
Next
•
AI Engineering
•
AI/ML
•
Prompt Engineering
•
Python
•
Redis
•
PostgreSQL
•
SQL
•
MongoDB
•
Frontend Engineering
•
Backend Engineering
•
Fullstack Engineering
•
Node
•
Docker
•
REST API
Software Developer
Gamr Tech solutions Limited
May 2025 - Present
* Develop and optimize responsive React/Vite/TypeScript web apps using Tailwind and shadcn.
* Build secure features using Supabase SQL migrations and Serverless API functions.
* Collaborate in agile teams, writing clean, documented code and performing code reviews.
* Set up automated E2E testing suites with Playwright to prevent UI regressions.
* Maintain Vercel CI/CD pipelines, resolving version conflicts and environment configs.
I'm currently deep in the intersection of agentic AI systems and distributed state management. Specifically, I'm exploring how multi-agent pipelines handle context retrieval at scale — where vector search recall quality (tuning HNSW parameters like efSearch and efConstruction) directly determines whether an agent reasons correctly or hallucinates a plausible-but-wrong answer. This connects my recent work on HNSW indexing and structured LLM outputs into a single production problem: building retrieval systems that are both fast and semantically precise enough to serve autonomous agents reliably.
On the distributed systems side, I'm studying how CRDT-based consistency models can be extended beyond collaborative text editors into broader application state — specifically whether the algebraic guarantees that make Y.js work for document sync can be applied to shared game state or multi-user configuration trees without a central coordination server. The goal is understanding where CRDTs break down and where you still need something closer to Raft-style consensus.
Love to play Play Station football games.
As a Dev, you should know how and where exactly different tools interconnect in a software building process, so to know which tool is best suited for which purpose and when to introduce it.
| Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
| Mon | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| Tue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| Wed | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| Thu | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| Fri | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| Sat | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| Sun | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |