The Two Sides in the Record
The value of first-person long-form pieces like this is that they don't cherry-pick the conclusion. The author shows the model's excellent parts: its quick absorption of the problem's background, and a few investigative angles a person hadn't thought of; and they preserve the crash scene as-is—an extremely believable fabricated technical detail that was almost taken at face value, revealed as pure fiction only after checking the docs. A mind-reading genius and a straight-faced bullshitter live in the same model—that's the truest portrait of today's high-end models.
What You Can Learn from a Single Case
Posts like this appear on HN every few days, so why are they still worth reading? Because launch events and benchmark leaderboards won't tell you "what a crash looks like," and recognizing a crash is precisely the core skill in using these tools well. From this and similar records, you can distill a fairly solid discipline: go ahead and generously adopt the angles the model offers, but for any factual assertion you'll make a decision on, always go back to the original source and verify it.
via: Hacker News