A few of these points are right, but a lot of it is so far lost from the reality of LLMs that it isn't even wrong. Yes: structure beats vibes. Primacy/recency

A few of these points are right, but a lot of it is so far lost from the reality of LLMs that it isn't even wrong. Yes: structure beats vibes. Primacy/recency bias is real. Treating prompts as engineering artifacts is empirically helpful. But: - “Reads all tokens at once.” Not quite. Decoder LLMs do a parallel prefill over the prompt, then sequential token-by-token decode with causal masks. That nuance is why primacy/recency and KV-cache behavior matter, and why instruction position can swing results. - Embeddings & “labels.” Embeddings are learned via self-supervised next-token prediction, not from a labeled thesaurus. “Feline ≈ cat” emerges statistically, not by annotation. - "Structure >> content". Content is what actually matters. “Well-scaffolded wrong spec” will give you confidently wrong output. - Personas are mostly style. Yes, users like words typed in their style better, but it'll actually hide certain information that a "senior software engineer" might not know. I don't really get the Big-O analogy thing, either. Models are constantly exposing and shifting how they direct attention, which is exactly the opposite of the durably true nature of algorithmic complexity. Memorizing how current models like their system prompts written is hardly the same thing.