CT No.237: Trust issues
Are attractive websites more likely to trick experienced content strategists?
newsletter-archive
CT No.236: Hold out your back, time to impress
The Content Technologist gets a brand new dress and (finally!) adds commenting on posts
CT No.234: How SEO ends
Don't ever tell anybody anything. If you do, you'll end up missing everybody.
CT No.76 [rerun]: Platform like a professional
How to choose a content business model and platform software
CT No.233: Adamantium skeleton
The storytelling tradition of SEO strategies and annual reports
CT No.232a: It's time to send the correct link.
In many email clients, that Spotify embed didn't work (although they work fine if you view in browser. But if you don't want to work even that hard, here are the playlists as boring regular links instead. * Best songs of 2024 * Christmas Goodies Have a lovely...
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