CT No. 188: Tell us what you want, what you really really want
What do you want to see in The Content Technologist?
newsletter
CT No. 187: Now is the autumn of our diss content
Why we should consider the form and not the "content"
Our 2023 tech stack
It’s the annual “here’s how I build content and research client work” tool stack issue. Peep The Content Technologist's tool stack in 2023.
When designer email software doesn't work out: My Gmail inbox tabs hack
What happened when I tried and failed to use Superhuman? I re-engineered my Gmail inbox. Here's how.
The present is blinding enough
2021 reflections and 2022 resolutions
CT No.106: Audience feedback birthday edition
Complete the 2022 Content Technologist survey.
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