C and C++
Embedded, systems software and performance-critical code, new or existing.
- Embedded and systems software
- Modernising existing codebases
- Profiling and optimisation
What I do
Services
Three stacks I use every day. Many projects combine two of them: a Python service with a web interface, or existing C++ code that gets a modern front end.
Python
Backend services, data processing, automation and integrations.
- Backend services and APIs
- Data processing and event streams
- Automation and integrations
Full-stack web
Web applications, portals and internal tools, from database to browser.
- Web applications and customer portals
- Internal tools and dashboards
- Fast, accessible front ends
Working together
Three ways to work together
Which arrangement fits depends on how well the work can be scoped up front. After an introductory call you get a proposal with a concrete price.
Hourly
For work whose size is not known up front: building alongside your team, research, or a codebase that needs understanding first.
- Invoiced monthly on hours worked
- Scale up or down as needed
- Remote, or on site by arrangement
Fixed-price project
For well-defined work with a clear outcome. After a short exploration you get a fixed price per phase.
- Fixed price per phase, agreed in advance
- Interim deliveries
- Code and documentation are yours on delivery
Maintenance and support
For software that is already running: updates, security patches and one point of contact when something breaks.
- A fixed number of hours per month
- Agreed response times
- Cancel monthly
Process
The same four steps, whatever the stack
Introduction
A free half-hour call. You explain what is going on, I tell you honestly whether and how I can help.
Proposal
A short written proposal covering the approach, what is in and out of scope, and an estimate in hours or a fixed price.
Building
Work in short iterations, with interim deliveries you can review or test yourself. No surprises at the end.
Delivery and handover
Code, documentation and a handover to your team. I can stay available for maintenance afterwards, but you are not tied to me.
Questions
About pricing and arrangements
What does it cost?
That depends on the arrangement: hourly, a fixed price per phase, or a maintenance agreement. After an introductory call you get a written proposal with a concrete price. All amounts exclude Dutch VAT (btw).
Who owns the code?
You do, once the invoice is paid. Exceptions, such as open-source components with their own licences, are listed in the proposal.
Will you sign an NDA?
Yes. Feel free to attach it to your first email so the conversation can get specific straight away.
Can I hire you just for advice or a review?
Yes. A code or architecture review, a second opinion on a technical decision or a performance investigation works well as a small hourly engagement.
Next step
Tell me what you are working on
A short email with some context is enough. I reply within one working day, even when I am not the right person for the job.