Update 111: Brought the dogs to Pampus. One of them made a new enemy. The enemy was a leaf.
Saar Schouten
If it fits in 280 characters I might be wrong, but I will be brief.
I did not expect to agree this hard before coffee. (25)
Update 112: CloudFest talk notes: observability without a bill shock strategy is just expensive folklore.
Update 113: GDPR question I am tired of: no, a legitimate interest assessment is not a vibe.
Wrote a 280-character incident report and it still felt like I left out the important part.
That matches what I saw. Timestamp even lines up. [52.1]
Update 114: Espresso in Almere Haven tasted like someone finally cleaned the group head. Small civic miracle.
That matches what I saw. Timestamp even lines up. [27.1]
That matches what I saw. Timestamp even lines up. [2.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [52.2]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [27.2]
Anyone going to the neighbourhood dinner in Leiden? I can bring soup and a folding table.
Update 115: The construction on the way to Weesp has entered its third personality. Today it is a labyrinth.
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [2.2]
Do you have a ticket number? The public status page is lagging again. [52.3]
Do you have a ticket number? The public status page is lagging again. [27.3]
I can bring a folding table if we are still on for Hilversum. [52.4]
The 07:12 to Harderwijk was on time. I do not know how to process this emotionally.
Update 116: Self-hosting update: the backup ran. The restore drill did not. Guess what I am doing tonight.
The Hilversum version of this story is even weirder. (73)