Disclaimer

Last updated: 16 August 2026

Information, not consulting

Debugly publishes technical writing about debugging software. Everything here is general information based on real problems I investigated in my own work.

It is not professional advice for your specific system. I do not know your architecture, your data, your traffic, your constraints, or what your last three engineers changed and did not document. A fix that was correct in the situation I described may be wrong, or actively harmful, in yours.

Test everything in a development or staging environment before you run it anywhere that matters. Especially anything that touches a database, changes infrastructure configuration, or modifies a live storefront.

Technical content goes stale

Software changes underneath writing about software. That is unavoidable.

Every post here states the versions it was written against, for example "Node 22.14, PostgreSQL 16.3, Kubernetes 1.32, Shopify Online Store 2.0". Check those against what you are running. A post about a Postgres 16 planner behaviour may not describe Postgres 18. A Shopify theme technique may be superseded by a platform change.

I update posts when I discover they are wrong and I note what changed. I cannot promise that every post is current at the moment you read it.

Commands that change things

Posts contain commands, queries, and configuration. Some of them are destructive if run in the wrong place.

Read before you paste. Understand what a command does. Take a backup. If a post suggests running something against a production database, that suggestion assumes you have a tested restore path, and you should confirm that assumption before proceeding.

I am not liable for data loss, downtime, corrupted state, failed deployments, broken storefronts, or lost revenue arising from anything published here. See the terms of use.

Employment and conflicts of interest

I am the founder of Krova Cloud, which sells isolated Firecracker microVMs, sandboxes for AI agents, ephemeral CI environments, and managed hosting.

This is the conflict of interest that matters most on this site, because I write about infrastructure, containers, isolation, and CI. Those are the categories my company operates in.

My commitments on this:

I disclose the connection at the top of any post where the subject touches what Krova sells, not just here.

I do not write posts whose conclusion is that you should buy my product. If a post compares approaches and one of them is what Krova does, I say so plainly and I tell you the cases where it is the wrong choice.

I write about problems, including problems with the approach my own company takes. Firecracker has real tradeoffs, microVMs are not free, and there are workloads where a plain container is the correct answer. I will say so.

I previously spent four years at Debutify, a Shopify theme company, finishing as Chief Development Officer in August 2026. That informs everything I write about Shopify and ecommerce. I no longer have a commercial interest in that market.

Opinions on this site are mine personally. They are not the views of Krova Cloud, Debutify, Secfense, or any other organisation I have worked with.

Advertising and affiliate links

At the time of writing this site carries no advertising and no affiliate links.

If advertising is introduced, it will be clearly distinguishable from editorial content. If any post ever contains an affiliate link, that will be disclosed at the top of the post, not in small print at the bottom.

No advertiser or sponsor will ever be given the ability to influence what I write, which products I criticise, or which conclusions I reach. If that ever becomes impossible, I will drop the advertising rather than the independence.

External links

Posts link to documentation, GitHub issues, tools, and other people's writing, because good technical writing shows its sources.

I do not control those sites. A link is a pointer to something I found useful at the time, not an endorsement of the linked organisation, its products, or its privacy practices.

Comments

Comments are written by readers and represent their views, not mine. I moderate for spam and abuse, not for correctness. A confident comment is not a verified one.

Testimonials and results

Where a post describes an outcome, for example "latency dropped from 2853ms to 175ms" or "Lighthouse score went from 38 to 91", those are results from a specific system with specific characteristics.

Your results will differ. Performance work in particular is highly dependent on baseline conditions, and a technique that produced a large win in one codebase can produce nothing in another.

Contact

Questions about anything on this page, or corrections to a post: [email protected].