I connect factory floors to business systems. OPC UA, PLC-to-WMS middleware, and PostgreSQL rescue work. 10 years, C#/.NET, zero-drama delivery.
I build the layer between industrial equipment and the software your business
actually runs on.
That means OPC UA connectivity, PLC and SCADA data acquisition, middleware between factory floor and WMS or ERP, and the PostgreSQL databases underneath all of it. Ten years doing this in production for a Dutch industrial software company, serving warehouse and manufacturing clients across Europe.
WHAT I TYPICALLY GET CALLED FOR
Integration that keeps breaking. Data arrives late, arrives wrong, or stops arriving at 3am and nobody knows why. Usually this is not a connection problem - it is a missing deadband, an unhandled reconnect, or a subscription that silently died. I find it and I make it not happen again.
Connecting equipment nobody wants to touch. Older PLCs, undocumented systems, a machine whose integrator went out of business in 2014. I have done a lot of this. It is mostly patience and protocol knowledge.
PostgreSQL databases in trouble. Queries that got slower every year until someone noticed. Schemas that grew organically and now fight the application.
Legacy databases with no documentation and no original developer. I do performance work, schema repair, and the unglamorous administration that keeps production alive.
Greenfield backend work. C#, .NET 8, ASP.NET Core, REST APIs, microservices, PostgreSQL. Built properly the first time so the paragraph above never applies to it.
HOW I WORK
I ask a lot of questions before writing code, because in industrial work the expensive mistakes are almost always requirements mistakes, not coding mistakes. I tell you when something will not work rather than building it and letting you find out. If a job is outside what I do well, I say so - there are plenty of jobs that are inside it.
Everything I deliver is documented well enough that the next person, including future you, can maintain it without calling me. I consider that part of the job, not an extra.
I work in English and French, fluently in both. Based in Tunisia, working
European hours.
Work Terms
AVAILABILITY
Based in Tunisia (UTC+1). I work European business hours and overlap with US Eastern until early afternoon their time. Available for calls between 09:00 and 19:00 CET, and I am flexible for a scheduled call outside that if your timezone requires it.
Typical capacity is 20-30 hours per week for freelance work. I will tell you honestly what I can commit to before we start rather than overbooking and missing deadlines.
COMMUNICATION
I send a written update at the end of each working day or at each milestone, whichever suits your project - short, factual, including anything that is blocked or has changed. You should never have to ask me where things stand.
Mails, Slack, Teams, or Guru messages all work. For anything with real technical complexity I prefer one video call at the start over ten rounds of messages.
I respond to messages within one business day, usually much faster.
PAYMENT AND SCOPE
I work through Guru SafePay on milestones. For projects over roughly two weeks I prefer three or four milestones tied to deliverables rather than one large payment at the end - it protects both of us and keeps scope honest.
Fixed-price for well-defined work, hourly for diagnostic and rescue work where the scope genuinely cannot be known upfront. I will tell you which one your project is and why.
Scope changes are fine and normal. I will quote them separately before doing them rather than absorbing them silently and then being resentful about it, or surprising you with an invoice.
DISCOVERY
Initial call to understand the problem is free, up to 30 minutes. I would rather spend that half hour finding out we are not a fit than have both of us discover it three weeks in.