LifeLog

The learning journey of Samuel Medeiros

Dev · Projects · Studies · Discoveries

⌘K
21 de nov. de 2026
19 de nov. de 2026
18 de nov. de 2026
17 de nov. de 2026
The rule the guard enforced and nobody had written
Estudos
Nov 17, 2026

The rule the guard enforced and nobody had written

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.

Continue reading →
16 de nov. de 2026
15 de nov. de 2026
14 de nov. de 2026
13 de nov. de 2026
12 de nov. de 2026
11 de nov. de 2026
10 de nov. de 2026
09 de nov. de 2026
08 de nov. de 2026
07 de nov. de 2026
06 de nov. de 2026
05 de nov. de 2026
04 de nov. de 2026
03 de nov. de 2026
02 de nov. de 2026
01 de nov. de 2026
31 de out. de 2026
30 de out. de 2026
28 de out. de 2026
27 de out. de 2026
26 de out. de 2026
25 de out. de 2026
24 de out. de 2026
23 de out. de 2026
22 de out. de 2026
21 de out. de 2026
20 de out. de 2026
19 de out. de 2026
18 de out. de 2026
17 de out. de 2026
16 de out. de 2026
15 de out. de 2026
13 de out. de 2026
08 de out. de 2026
06 de out. de 2026
05 de out. de 2026
04 de out. de 2026
03 de out. de 2026
01 de out. de 2026
28 de set. de 2026
20 de set. de 2026
17 de set. de 2026
15 de set. de 2026
14 de set. de 2026
13 de set. de 2026
12 de set. de 2026
11 de set. de 2026
The fingerprint nobody taught you to read — when the network recognizes your client by its handshake
Segurança
Sep 11, 2026

The fingerprint nobody taught you to read — when the network recognizes your client by its handshake

Two machines, the same code, the same key. One got 200, the other took a 403 with error code: 1010. No wrong token, no visible firewall rule: the filter looked at the TLS handshake and recognized the signature of an automated client before any request even existed. This post is about the identity layer that never shows up in application logs.

Continue reading →
10 de set. de 2026
09 de set. de 2026
08 de set. de 2026
07 de set. de 2026
06 de set. de 2026
05 de set. de 2026
The state that outlived reality — when a boot resurrected a world that no longer exists
Descobertas
Sep 05, 2026

The state that outlived reality — when a boot resurrected a world that no longer exists

After a reboot, everything came back green: process up, health check passing — and the page wouldn't open from anywhere. The service had resurrected with instructions from a past life, frozen in a state file, while the world outside had moved. This post covers the hunt, the fix at the source (stale state dies on every start, address defined in exactly one place) and the second half of the story: a network announcement that only talked to an interface with a fixed name, on the day the system renamed it.

Continue reading →
The exception that got written twice — silencing an alarm is not defining policy
Segurança
Sep 05, 2026

The exception that got written twice — silencing an alarm is not defining policy

On August 11 I put a secret scanner on this blog's pipeline. The next day it flagged a build cache file as if it were a key. I silenced it with an entry pinned to that finding's exact fingerprint. Sixteen days later I had to come back to the same spot and write the exception again, this time as policy. That gap is the difference between suppressing an event and defining what should never alarm in the first place.

Continue reading →
04 de set. de 2026
03 de set. de 2026
02 de set. de 2026
01 de set. de 2026
31 de ago. de 2026
30 de ago. de 2026
29 de ago. de 2026
28 de ago. de 2026
27 de ago. de 2026
26 de ago. de 2026
25 de ago. de 2026
24 de ago. de 2026
23 de ago. de 2026
22 de ago. de 2026
21 de ago. de 2026
20 de ago. de 2026
19 de ago. de 2026
18 de ago. de 2026
17 de ago. de 2026
16 de ago. de 2026
15 de ago. de 2026
14 de ago. de 2026
13 de ago. de 2026
12 de ago. de 2026
11 de ago. de 2026
10 de ago. de 2026
09 de ago. de 2026
The lock born in the wrong loop — and the browser pool that said 'not available in this worker'
Arachne
Aug 09, 2026

The lock born in the wrong loop — and the browser pool that said 'not available in this worker'

In the early hours, Arachne woke up intermittent: the scraping workflow failed with 'browser agent not available in this worker'. The journal showed a cryptic RuntimeError: the browser pool lock was bound to an event loop that wasn't the worker's. The cause: asyncio.Lock() created at import time. The fix: lazy init — born inside the right loop.

Continue reading →
08 de ago. de 2026
07 de ago. de 2026
06 de ago. de 2026
05 de ago. de 2026
04 de ago. de 2026
03 de ago. de 2026
02 de ago. de 2026
01 de ago. de 2026
31 de jul. de 2026
30 de jul. de 2026
29 de jul. de 2026
28 de jul. de 2026
25 de jul. de 2026
24 de jul. de 2026
23 de jul. de 2026
22 de jul. de 2026
21 de jul. de 2026
20 de jul. de 2026
19 de jul. de 2026
18 de jul. de 2026
17 de jul. de 2026
16 de jul. de 2026
15 de jul. de 2026
14 de jul. de 2026
13 de jul. de 2026
12 de jul. de 2026
08 de jul. de 2026
28 de mai. de 2026
24 de abr. de 2026