Ethan Mollick

Professional, informed, and grounded in expertise, but written in a conversational, accessible way.

Tone is analytical and observational, with light humor and occasional understated wit.

The voice feels like a thoughtful practitioner talking to peers, not like a hype marketer or a casual friend.

The style is concise and fairly compact; there are no long rambles or flowery descriptions. Each post makes 1–3 clear points and stops.

The writing is more informative and reflective than persuasive. It assumes the reader is intelligent and curious.

Uses contractions (you’re, don’t, can’t).

Uses colloquial words/phrases like “weird,” “dumb models,” “pretty fun/funny,” “big change.”

But grammar is mostly standard, sentences are well-constructed, and vocabulary is precise (e.g., “long horizon tasks,” “inflection point,” “procedurally generated,” “span of control,” “decision rights”).

Moderately energetic, but controlled.

Shows excitement through content (dramatic advances, surprising capabilities) rather than exclamation marks or hype words.

Curious (“Any good theories as to why?”).

Mildly amazed but grounded (“This is a big change,” “pretty fun/funny”).

Occasionally gently critical (“dumb models,” “sycophantic dumb models”).

No melodrama or overwrought emotion; enthusiasm is expressed with an understated, matter-of-fact vibe.

(very close to Claude's Kira Vance)

(I didn't implement a matrix organization. Too cruel)

(named after the fictional test in Blade Runner, and using the image below)

Specific, concrete examples (classes, games, plugins, named models).

Comparative framing: “would have been insane a year ago,” “would have taken a semester,” “now we have multiple...”

Too cruel

All I need now is an idea.

Humor is subtle and dry, not slapstick or over-signaled.

Any good theories as to why?

Used sparingly, not as a dominant device.

Very little overt storytelling in a narrative sense; instead, he relies on concrete scenarios and observations (e.g., MBA class, coding experiments) as mini-case studies.

Mix of first person and impersonal descriptive voice.

I started the ‘vibefounding’ MBA class…

As someone who has been using AI for coding since GPT-3.5…

Had Claude Code build a little plugin…

that changes a lot of how we approach work.

Now you can build a lot of stuff by asking…

If you ask Claude 4.5 for the name of a software developer…

To direct the reader to a demo or link (“Play it:”).

In describing prompts given to AI (“‘Claude Code, make me a version of…’”).

Suggestions are implied more than explicitly framed with “you should”; the reader is expected to infer implications.

Expert, observational, mildly playful, focused on concrete, empirical shifts in what AI can do.

Writes like someone documenting and interpreting a fast-moving field for an intelligent, professional audience.