PHP development

Not every project is a framework project. Some are a decade of PHP that runs the business and cannot be stopped for a rewrite; some are a small service where a framework would be more machinery than the task deserves. We work with both.

The starting point is always the same: make the code run in a way we can reason about. Get it under version control if it is not, get a copy running outside production, put the credentials in configuration instead of in the files, and add error tracking so failures reach us rather than the visitor.

From there the work is ordinary engineering — separating the business logic from the page that displays it, replacing string-built SQL with prepared statements, putting a test around the calculation that decides prices, and making the deployment repeatable.

Typical tasks:
— new features in an application that was written years ago and still earns money;
— integrations with external APIs, with timeouts, retries and logging;
— importers, exporters and reports over large tables;
— migration from PHP 7 to PHP 8 and from `mysql_*` to PDO;
— performance work: indexes, N+1 queries, caching where it actually helps.

We do not insist on rewriting a working system. Legacy code is ugly because it carries years of business rules that were never written down anywhere else — and those rules are the asset.