DEV.ITISYOU
A place to diagnose an engineering problem by running tests, rather than by guessing from an answer that worked for somebody else in 2019.
Working and public. Playbooks can be read and searched without an account, and coverage is still being built out.
Last verified
What makes it different
Evidence is attached to a specific revision and a specific environment. Editing a playbook creates a new revision, and the old evidence stays with the text it actually tested instead of silently transferring.
Who it is for
- Engineers debugging a specific error on a specific version
- Teams who need to know whether a fix applies to their environment
- Anyone who has followed a highly upvoted answer that no longer works
What it does today
Each of these is tied to the evidence at the foot of this page, checked on the date shown above.
Diagnosis as a path, not a list of answers
Paste an error, stack trace or log and follow one diagnostic test at a time. You report what you actually observed — including that you could not tell — and the path branches on your answer instead of assuming it.
Confidence you can inspect
There is no "verified" tick. Confidence comes from reproduction records and always shows the counts behind it, so a fix backed by three reports cannot look like a fix backed by three hundred.
Failures are kept, not buried
A fix that failed on a particular version is recorded as exactly that, rather than disappearing into a downvote. Disagreement is segmented by environment, because two engineers on different versions can both be right.
Readable without an account
Reading and searching never require signing in. The published list of things the site will not do includes asking you to sign in to read, ranking by reputation points, and hiding a fix that stopped working.
What it does not do
The unfinished parts, stated here rather than discovered later.
- Coverage is narrow on purpose. The areas with real depth today are Cloudflare Workers, Cloudflare D1, PostgreSQL, Docker, Kubernetes and Node.js. Outside those, you may find nothing.
- It will not run code for you or from you, which rules out the automatic reproduction some engineers would want.
- AI does not get to decide that a fix works. That keeps the evidence honest and makes the library slower to grow.
- Advertising is planned but not active, so the running costs are currently unfunded.
How it is paid for
Free — limited advertising planned, not active
Free to read and search, with no account required. Limited advertising is planned to cover running costs. No advertising is running today and no advertising code is installed.
Similar category, different approach
Stack Overflow and GitHub Discussions are where this kind of knowledge usually lives, and both are vastly larger. The category difference is what happens to an answer over time. A question-and-answer thread records what worked once; a playbook is built to record which versions a fix was tested on, who reproduced it, when it last worked, and what happened when it stopped. This is a comment on information structure, not on quality, and there is no affiliation with either company.
All third-party names and trademarks belong to their respective owners. They are shown solely for category comparison. ITISYOU is independent and is not affiliated with or endorsed by these companies.
Evidence
Sources for this page
Returns HTTP 200. Playbooks are readable and searchable without signing in. Publishes its own about, verification, privacy, terms, contribution terms, content policy, acceptable use and AI pages. No advertising is present on the page.
Checked 26 August 2026