dbit.one© 2026
000
booting_
Loading experience0%
dbit.one
dbit.one engineering desk

How we write

The editorial rules behind the dbit.one blog: where the numbers come from, what we verify before publishing, and why articles carry no personal byline.

01

Where the prices come from

From the same calculator that runs on this site, and from real project estimates. If a figure in an article disagrees with the calculator, the article is wrong and we will fix it: a discrepancy reads as dishonesty and costs more trust than a rounder headline number is worth.

02

What we verify before publishing

Every numeric claim, against a primary source or our own measurement. Measurements are described so they can be repeated: tool, conditions, date. Sources are listed at the end of the article, not left “somewhere on the internet”.

03

Why articles carry no byline

For the same reason there are no client logos on this site. Nearly every project runs under an NDA, and some are white-label. An engineer’s byline on a payment-core deep dive points at the client as clearly as a logo would, and the combination of author, technology and industry can be resolved in one evening. We chose to stand behind the text with rules rather than names. There is one exception: articles about our own open-source code carry the author’s name — there is no client behind them, nothing to give away, and the author is checkable because the repository is published under the same name.

04

What we never publish

Client names, their logos, their countries, or any combination of details that identifies them. No exports from anyone’s production database, no screenshots of anyone’s system. Numbers in examples are illustrative: they show the class of system, not someone’s real reporting.

05

How we update articles

Prices and timelines are revised together with the calculator. Updated articles get a new “updated” date — but only when the meaning changed, not for a typo. Stamping today’s date on every page destroys the signal for readers and search engines alike.

06

Found an error

Write to [email protected] — we will correct it and note the date of the correction. That applies to figures and to wording alike: text that cannot be corrected should not be published.