>This article does not tell people to patch Apache. The >point, as for as I can tell, is to explore the projects you >use so you can learn to write better code.
You're right. But saying something like
"I’ve never taken a hard look at the Apache source code before, but I have found a few bugs in Apache that I’d love to have fixed."
is like launching a stick in front of a dog.
>The article gives good advice. I don't understand why you >would jump to the Dunning–Kruger effect to seemingly assume >that the readers are incapable of following the advice.
It's a book about php. Don't tell me about Composer, Symfony or other things that 0,1% of php coders are using. Php coders don't read, they cut'n'paste.
The article is about writing better code. My guess is that the PHP developers who do want to write better code would probably take the advice.
Is your point that nobody should ever suggest that PHP developers write better code?
People wo could write better code in php have already learned how to write better code in other languages. I don't even see the point of this book. Learning to write good code with php looks to me like learning ornithology with Angry Birds
You're right. But saying something like "I’ve never taken a hard look at the Apache source code before, but I have found a few bugs in Apache that I’d love to have fixed." is like launching a stick in front of a dog.
>The article gives good advice. I don't understand why you >would jump to the Dunning–Kruger effect to seemingly assume >that the readers are incapable of following the advice.
It's a book about php. Don't tell me about Composer, Symfony or other things that 0,1% of php coders are using. Php coders don't read, they cut'n'paste.