Full-Stack Developer & DevOps Engineer
Tom Schorn
I build software that holds up in real operation. From the database through the interface to the server everything runs on in the end.
For thirteen years I kept machines and plants running before moving into software development. The mindset stayed: I do not just build, I also operate.
- Open to full-time roles
- Non-profit projects

2011 to 2024
Thirteen years in front of machines that had to run.
Industrial electronics technician. Maintenance, PLC programming and commissioning in manufacturing, plus machine networking and IIoT.
When a plant stops, every minute costs money. That teaches you to chase a fault to its root cause instead of working around it.
- Continuous improvement team, electrical part
- Deputy leadership responsibility
- IIoT and machine networking

Today
Same mindset, different tools.
Florabase is a platform for plant cultivation: monitoring sensor readings, flagging threshold breaches, documenting care. Plus AI-assisted diagnosis from a photo.
React and TypeScript on the front end, Python and FastAPI on the back end, PostgreSQL as the database. Built alone and running on my own infrastructure.
Next up: automation and IoT integration, so sensors and controllers talk to the platform directly. Later for organisations and external systems. This is exactly where my industrial experience meets the software.

Cloud & Operations
I write infrastructure as code.
In a Masterschool project I built an AWS environment with Terraform: a VPC with public and private subnets across availability zones, EC2, RDS with its own subnet group, security groups and routing. Described reproducibly instead of clicked together.
My own applications run on a self-managed Ubuntu server: Docker, reverse proxy, CrowdSec and monitoring. My homelab adds Proxmox for virtualisation and an Omada setup for the network. I know my systems because I operate them, not only because I write them.

Hover a block to see what is behind it.
Notes · draggable
What is it about for you?
One click and you will see whether I fit your case. No jargon.
From the database to the button your people press.
I build complete web applications on my own: interface, APIs, database and the server everything ends up running on. You do not need to coordinate half a team for it.
Florabase was built that way. Version 2 is in use, version 3 is in progress, a mobile app via Capacitor is being built.
See the projectsWriting software is one half. Keeping it running is the other.
Most things do not fail because of the code but because of operations: no backups, nobody sees the errors, nobody applies updates. That is exactly where I come from.
I operate my own applications myself, including servers, backups, certificates and error monitoring. This page loads without cookies in under half a second.
My backgroundRepetitive manual work is usually a solved problem.
Lists someone maintains every Monday. Numbers copied by hand from one system into another. Those routines can almost always be removed, often in days rather than months.
In the continuous improvement team at WERIT this was my daily work: look at the process, find the bottleneck, remove it. Responsible for the electrical side.
My backgroundThen we will understand each other quickly.
Thirteen years in maintenance, four of them in the continuous improvement team. I know what it costs when a line stops, and I talk to your technicians in their language rather than mine.
PLC technology, drives, electrical testing to DGUV V3 and connecting machines via IIoT. The certificates are openly listed on the profile page.
See the certificates