AI won't fix what bad engineering broke.

Preview text: AI won't fix what bad engineering broke. New insights, resources, and more! View this…

Monday, Jul 20, 2026 at 9:01 AM EasternMailchimp

Alan DeKokAI won't fix what bad engineering broke.

Image not available

No image available for this email.

Subject: AI won't fix what bad engineering broke.
Preview text: AI won't fix what bad engineering broke. New insights, resources, and more! View this…
From: alan.dekok@inkbridge.io
Brand: Alan DeKok
ESP: Mailchimp
Sent: Mon Jul 20, 2026, 9:01 AM ET
Sent to: inkbridge.io
Size: 197 KB
Images: 22
Links: 41, 9 of them buttons
Subject length: 40 characters

Against Alan DeKok's usual

Sent in its busiest hour, 9 AM, which holds 42% of its emails. The subject is 40 characters; its average is 52.

Email headers

What the brand's servers put on this email. Our receiving servers, the address we subscribed with and unsubscribe links are left out.

From: Alan DeKok <[email protected]>
Reply-To: Alan DeKok <[email protected]>
Subject: AI won't fix what bad engineering broke.
Date: Mon, 20 Jul 2026 13:01:42 +0000
Message-ID domain: mail166.suw14.mcdlv.net
Return-Path domain: mail166.suw14.mcdlv.net
DKIM signature: d=gmail.mcsv.net s=k2; d=inkbridge.io s=k3
Authentication: dkim=pass (gmail.mcsv.net), dkim=pass (inkbridge.io), spf=pass (mail166.suw14.mcdlv.net), dmarc=pass (inkbridge.io)
List-Unsubscribe: Present, one-click
Mailer: Mailchimp Mailer
Feedback-ID sender: mc

from mail166.suw14.mcdlv.net [198.2.183.166] by our receiving server with ESMTPS
from localhost [127.0.0.1] by mail166.suw14.mcdlv.net with ESMTP

Other sending headers (names only): X-Campaign, X-campaignid, X-Report-Abuse, X-MC-User, X-Accounttype

	Aug 13, 2026 8:30 AM	The hard part of convergence isn't the network. It never was.
	Aug 3, 2026 9:03 AM	They replaced the PAM modules. For a decade, nobody checked.
	Jul 30, 2026 1:15 PM	They didn't steal your credentials. They replaced your authentication stack.
	Jul 20, 2026 9:01 AM	AI won't fix what bad engineering broke. (this email)
	Jul 16, 2026 8:31 AM	They added AI to the network. The authentication layer fell over first.
	Jun 29, 2026 9:03 AM	He wiped the wrong database at 2am. What's your recovery plan?
	Jun 25, 2026 8:30 AM	They had two backup systems. Both had been failing for months.