I didnât publish last Monday, and the blame goes to personal commitments and a beautiful six-month-old baby who has zero respect for editorial calendars. While Iâm confessing things, in 2027 Iâll probably publish once a month, maybe once every two months, so tell me in the comments which rhythm youâd prefer.
Now, Friday the 13th. Microsoftâs global outage began on Thursday the 12th and kept Outlook, Teams and Copilot down for more than twelve hours, long enough for two days of procedural deadlines to be frozen at Brazilâs Supreme Court. The companyâs explanation pointed to server problems, with no malicious activity that it knew of. On Friday, in a separate episode, American planes spent more than four hours stuck on the ground because a communication failure in air traffic control led the FAA to hold departures nationwide.
Everybody already wrote the âwe depend too much on technologyâ column, so let me ask something more uncomfortable: how much control do we really have over our data when access to it depends on systems we canât replace when they fail? Yeah I know the answrâŠ
Picture an analyst with a deadline at 5 p.m. and a dead inbox, who forwards the contract to a personal Gmail, sends the client spreadsheet through a personal WhatsApp account and promises to delete everything later, which never happens. Nobody was hacked, nobody had bad intentions, and still the data left the building through a door that no policy, audit or DPO ever mapped.
That is why I say the plan B of an operation is part of its privacy policy. If your continuity plan is âpeople will figure it outâ, then people will figure it out with whatever is in their pocket, and your carefully documented controls will last exactly as long as the vendorâs uptime.
I confess that after that Friday I seriously thought about planting potatoes and raising chickens. It wouldnât solve anything, I know, but thereâs some comfort in imagining a routine where the potatoes grow without a status page and at least the chicken coop works without a login.



