Let's take a recent example (from [1]):
> Though no doubt correct, such statements tell the reader
> nothing. Useful writing makes claims that are as strong as
> they can be made without becoming false.
> For example, it's more useful to say that Pike's Peak is
> near the middle of Colorado than merely somewhere in
> Colorado. But if I say it's in the exact middle of
> Colorado, I've now gone too far, because it's a bit east
> of the middle.
This is deeply pedestrian writing you could be proud of if English was your second language and writing was not any sort of job but as written it reads like that boring father-in-law who collars you at a family picnic and insists on telling you (even though you know) about what a frequent flyer programme is and about that time 15 years ago when they hit silver status.It's a very unfair comparison, but if you want to read amazing technical writing, try reading "Everything and more: A compact history of Infinity" by David Foster Wallace. Or contrast PG's essay with Umberto Eco's "How to write a Thesis"[2].
It's hard to escape the conclusion that PG's writing would not survive a double-blind test where someone didn't see his name attached.
[1] http://www.paulgraham.com/useful.html
[2] It's a whole book but is excerpted here in a format that bears comparison to PG's essay https://thereader.mitpress.mit.edu/umberto-eco-how-to-write-...