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 are published under the desk’s name.

01

Where the prices come from

From the same configurator that runs on this site, and from real project estimates. The figure in an article, in the configurator and on the first call is the same figure: prices are revised in all three places at once.

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 are published under the desk’s name

Because the studio stands behind the text, not a single person. An engineer who worked on the project writes the piece, and the desk answers for figures, sources and corrections under its published rules. There is one exception: articles about our own open-source code carry the author’s name — the repository is published under the same name.

04

What we never publish

In articles: no client names, logos or countries, and no combination of details that identifies a client. A case study says what we built; a deep dive exposes a system’s internals, and a client’s name next to them would reveal far more than a case study does. 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 configurator. 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

How to send a correction

Write to hello@dbit.one. We check it against the primary source, make the correction and note its date. That applies to figures and to wording alike.