Backend engineer, Go and PHP
I've spent twelve years building backends for high-traffic online shops. These days I also build my own apps single-handed: the API, the mobile app, CI and the release.
I write REST services in Go with Fiber, GORM and PostgreSQL. Sign-in runs on JWT, access is role-based and each group of routes has its own rate limit. Anything involving money leaves an entry in the audit log. I run the tests against a test PostgreSQL database, not mocks.
I've spent years working on shops with 400,000 products in the catalogue and more than a thousand orders a day. In a shop like that, nobody should be kept waiting by an import or a slow third-party service. Imports run through queues and data sits in Redis and Varnish caches. Integrations keep working even when a partner's service stops responding.
Backend, mobile app, landing page, CI and the release itself. Single-handed, I've taken a project from an empty repository to a public beta on TestFlight and test builds for Android, so I know where time usually gets lost.
For Pickapocket I gave myself one calendar month: from an empty repository to an app people could already use.
I met the deadline because almost nothing had to be built twice. Code talks to the database through interfaces, so I can rewrite one part without touching the rest. Unit tests use generated mocks, while integration tests run against a PostgreSQL test database. Nothing merges until CI passes three checks: flutter analyze plus the Flutter tests, go test -race and govulncheck. Only a green build gets deployed.
I use AI tools and they make me faster. The bar for the code stays the same: every change has to pass the same three checks before it merges, and I take responsibility for every line.
Pickapocket and magento2-docker are public, and my730days is still in progress.
A budget tracker for families and couples. I wrote the backend, both mobile apps and the landing page, and set up the deployment.
Several people share one wallet and split expenses, and roles decide who can do what. The app works offline: data sits in an encrypted cache on the phone and syncs in the background. If two people change the same entry, the app resolves the conflict. Deleting an account removes all of that person's data. The app is available in English, Polish and Ukrainian.
A journal for parents whose child is being treated under the AIEOP-BFM protocol. Treatment takes about 730 days, hence the name.
The app has no network code at all, on purpose: it holds a child's medical data. Everything is stored on the phone in an encrypted database, with the key in the system keystore. Backups are encrypted separately, and opening the app takes a PIN or a fingerprint. Parents log blood counts, symptoms and fluid balance, follow growth charts and get medication reminders. There's a PDF report for the doctor and a separate screen for emergencies. I plan what to add next with an adviser from Ukraine's largest charity for children with cancer.
A Magento 2 development environment that starts with a single docker compose command and behaves like production. I've maintained it since 2019, and developers outside my teams use it.
Twelve services: Traefik with local TLS, Nginx, PHP-FPM 8.3 with a second Xdebug container beside it, Magento itself, MySQL 8, Redis 7, RabbitMQ, OpenSearch with Dashboards, Varnish 7 and Mailpit. Most of the work went into the things that quietly eat a day: killing the proxy loop between Varnish and Nginx, making it run properly on Apple Silicon and switching between plain PHP-FPM and the Xdebug container without a rebuild.
