
The counter that went blind after the restart
An idle process wiped 9 destillations from the history. The max() fix created the next defect: a new process increment vanished.
20 posts

An idle process wiped 9 destillations from the history. The max() fix created the next defect: a new process increment vanished.

I set a 4 KB ceiling per document and 15 per day. Two days later came the record: 113 files. What changed behavior was the meter, not the rule.

The portfolio suite had 599 green tests and four files that never exercised the code they claimed to cover. One called GET on a route that only exports POST. Another mocked the entire React module, making unreachable the exact case it was supposed to prove.

The Capivara test routine created real invites, and the invite endpoint really sent email. In five days, 410 messages went out to addresses that do not exist, 295 of them bounced. The sending domain is the same one that serves the store, the dog-walking app and the portfolio.

An audit guard demanded four provenance fields on every work plan. I ran it against the archive and found that 1 of 500 plans complied — 0.2%. The cause was not laziness from whoever wrote the plans: the rule existed only on a branch that was never merged. What changes when the rule lands in the contract with a ceiling proportional to plan size, and why adherence went from 0.2% to 15% in three days.

The terminal game was still announcing the old domain months after the migration. I wrote a guard for that class of bug and it started lying in three different ways: it ignored PDF, it could not read PDF text, and in CI it did not have the tool to open the file.

Recent evolution of the blog: accessibility WCAG AA improvements, tag corrections, and the 2-posts-per-day cycle. A journey of quality engineering and consistency.

Three holes closed in 48 hours in the same verification engine: a null key that in Node collapsed to zero and released any score at all, an inherited environment that made the same commit produce two different results, and a timeout that killed the parent process and left four children burning CPU for over an hour.

A hook meant to keep secrets out of the repository rejected, twice, a commit that carried no secret at all — first by confusing parsing with assignment, then by breaking under four layers of quoting. The lesson: a guard that cannot tell the difference is not protecting anything, it is teaching people how to bypass it.

Three suites broke on the same day in two different projects, all with the same timeout message — and none of them had a regression. The cause was a host load average of 81. What changes when a test's budget comes from observed latency instead of a number picked in a hurry.

A shell block on the last line of an already published post. The same defect sat in 18 posts, and none of my gates looked at the body of the article: one checked tags, another checked PT/EN pairs. I wrote the guard that was missing — and its first version accused 9 innocent posts.

A commit at 2:37 on a June morning made lint and tests non-blocking in the Portfolio CI, with a reasonable justification. One hundred and thirty-two days later, the repository had 14 lint errors and a broken test on master, and the pipeline was still green.

A health check that only looked at the HTTP status let truncated and empty responses through for days. The probe that came after measures the body, not the envelope.

For months I looked at the pipeline's green dot as if it were proof. The moment I removed the two lines that swallowed the test suite's exit code, the first honest run in the repo's history returned 8 failures out of 417 tests. The fix wasn't to hide them again: it was to give the debt an address, an owner, and an expiry date.

The tag pages shipped with no cover art at all, mixed Portuguese with English in the same listing, and threw anyone who switched language straight back to the home page. Three bugs that looked unrelated and came from the same place: the rule lived in the home page, not in the component.

Cover gate at build time, WCAG AA contrast, the 10th project in the schema, and a bug-hunter audit with zero violations. The story of how a blog stopped being just a blog and became a quality system.

Broken Pix BR Code, focus trap stealing keyboard input, scroll jumping sections — a deep audit fixed everything at once.

July 2026 was the month my portfolio stopped getting new features and started fixing the ones it already had. A deep audit revealed 10 problems — from Pix to focus trap — and by the end, deployment was more automated than ever.

How end-to-end tests transformed quality and confidence in Dogwalk's development — the real story of a stack that learned to test itself.

From zero tests to 853: how Playwright tests became the quality backbone of Dogwalk/PataPass, what we learned and what changed in the process.