SELECTED SYSTEMS / ENGINEERING DEPTH
Four systems. Four different kinds of constraint.
A recruiter can stop at the first layer. The technical layer explains the problem, system boundaries and the work I owned across gaming, decentralized science, optimisation and aeronautical R&D.
Technical deep diveProblem · system map · engineering ownership
01 / Problem
Connect consumer software, on-chain behaviour and a physical gaming device without treating them as separate products.
02 / System map
- Surfaces
- Web, Android and consumer applications
- Platform
- APIs, production databases and backend services
- Chain
- Digital assets, payments and on-chain game features
- Operations
- Internal tooling, bots, automation and deployments
03 / Engineering ownership
- 01Build and maintain product surfaces across web and Android
- 02Develop backend services, APIs, production data and Solana integrations
- 03Contribute to Origins, Eggy League and the wider hardware ecosystem
Technical deep diveProblem · system map · engineering ownership
01 / Problem
Turn research artifacts into accessible, ownable knowledge objects without allowing blockchain complexity to dominate the publishing experience.
02 / System map
- Product
- Publishing, profiles and research collaboration
- Data
- Prisma-backed application and publication state
- Chain
- Compressed NFTs and Solana digital asset standards
- Storage
- Decentralized artifact storage through Irys and Bundlr
03 / Engineering ownership
- 01Develop frontend and backend product features
- 02Contribute blockchain integrations and decentralized functionality
- 03Support architecture decisions and tools for publishing research
Technical deep diveProblem · system map · engineering ownership
01 / Problem
Model competing timetable, capacity and student constraints as a result people can understand and act on.
02 / System map
- Input
- Course shifts, capacity and student constraints
- Solver
- Python optimisation and allocation logic
- Interface
- A web flow for submitting and reviewing scenarios
- Output
- Reduced conflicts and more balanced class shifts
03 / Engineering ownership
- 01Translate a scheduling problem into explicit optimisation constraints
- 02Connect solver behaviour to a usable web product flow
- 03Present allocation results without exposing algorithmic complexity
Technical deep diveProblem · system map · engineering ownership
01 / Problem
Turn aeronautical operations and cyber-physical constraints into digital tools a multidisciplinary research team could use.
02 / System map
- Surfaces
- Web and desktop operational applications
- Data
- Databases supporting monitoring and control workflows
- Domain
- Digital and cyber-physical system integration
- Delivery
- Multidisciplinary R&D in an aeronautical programme
03 / Engineering ownership
- 01Develop web and desktop applications for research workflows
- 02Manage application data and database integrations
- 03Collaborate across software, operations and cyber-physical systems
DISCLOSURE BOUNDARY
Enough technical depth to evaluate the work. No invented proof.
The 645-contribution snapshot includes the public signal. Current production work also spans private repositories, operational systems, integrations and internal tooling that cannot be presented as a conventional open-source case study.
- Public evidence
- Products, repositories and contribution history
- Private scope
- Architecture boundaries and engineering responsibility
- Not published
- Credentials, production data and internal implementation
