Yourstruggle11 OS / Case FilesEngineering investigations, filed with evidence.
Start with the summary and outcome. Open a file when you want the constraints, decisions, architecture, trade-offs, and supporting references.
- Records
- 04 case files
- Fast path
- Summary and outcome
- Deep path
- Evidence and investigation
Case register
CASE 001Published package
Active filereact-dragdrop-kit
Controlled drag-and-drop primitives for React: sortable lists and grids, plus a headless Kanban path, built on pragmatic-drag-and-drop and shipped as a tree-shakeable npm package with a live demo.
A reusable layer for reorder and board moves where application code owns IDs, positions, and persistence while the toolkit standardises drag mechanics and drop semantics.
Filed UnderUI Engineering / Open Source
References03 external links
View CaseCASE 002Documented systems build
NotifyFlux
Multi-tenant notification stack: Express and Socket.IO, MongoDB change streams, Redis-backed socket fan-out, JWT-scoped tenancy, and a React admin console for delivery visibility.
An end-to-end path from persisted events to tenant-scoped real-time delivery, with an operator-facing UI that shows activity instead of hiding it behind raw API calls.
CASE 003Live product build
HaveItDiscussed
Developer community client: discussions, threaded comments, likes, profiles, social graph, notification hub, and dark mode—deployed to Netlify against a separate Node API (`HaveItDiscussed-Server`).
A shipped forum product where reading, posting, and notifications share consistent client patterns instead of each screen inventing its own data lifecycle.
Phlo Systems — trade-finance workflows
Frontend work on regulated trade-finance and operations surfaces: long-running cases, document-heavy steps, and dashboards where operators need current status without fighting the UI. Filed while the implementation is still evolving inside the organisation.
A documented line of work on enterprise workflow UX and live data—scoped honestly as in-flight, with public references limited to organisation context and role-level description.
Filed UnderEnterprise fintech / workflow UX
View Case