Based in Suffolk, UK · Open to permanent opportunities
01
Listen first.
What’s getting in the way?
02
Build something useful.
Bring the pieces together.
＋＋✓
03
Make their day easier.
Keep improving it, together.
That’s the part that matters.
A little curiosity. A useful change.
WHAT THAT LOOKS LIKE
Small frustrations. Worth solving.
I’ve spent more than 11 years building and supporting the tools people use in a healthcare business. Here are a few ways that work has helped.
↳
Less copying. More getting things done.
I brought repetitive document-preparation steps into one application, making the process simpler for the people doing it every day.
↔
Better information. Better conversations.
A messaging platform grew through colleagues’ feedback, helping them understand concerns and support people remotely.
✓
Someone who sees the whole problem.
I work across software, systems and support. That means understanding what’s happening at someone’s desk as well as behind the screen.
THE PERSON BEHIND THE WORK
I love the puzzle. And the people.
Building something feels like an “ASMR puzzle” to me. I love watching the pieces come together. Seeing it make someone’s life easier gives that feeling a purpose.
I start by listening and seeing the problem firsthand. Then I try an early solution with the people affected and improve it through their feedback.
01
Understand the real problem.
See the work through the person doing it.
02
Make something useful.
Choose a practical solution and try it together.
03
Keep making it better.
Listen, refine and help it fit into everyday work.
THERE’S ANOTHER SIDE TO THIS
Curious about the moving parts?
Open the dark workshop to play with working demos, explore the tools I use and look under the hood. It’s all here when you want it.
I’m Steven. I build software and look after the systems underneath. I like figuring out how things work—and making them easier for the people using them.
BASED IN SUFFOLK, UKBUILDING SINCE BEFORE IT WAS MY JOB
THE CONNECTIONS BEHIND THE WORK
01
An interface is only the beginning.
JavaScript, React and Electron: bringing the work behind the screen into a place people can actually use.
Drag a node, or focus it and use arrow keys. Enter to explore.
ONE PROBLEM. MANY LAYERS.Applications ↔ Automation ↔ Data ↔ Infrastructure ↔ PeopleEXPLORE ↓
01 / THE WORKBENCH
Don’t just read it. Get your hands on it.
Small, working explainers inspired by the problems I enjoy. Change an input, break a connection, step through an instruction. See what changes.
</>Curious how this works?Open the code. Watch the state change.
THE REAL-WORLD CONNECTION
Getting the repeated work out of the way.
At Medical Resources Inc., I brought repetitive document-preparation steps into a desktop application. It evolved from browser automation to a direct API integration, with the people doing the work at the centre of the process.
INTERACTIVE EXPLAINER
This is a new, simplified batch-processing example. It uses fictional workshop requests, not healthcare data or employer software.
01Collect8 sample requests
→
02ValidateMissing or invalid fields
→
03ReconcileRepeated references
→
04PrepareReady for the next step
Incoming requests
EDIT ANY FIELD
Reference
Customer
Quantity
What comes out
WAITING FOR INPUT
—Ready
—Needs attention
—Repeated
↳
Some requests are incomplete. Some turn up twice.
Run the batch to find out which.
Everything runs in this browser. No requests are uploaded.
THE REAL-WORLD CONNECTION
Understanding the machine, one instruction at a time.
I started a Game Boy CPU emulator to learn bitwise operations and assembly, testing it instruction by instruction. This separate teaching machine lets you explore the fetch-and-execute loop.
INTERACTIVE EXPLAINER
A bounded five-instruction teaching example, built for this portfolio. It is not a complete Game Boy emulator and does not need a game ROM.
The program
HEX → INSTRUCTION
Inside the machine
READY
REGISTER B0000000000
REGISTER C0000000000
PROGRAM COUNTER000 instructions
MEMORY / FIRST 32 BYTES Highlighted = next instruction
Press Step to fetch the first opcode.
THE REAL-WORLD CONNECTION
A system is more than the happy path.
Networks, VPNs and redundant communications have been part of my infrastructure work. Here you can explore why having another route matters when a connection fails.
INTERACTIVE EXPLAINER
A shortest-path simulation. Link costs are illustrative milliseconds, not measurements of real hosts or an actual internet traceroute.
Connection switches
TRY BREAKING A LINK
Trace a route from your device to the service.
02 / BEHIND THE WORK
Different problems. The same curiosity.
Software, systems and the people using them. A few connections from my professional work and personal projects.
03 / TECHNOLOGY ATLAS
More than a wall of logos.
Select a tool to see where I’ve used it and follow its connection to the work. Experience has context—not a percentage bar.
○ Established use ◐ Developing or contextual experience
04 / THE PERSON AT THE KEYBOARD
A puzzle that comes to life.
Building something is deeply satisfying to me. I describe it as an “ASMR puzzle”: the pieces gradually connect, and then you get to watch them work.
That curiosity takes me from simulated engines in Garry’s Mod to registers in a Game Boy CPU. At work, it means understanding how the application, the data, the system and the person fit together.
The best part is seeing something I built make someone’s day easier. I want to make the world an easier, happier place—and useful software is one way I can contribute.
Custom software, business workflows, databases, infrastructure and hands-on support in a healthcare business. Working with management and colleagues to turn operational needs into practical tools.
DevelopmentAutomationStaff training
2013 — 2014
Software Development Student Assistant
ITT Technical Institute
Tutoring programming and IT, helping with campus networks and audiovisual troubleshooting, and building a child-care management system as a capstone project.
Associate’s Degree in Software Development and Administration · 2014
HOW I WORK
Start with the person. Follow the problem.
A business is a bit like a program in real life: people, information and decisions moving through a process. I like finding where technology can make that process easier.
01 / OBSERVE
See it firsthand.
Reproduce the issue where it happens. Learn the person’s setup and ask why the steps matter.
02 / INVESTIGATE
Find the recurring friction.
Use logs and other evidence. Decide whether a direct IT fix or a software change fits the problem.
03 / COLLABORATE
Put an early version in their hands.
Work with the people affected. Their feedback helps reveal what the solution needs to become.
04 / INTEGRATE
Make it part of the work.
Agree the wider plan with the team and management, then keep improving it through real use.
05 / THE NEXT CONNECTION
Something worth figuring out?
I’m interested in opportunities to build useful systems, understand real problems and contribute to a team.