Full stack developer

I build systems
that work.

I am a full stack developer with 15+ years behind me. I take care of every layer of the project: the backend, the web interface and, if needed, the mobile app. If what you want will not work the way you imagined it, I will tell you why, and show you how to reach the same goal better.

Tell me about your project → See what I have built

Or start with a system audit

// writing code since 2010

/01

Featured projects

All projects →

Web application and API

Ticketing platform

From ticket purchase to entry control and follow-up: a web system with payments, invoicing, a mobile API and a community layer.

How it was built →

CreateInvoiceJob.php

public function handle(): void
{
    $order = Order::with(['billingAddress', 'user', 'items'])->find($this->orderId);

    // On-site (POS) sales are invoiced through another flow and have no billing address.
    if (Str::startsWith($order?->order_number ?? '', 'POS-')) {
        return;
    }

    // What was actually paid is authoritative, not the list price of the items:
    // a fully discounted order has total_amount = 0 and must not be invoiced.
    if ((float) ($order?->total_amount ?? 0) <= 0) {
        Log::info('Invoice skipped: order total is zero', ['order_id' => $this->orderId]);
        return;
    }

    if (empty($order?->billingAddress)) {
        Log::error('Invoice skipped: billing address is empty', ['order_id' => $this->orderId]);
        return;
    }

    // ... build the invoice and hand it to the provider configured for this organiser
}

Self-service platform

Wholesaler integration platform

Connects online stores to over 400 wholesalers, with automatic price, stock and order handling, no developer needed. Behind it, it processes up to millions of records per second, reshapes and saves them by rules with no room for error, keeping states and statistics too.

How it was built →

Marketing automation

Statistics, SEO and email campaigns

In-house web analytics, SEO monitoring and email campaigns that are measurable, protected, and do the routine work on their own.

How it was built →

RecommendationPolicy.php

public function evaluate(User $user, string $channel, ?CarbonInterface $now = null): PolicyDecision
{
    $now = ($now ?? Carbon::now())->copy();
    $reasons = []; // collect ALL reasons, not just the first, so a preview can explain every skip

    if (! (bool) $this->cfg('enabled', false)) {
        $reasons[] = 'kill_switch_off';
    }

    if ($user->is_banned || $user->deleted_at) {
        $reasons[] = 'account_blocked';
    }

    if ($channel === self::CHANNEL_EMAIL) {
        if (! (bool) $user->is_subscribed) {
            $reasons[] = 'no_marketing_consent';
        }
        if ($this->emailSuppressed(trim((string) $user->email))) {
            $reasons[] = 'email_suppressed';
        }
    } elseif ($channel === self::CHANNEL_PUSH) {
        if ($this->isQuietHour($now)) {
            $reasons[] = 'quiet_hours';
        }
    }

    // ... weekly cap from the shared marketing ledger, then the holdout control group
}

Web business system

Dental practice management

Appointments, treatment records, cash desk, invoicing and regulatory reports in one system, for multiple practices.

How it was built →

ChangeAuditor.php

/** Temporarily disable logging, e.g. during a bulk import or seeding. */
public static function withoutLogging(callable $callback): mixed
{
    $previous = self::$paused;
    self::$paused = true;

    try {
        return $callback();
    } finally {
        self::$paused = $previous;
    }
}

/** On `updating`, keep the original row in memory, so no extra SELECT is needed. */
public function captureOriginal(Model $model): void
{
    if (! $this->enabled($model)) {
        return;
    }

    $this->originals[spl_object_id($model)] = $model->getOriginal();
}

/02

What I do

01
Custom software

Systems fitted to your business processes, not an off-the-shelf package you have to adapt to.
02
Website development

Websites and web applications that are fast, secure, and still easy to work on in two years.
03
Small and large features

A new feature, an integration or a whole module. It can be a one-off job, whatever the size.
04
Live system maintenance

If your system is already running, I can carry it on: fixing bugs, extending it and keeping an eye on operations.
05
Optimisation and scaling

When a system slows down or cannot take the load: caching, message queues (Redis, RabbitMQ), asynchronous processing and database tuning.
06
Mobile apps

iOS and Android apps, from design to the day they reach the app stores.
07
Legacy refactoring and redesign

I rewrite an old, hard-to-handle system feature by feature, so it stays usable the whole time and its behaviour does not change.
08
Consulting and system design

I help you decide the architecture, the data model and the technology, so the system stays extensible and cheap to run.
09
Diagnostics and audit

I go through your system and tell you where the bugs, the slowdowns and the security and maintenance risks are. At the end you get recommendations in order of priority.

RK. Not Ready Kit, not Random Kode. Just me.

/03

What I do not take on

I do not hand over half-finished work. If it is not carried through and tested, I do not deliver it.
I do not request more data than is needed. Needlessly large, unoptimised data requests are what slow a system down later.
I do not just nod along. If what you want will not lead to your goal, I will say why and show you a way that will.

How we can start

Three ways to get going

Recommended start

System audit

I go through your system and tell you what is wrong, how risky it is, and what to start with.

Review of code, database, performance and security
An issue list in order of priority and a proposed next step
A walkthrough call, with no obligation

How the audit works →

New system or MVP

I turn your idea into a working product: design, development, go-live. We build the essentials first, then extend.

Requirements turned into a system design
Regular demos, so you see where we are
Handover and documentation, and I am around afterwards

Tell me about my idea →

Extending an existing system

Extending a live system, fixing bugs, speeding it up, or gradually rewriting old code while it keeps running.

New features and integrations
Performance and bug fixes
Legacy refactoring, with a safe cut-over

What needs developing? →

An example of a good ecosystem

Apps that build on each other, in one shared system

An example of a good ecosystem

Web platform

The core of the system: catalogue, cart, payment, ticket issuing and API. Everything else connects to it.

Hover or tap a node to see what it is connected to.

Background

Full stack skills, in one pair of hands

PHP and Laravel

This is my main field, and I have worked in it for years.

Database systems

I design and tune databases, and I have worked with large data volumes.

Frontend and mobile

HTML, Twig, JavaScript and React Native. I give the interface and the app as much attention as the backend.

High-load systems

I have worked on systems where speed and stability are not up for negotiation.

Operations

Background jobs, message queues (Redis, RabbitMQ), caching, scheduling, health monitoring. So that what I build runs steadily in production.

Integrations

Payments, invoicing, email, push notifications and external systems, all wired into one system.

Technologies

Backend: PHP 8.x Laravel 12 Queues and events RabbitMQ Permission systems Feature flags
Mobile: React Native Expo TypeScript iOS Android OTA updates
Real-time: Laravel Reverb Echo WebSockets Pusher-js
Authentication: Sanctum JWT Socialite (OAuth)
Integrations: REST API Webhooks SOAP Payment providers Third-party APIs External systems Swagger / API docs
Database and cache: MySQL / MariaDB PostgreSQL MongoDB / NoSQL Redis Stack and Search
Media and documents: FFmpeg HLS streaming Image processing (WebP) PDF generation Excel export QR codes
Frontend: Blade Twig Smarty Tailwind Bootstrap 5 SCSS / SASS / LESS JavaScript jQuery Vite WordPress
Version control and deployment: Git GitLab GitHub Deployer CI/CD
Infrastructure: Docker Docker Compose Deployment pipelines Jira

/04

How we work together

01

Conversation

I learn your goals and constraints. The first call is free.
02

Proposal

A concrete plan, timeline and price, with no surprises afterwards.
03

Development

Regular demos, so you always see where we are.
04

Handover and support

I do not disappear after go-live.

/05

What I have learned

All articles →

FAQ

What is worth knowing before we start

Do you work at a fixed price or on a time budget?

It depends on the task. If it is well defined, I give a quote with an agreed scope. If it may change or needs research, we work on a time budget. At the start I always write down what is included.

How fast do you reply?

Usually within 1 business day. If it is urgent, say so in your message.

Do you work on existing systems too?

Yes, that is most of my work: extending live systems, fixing bugs, speeding them up and redesigning old ones. First I go through the code and tell you what I see.

Do you work alone or in a team?

Usually alone. If the job is bigger, we can handle it as a team, and I have led a development team before.

What happens after handover?

You get documented code and a handover. If you want, I can take on maintenance and further development afterwards, but it is not required.

How do we work together if we are far apart?

I work remotely. We talk over video, phone or in writing, and you follow progress in regular demos.

Have an idea, or a system that needs work?

Write a few lines and I will reply within 1 business day.

Write, and we will sort it out → LinkedIn ↗

I build systems that work.

Ticketing platform

Wholesaler integration platform

Statistics, SEO and email campaigns

Dental practice management

Custom software

Website development

Small and large features

Live system maintenance

Optimisation and scaling

Mobile apps

Legacy refactoring and redesign

Consulting and system design

Diagnostics and audit

Three ways to get going

System audit

New system or MVP

Extending an existing system

Apps that build on each other, in one shared system

Web platform

Full stack skills, in one pair of hands

PHP and Laravel

Database systems

Frontend and mobile

High-load systems

Operations

Integrations

Technologies

How we work together

Conversation

Proposal

Development

Handover and support

Bot protection for a contact form without a captcha

A Laravel gotcha: the throttle counter is shared

A strict CSP in Laravel, with Vite

What is worth knowing before we start

Have an idea, or a system that needs work?

I build systems
that work.