ckdot

In the last years, PHP has been refactored in a lot of places. It‘s way faster and cleaner now. There are still some quirks, like the inconsistent function naming. But - like the article says - your IDE is helping. Also, PHP has a great doc. Just open php.net/{{function name}}. You can write really clean code at enterprise level in PHP now. PHP is not just WordPress. Still a lot of PHP developers don’t tend to write clean code. It’s often a mess even if the language would not prevent them to write clean, S.O.L.I.D. and performant code. I don’t know if this is the case for other programming languages, too, or if Bad code is just more often tolerated in the PHP world.

In theory that’s right what you say.

But still, tasks should be small enough that it hopefully won’t hurt too much if you throw away all the code again.

Too often I experience that - even if you talk to low/mid level devs about a feature before, even if you make a task breakdown together with them and write all the software design decisions down, even if you tell them they should commit often to you can check once in a while, even then in the end it‘s too often garbage what has been produced. Still, companies want to keep these developers because it’s hard to find new ones. And I guess it’s our senior’s duty - even if there are many disappointments - to still assume the best and try to teach them to do better. Again and again and again.