Elton Sakyi
I’m at my best where the blueprint ends.
When the requirements are incomplete, the logic is difficult, and the product still needs to feel effortless, I turn ambiguity into structure and structure into something people can use.
Step inside the systems I’ve built.
Four systems
Pick a world. The camera goes there.
The challenge
A camp responsible for children’s health was managing 250+ applications on paper. Parents, administrators, and medical staff all needed the same camper record, but each needed a different view of it.
Camp Burnt Gin
One application platform with four role-scoped portals, from intake through audit.
How it works
One camper record sits at the centre. Each role gets a different projection of it, decided server-side by Laravel policies, not by hiding buttons in the UI.
Switch roles on the right and watch the same record change shape.
The decision that mattered
Authority is shaped per role, not stacked. Only a super admin can read the audit trail. A clinical override needs the medical role, which a plain administrator does not hold. Medical staff can open a camper’s file only while that camper is active. Every access is written to the audit trail.
Shipped
Role explorer · one camper record
simplified from the policy layer
Sees only their own application, and only the parts they are responsible for.
Camper #4118 · Session 3
Submitted · awaiting review
Audit trail: appended, never edited
No access recorded yet. Switch role to write an entry.
Follow one rent payment
illustrative record
July rent becomes an obligation
A charge is written against the tenancy. It is an event, not a mutable balance field.
The challenge
Rent in Ghana often moves offline: cash, transfers, part payments. When money and records disagree, someone loses a dispute.
Wyncrest
The whole tenancy lifecycle on one append-only ledger. Co-founder, sole developer.
The decision that mattered
Nothing in the ledger is ever updated in place. A correction is a new entry that points at the old one, so a balance can always be walked back to the event that caused it. Duplicate captures are rejected at the boundary rather than cleaned up later.
What holds it together
The challenge
Students pick majors with almost no view of what the work pays, where demand is going, or what the degree returns.
Pathfinder-X
Six decision domains, three federal sources, one queryable schema.
The decision that mattered
Every answer keeps its source. BLS, O*NET and College Scorecard use different codes, cadences and units, so nothing is merged into an anonymous average; each domain resolves to the dataset that can actually defend it.
One question, six lookups
If I major in Computer Science, what am I walking into?
College Scorecard
Majors
CIP code 11 resolved to the programs that actually award it.
O*NET
Careers
Occupations mapped from the major, not from job-title guesswork.
O*NET
Skills
Tasks and tools per occupation, deduplicated across related codes.
BLS OES
Salaries
Wage distribution by occupation and area, kept as ranges.
BLS projections
Job demand
Ten-year outlook joined on the same occupation code.
College Scorecard
Outcomes
Completion, debt and earnings for that program by institution.
Structure of the query path, not published figures. Live values come from the ingested datasets.
The challenge
Financial advice arrives as advice. People need to see the consequence of the choice before they make it.
FutureYou
A decision → consequence → action loop, built and presented in a hackathon weekend.
The decision that mattered
The arithmetic layer is deterministic and testable. The AI layer only explains what that layer already computed, so the numbers can be defended and the guidance still reads like a person wrote it.
Move the dial. The horizon moves with it.
sample scenario
22 mo
until the $6,400 card at 18.9% is cleared
$76,071
invested balance at the horizon, 7% a year
$1,520
interest paid on the card before it clears
$240 a month compounding for 15 years
How I work
Four systems, one habit: decide the rules before writing the screens.
01
Find the constraint
Medical privacy, disputed money, mismatched federal datasets. The hardest rule shapes the schema.
02
Model it once
Normalized tables, domain engines, service layers. Logic lives in one place so four portals can share it.
03
Enforce on the server
Policies and gates, not hidden buttons. If a role cannot do it, the request fails and the attempt is recorded.
04
Prove it, then ship it
Automated tests, audit trails, a CI/CD pipeline built for EC2 behind Nginx. Deployment is part of the design, not an afterthought.
About
I build the part that has to work.
The permissions nobody should be able to bypass. The financial records nobody should be able to rewrite. The workflows that must remain clear when four different roles, hundreds of decisions, and real consequences collide.
That is where I do my best work.
I’m a full-stack software engineer with a computer science background and a habit of thinking beyond the feature in front of me. I look for the missing rule, the dangerous assumption, the broken handoff, and the decision the system must be able to explain six months later.
I’ve brought that approach to platforms for housing, insurance, career intelligence, and financial decision-making. Different industries, same responsibility: turn complexity into software people can understand, operate, and trust.
I don’t just ask whether a product works.
I ask whether it holds up.
B.S. Computer Science, minor in Chemistry · Rock Hill, SC
Associate in Science
Tools I reach for first
Java · PHP · TypeScript · SQL · Laravel · React · MySQL · AWS EC2 & RDS · Nginx · GitHub Actions · Claude Code
Also: Python, JavaScript, MongoDB, Node/Express, Vite, IAM, PHP-FPM, PM2, Linux, Postman, Vercel.
Languages
Native bilingual in English and Akan; working proficiency in German and French.
Writing
Digital Dependency: Cognitive and Neurological Consequences of Technology Use · 02/2025
Ethical Responsibilities of Technology Corporations in the Digital Age · 04/2025
Four worlds, one body of work
If you are building something that has to be trusted, I would like to work on it.
eltonsakyi@proton.meOpen to full-time roles