Selected work
Many of my projects begin with work spread across several tools or handled by hand. I learn how the process works today. I pay close attention to breakdowns and to what the people involved need to see or control.
I then build software around that understanding. Depending on the need, I may build a customer-facing product, an internal tool, a mobile app, an online store, or a service that connects existing systems.
Case 03
Mobile application for connected camera hardware
Putting connected cameras and editing in one mobile app
Camera controls and image handling are available in one mobile interface.
- Photography hardware
A hardware engineer designed and built the camera rig. I contributed to the hardware software and built the mobile app.
Also built
Shops and sitesOnline storeA full online store for a client, from the catalogue to the server that runs orders and content.Vue · Node
Built a full online store for a client: catalogue, customer-facing pages, and the server that runs orders and content, without splitting the work across a separate frontend and backend team.
Devices and mediaLivestream-to-device productSoftware that watches livestream activity and drives physical smart devices when configured events occur.Contributed to
Built software that watches livestream activity and drives physical smart devices when configured events occur. The work covered the server, operator interface, desktop tooling, and a mobile companion.
Devices and mediaPrivate photo-sharing platformBackend services and a mobile companion where owners control whether a photo is private or public.NestJS · Fastify · Prisma · PostgreSQL · S3 · Firebase Admin
Built backend services for accounts, feeds, groups, invitations, photo permissions, favourites, and member roles. Owners control whether a photo is private or public. A mobile companion talks to the same services. Media can be delivered through object storage and a content-delivery network.
Shops and sitesBusiness websitesService websites that explain the offer in plain language and let visitors send an enquiry directly.
I build service websites that explain the offer in plain language and let visitors send an enquiry directly. The work covers responsive interfaces, accessible forms, local search metadata, structured data, canonical URLs, spam protection, and email-based enquiry handling. This includes a series of sites for US service businesses.
Systems and supportEducation and administration systemsSystems for a university student association: quizzes, question banks, member records, and elections.Contributed to
Built and extended systems for a university student association: quizzes, question banks, score sheets, member records, alumni information, galleries, elections, and academic content. The most useful improvements were bulk question upload, automatic quiz-state updates, clearer validation, and administrative routes that replaced repeated manual entry.
Systems and supportConversational support toolsA web-based assistant for text and voice conversations that I contributed to.Contributed to
Contributed to a web-based assistant that supported text and voice conversations. I worked on voice integration, user context, analytics endpoints, and screens for reviewing conversation quality. Staff could inspect recurring questions and failed conversations.
Systems and supportHealthcare business platformA full-stack application for a healthcare business, including the web interface and backend authentication.Contributed to
Contributed to a full-stack application for a healthcare business, including the web interface and backend authentication work.
How projects run
You explain what happens today.
A technical brief is optional. Explain who does the work and what happens now. Tell me which part causes the most trouble.
Four tools sit at the corners of the drawing: an inbox, a spreadsheet, dashboards and a chat. Lines cross between them and one line is broken. A ring pulses where it breaks. I map the work and identify unknowns.
I review the current tools, data, risks, and decisions that could affect cost or delivery.
The same crossing lines, now numbered one to six. Two question marks sit on the parts nobody has pinned down yet. We agree on the first release.
The scope is written in plain language. Technical choices are explained where they affect the product or future maintenance.
A frame is drawn around the top row and labelled First release. The rest comes after it. I build in visible stages.
You see working progress, test important flows, and receive documentation for handover or continued support.
The crossing lines fade and one clean path is drawn through all four tools, stage by stage.
Why Skybreaker
One engineer can follow the whole problem
A problem seen in the interface may begin in the database or in an external service. I can trace that path and make changes across the product without losing sight of the person using it.
Existing software is welcome
Many useful projects begin with code that already exists. I am comfortable reading an unfamiliar system. I find the risky areas and improve them in stages while current users still depend on the product.
Failures are part of the design
External services become unavailable. Mobile connections drop. The same event may arrive twice. I plan for those conditions and give operators enough information to recover.
Technical decisions stay understandable
I explain choices in terms of cost, delivery, user impact, and future maintenance. Technical readers can inspect the deeper reasoning, while other stakeholders can still take part in the decision.
Free for anyone
Brief builder
Answer a few plain questions and the brief writes itself. Keep it, or send it to me.
Has your work outgrown the tools?
A short self-check on how your work runs today, with a plain answer on what to do next. Sometimes the answer is to tidy what you have.
Field Notes
Short engineering notes from real work, some with a small live demo.
Tell me what happens today.
I will tell you whether Skybreaker is a suitable fit and suggest a practical next step.
Prepare a brief first