A freelance Python developer for integrations, data and smart tools.
Does data need to move between systems on its own, or is there a chore that is still done by hand? With Python you have something working quickly. I work as a freelancer from Enschede, remote for the Netherlands and Belgium. With AI assistants there is a working proof of concept to review within days, checked and tested by me.
- Based in
- Enschede, NL
- Works in
- Netherlands and Belgium, remote
- Language
- Python
- Proof
- Own projects, private and so unnamed
Quick to build, easy to maintain.
In Python you have something working fast. That makes it strong for links between systems, processing data and small web services. The next developer can read the code easily, too.
I have worked as a developer for nine years, mostly on web applications. I use Python for projects and tools of my own. They live in private repositories, so I describe them below without names or links. Ask if you would like more detail.
Python work that takes chores off your hands.
Clients usually come to me with one of these four jobs.
Links between systems
Data from one system ends up in the other on its own, so nobody retypes it.
Processing data
Reading files and exports, cleaning them up and turning them into an overview you can work with.
Small web services
A piece of software with its own address that other programs can call, for example to fetch data from an outside service.
Automating recurring chores
Work that is done by hand every week, from now on at a set time and with a message when something goes wrong.
AI as a working method.
I work with AI assistants, but I do not sell them as a service. They take over the routine work, so a working prototype of the most important part can be running within days. I decide how it is put together and read and test every line myself. A proof of concept is not a finished product: real use still needs testing, security and review.
Tracker, my own tool for tracking work and bugs, had login by emailed code and data import and export on day one, and was live. I built a registration app for a school the same way.
From idea to a running program.
Four steps, and at each one you have something you can look at.
Intro call
A 20-minute call: what should it do, and what is not working now?
Proof of concept
Within days a working version of the most important part, to test whether the idea holds.
Build
In small steps, on a test environment you can follow yourself.
Handover
The code lives in your own repository, tested and documented, so someone else can continue without me.
Python work from my own projects.
This is my own work, not client work. The code is in private repositories, so I describe what it does without names or links.
A web service that syncs training data
A small Python web service (FastAPI) that fetches training data from a sports-watch platform for a training app of my own. Now archived.
A tool that saves video transcripts
A Python program that stores the transcript of an online video, based on the captions the video platform already has.
Tools for my own work
Scripts and helpers that keep the conventions and settings for my projects in one place.
A chore that should run by itself?
Tell me what is done by hand now, or which systems need to talk to each other. I usually reply within one business day.