About & publishing standards

Tools with a method, not a promise.

Developer Workbench is a collection of six free utilities for inspecting text and comparing technical assumptions. The site is operated by Orr Yoffe. Software and explanatory material are developed with AI assistance.

What the workbench is for

Make a payload readable, convert a CSS scale, estimate a delivery bill or inspect declarations in an email or playlist. Examples explain the calculation and its limits. A result does not certify a system, replace a provider quote or prove a service will perform as expected.

How examples are checked

Examples use synthetic data rather than private production records. Arithmetic is checked against the stated formula, and interface changes are tested against known inputs. Software checks are not independent expert certification. Worked guides separate inputs, methods, assumptions and exclusions so you can reproduce results.

Content can contain mistakes. For production decisions, compare the result with your actual environment and the primary reference. The security section is educational response guidance, not a threat-detection service or an incident-response engagement.

Sources behind the methods

• MDN: JavaScript safe integers explains why valid JSON identifiers can be unsafe as a JavaScript Number.
• MDN: CSS values and units explains relative sizing and root-based rem units.
• RFC 2045 specifies MIME transfer encodings, including base64 and encoded line lengths.
• RFC 8216 defines HLS playlist attributes. A declaration is not a measured viewer session.

Privacy is specific to the data flow

Tools process entered text and numbers inside an isolated browser workspace without uploading those inputs. Normal page requests still reach the server. Optional analytics on developer tools requires consent; privacy signals can override it. The security section retains its separate no-third-party-script design. Read the privacy page for details and choices.

Corrections

A useful bug report includes the tool name, minimal synthetic input, expected output and observed result. Remove passwords, tokens, private addresses and customer data. Existing public JSON precision examples and the security response resource have GitHub comment threads for feedback on those resources. Sign-in may be required; comments are public. Do not use them for confidential incident reports.

Commercial boundaries

The tools are free to use. Advertising is not currently served. Synthetic prices explain calculations rather than endorse providers. Any future paid offer or sponsored placement must be clearly labelled. Technical recommendations should stand on their method, not on a commission or an approval badge.

Standards and examples updated 27 October 2026.