CT No. 217: Digital performance data that's rooted in reality
Everyone else's numbers are inflated, but your own data is your gold. Learn to trust your owned data and make decisions with verifiable performance metrics.
newsletter-archive
CT No.216: Perplexity perplexes + solstice soothes
Should I let Perplexity index and cite my website content?
CT No.215: Content engagement benchmarks for a sophisticated flex
Content performance measurement is within your team's reach
CT No.214: A fresh coat of paint
Check out our new homepage!
CT No.213: You say tamater, I say tomato
Hello, and welcome, new subscribers! It's time to talk style, a phase of The Content Technologist approach that addresses the many dimensions of finesse we can apply to content. To minimize word count, this issue focuses on the textual elements of brand and content style, but one day...
CT No.212: Should you panic about Google search?
No. Don't get stressed about Google. Ever.
CT No.242: What's your vector, Victor?
How to understand tokens and vector embeddings, for word people.
CT No.241: TF? ID(GA)F: The old faithfuls of language processing
Even in the face of "black box" algorithms, the history of artificial intelligence—natural language processing, more specifically—has left plenty of clues. While we can't understand the full equation, we can see how building blocks create common patterns in how current algorithms process language.
CT No.240: Mad inconvenient infrastructure
Infrastructure, no matter how solid or planned or continuously improved, gets messy. Observing humanity in July feels like the ultimate UX research experiment.
CT No.239: Please automate the tedious part for me
July is prime chart-making season. July 2025 is one more chartmaking season that will not be powered by artificial intelligence, and here's why.
Processing your application...
Please check your inbox and click the link to confirm your subscription.
There was an error sending the email