
Engineering · July 16, 2026 · Gynvix · 1 min read
API errors people can handle
An error should name the field, the rule, and whether trying again makes sense.
Blog
Articles are published by Gynvix. Drafts stay in the database and are not listed here.
Loading articles…

Engineering · July 16, 2026 · Gynvix · 1 min read
An error should name the field, the rule, and whether trying again makes sense.

Delivery · June 15, 2026 · Gynvix · 1 min read
The first product decision is which records belong to an account, not which chart to draw.

Cloud · June 14, 2026 · Gynvix · 1 min read
A green badge is only useful if a red one stops the release and says why.

Cloud · June 13, 2026 · Gynvix · 1 min read
Development, review, and production should differ by data and secrets, not by surprise behavior.

Cloud · May 12, 2026 · Gynvix · 1 min read
An additive migration is easier to recover than a clever one that rewrites history.

Engineering · May 11, 2026 · Gynvix · 1 min read
The API process should own validation, authorization, and the database. The page should not.

Engineering · May 10, 2026 · Gynvix · 1 min read
Types help inside the program. They do not validate the JSON that just arrived.

Engineering · April 9, 2026 · Gynvix · 1 min read
Filters, search, and pagination belong in the query string so a view can be shared.

Engineering · April 8, 2026 · Gynvix · 1 min read
A server component can render the page. A client component should own only the interaction.