Contact

Get in touch

I read everything that arrives, and I reply to most of it. Response time is usually two to three days, occasionally longer if I am deep in a release.

Email: [email protected]

LinkedIn: linkedin.com/in/rbonweb

GitHub: github.com/rbonweb

What I would especially like to hear about

Corrections. This is the most valuable email you can send me. If a post is wrong, incomplete, or out of date because a version changed, tell me. Include the version you are on and what you observed. I will fix the post and note the correction, and I will credit you unless you would rather I did not.

Variants of a bug I wrote about. If you hit the same error message with a different root cause, that is exactly the material that makes an error autopsy more useful. Those ranked lists of causes grow because readers send in the ones I missed.

Post suggestions. Specifically: an error message that wasted a day of your life and has no decent writeup anywhere. Those are the best requests, because the absence of good material is the whole reason this blog exists.

Questions about something I published. If a post left you stuck, that is a gap in my writing and worth knowing about.

What I cannot help with

I want to be straightforward rather than leave you waiting on a reply that is not coming.

Free debugging of your codebase. I get a fair number of these. I genuinely wish I could, but I cannot review private repositories or debug production systems over email. If you are stuck, Stack Overflow with a minimal reproducible example will usually get you further faster.

Guest posts and link insertions. Debugly does not publish guest posts and does not sell links or sponsored placements. Please do not send the outreach template. If your product genuinely solved a debugging problem I write about, tell me the technical detail and I may well try it, but that is a conversation and not a transaction.

Content marketing partnerships. Same answer.

Work and consulting

I run Krova Cloud full time, so consulting availability is limited. I take on a very small number of engagements when the problem is genuinely interesting, mostly around production debugging, infrastructure isolation, and Shopify theme performance.

If that is why you are writing, include the problem, the stack, and the rough timeline in the first email. It saves us both a round trip.

Newsletter

One email a week when a new post goes out. No sequences, no upsells, no "just checking in" emails. Unsubscribe is one click and I do not follow up on it.

Privacy

Anything you send me stays between us. I do not add correspondents to the newsletter list, and I do not share or sell email addresses. Details are in the privacy policy.