Is this blog written by AI?

· Source: Marc Brooker's Blog · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering · Depth: Intermediate, quick

Summary

The author clarifies their policy on AI usage for content creation, stating that no human-readable text on their blog or in their professional life is AI-generated. They emphasize a "social contract" with readers, valuing deep understanding and ownership of their writing. While they extensively use AI agents for brainstorming, research, summarizing, and data analysis, they discourage generating full documents with LLMs if the reader will simply summarize them. Conversely, the author expresses 100% comfort with AI-generated code, noting that almost all code on their blog in the last two years is AI-generated and often "vibe-coded slop." They now believe code's primary purpose is not sharing ideas between people. Although LLMs are used for editing and critiquing writing, this practice is being reduced due to concerns about fostering a "super defensive" writing style that impedes clear communication.

Key takeaway

For a Director of AI/ML shaping content policies, recognize the distinct implications of AI for human-facing text versus code. While you might encourage AI for code generation to boost efficiency, consider limiting its use for public-facing written content to maintain reader trust and authenticity. Evaluate your team's LLM editing practices to prevent a "defensive writing" style that could obscure clear communication.

Key insights

The author distinguishes between AI's role in human-facing text (no) and code (yes), prioritizing human connection in writing.

Principles

In practice

Topics

Best for: Machine Learning Engineer, AI Engineer, Director of AI/ML, AI Ethicist

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Marc Brooker's Blog.