CT No. 188: Tell us what you want, what you really really want
What do you want to see in The Content Technologist?
newsletter-archive
CT No. 187: Now is the autumn of our diss content
Why we should consider the form and not the "content"
CT No.106: Audience feedback birthday edition
Complete the 2022 Content Technologist survey.
CT No.98: DAOs, Web3 and 14 bosses
10.14.21: Decentralized authority, a feature content tool review, questioning performance advertising and more.
CT No.97: Netflix good? Facebook bad? C'mon let's get nuanced
10.7.21: The last time I'll ever write about Facebook + the third and final installment of UX/UI reviews
CT No. 96: Does Peacock serve everyone Party Monster or is it just me?
9.30.21: Newsies, the Blues Brothers, ghost tv and a graphic design program for the current era.
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