Things we find out building real systems, written for people who have to choose one. No theory: problems we hit, and how they got solved.
On 21 October two critical flaws in the PHP core went public. The fix for our servers landed late that evening, carrying the same version number as before. What we did while we waited, and how we checked.
Read
All our sites go through Cloudflare, and our servers take web traffic from nobody else. How we use it, the cache rule that got us into trouble, and why one domain moved to the Pro plan.
Read
For years we have built the entry platform and digital race office for the Tre Golfi Sailing Week and C.R.V. Italia. What goes on behind a regatta, from the entry form to the crew app.
Read
More and more searches go through ChatGPT, Claude or Perplexity, and they cite only a handful of sources. What we changed on our own site to be one of them.
Read
AI assistants cite pages that answer straight away, with clear facts and a source. The rules we follow when we write for ourselves and for clients.
Read
One night in July, four administrators nobody had created appeared on a WordPress site on one of our servers. How we dealt with it, and why we checked the whole server.
Read
For three months the hourly backups on one of our servers failed 7,162 times while the log kept saying OK. What broke, how we rebuilt it, and the check we now never skip.
Read
We wrote our own security scanner for our servers. At midnight it runs 67 checks, emails a report and, if it finds something critical, acts without waiting for morning.
ReadOperations that write to invoices, stock or accounts never run blind. The rule is simple and has saved more projects than any technical choice.
ReadA question almost nobody asks before signing, and the only one that matters three years later. What to look for in a software development contract.
ReadThe wall every web app hits when it has to talk to hardware on site. The answer is not a VPN, and it is far simpler than it looks.
ReadThe comparison is almost always made on the monthly fee, which is the quickest way to get it wrong. The three items that actually decide it only become visible after year three.
ReadTell us what isn't working. The first meeting is to see whether it's worth doing anything, and if the answer is no, we'll tell you straight away.
Or call us: 351 240 7196 · [email protected]
We would like to know how many people read these pages, and which ones. The data is anonymous and only helps us write better. If you would rather not, the site works exactly the same.
