Miroslav Machynka

Software built to a standard.

Websites, web apps, desktop software, and the servers underneath them. Built from scratch and kept running long after launch.

Custom websites

Company sites, portfolios, and landing pages, in one language or several. Design, build, launch, and the maintenance afterwards. Rendered on the server, so pages arrive fast and search engines read the real content.

Web applications

Software with users, accounts, permissions, and data that has to stay correct: dashboards, internal tools, booking and management systems. TypeScript from the interface down to the database.

Desktop applications

Applications installed and run on the machine itself, built for Linux first and macOS alongside it. They keep working without a connection, and the data stays on the device instead of somebody else's server.

Servers and hosting

Setting up and running the servers behind the software: deployment, backups, monitoring, and updates. It can run on your own machine instead of a cloud account, so nobody else sets the price or holds the data.

About

I am Miroslav Machynka, a software developer from Czechia. I take a project end to end: the design, the code, the servers it runs on, and the maintenance once it is live.

Whoever designed it is whoever maintains it. Every decision has a reason somebody still remembers, and when something breaks at two in the morning it gets fixed instead of handed off.

I work in Czech and English, for clients here and abroad. Everything runs remotely, so where you are does not matter.

How I work

I decide what a system must never get wrong before I decide anything about how it looks. The failure cases come first, and the interface follows from them.

Every rule I keep is a rule that can fail the build. Discipline that lives in a document is only a preference.

No comments anywhere in the codebase. If a function needs a paragraph to explain it, the function is the thing that is wrong.

I write the shared layer myself: bundling, logging, persistence, translations, background jobs. Twenty packages, so every project starts from the same tested base instead of a fresh pile of dependencies.

Linux first, always. I develop on it, deploy to it, and design for it before anything else. macOS is supported. Windows is not a platform I build around.

I stay after launch. Updates, monitoring, and fixes are part of the work, not a separate contract you find out about later.

Tell me what you are building.

Send a rough description, the deadline if there is one, and any constraints you already know about.