• Great read, I feel related to this… you know some way :)

    We (team work) use now composer, autoloading, namespaces and it’s great, we have our plugin generator and project generator so we save time or at least we do not spend time for boring things anymore :)

    But this core thing is a huge concern to me. As you said “disconnect from core development” could be the price for a “better/faster/stronger” code.

    Who’s the culprit ? When you look into the core files you see choices. What’s the best way ? “low barrier to entry” or “Pure technical thing” ? I guess we cannot have it both ways, maybe something more like “half way”.

    If it’s about me I push my ambitions to the limit even if it seems already lost, but I’ve started to teach WordPress and I realized even very simple PHP code is difficult to understand for some students.

    So how you do this… pushing them forward because it’s always better, ok, I agree with you but kinda elitist what about the other 70% ? Not sayin I’m the truth, in fact it’s hard to choose but to note that we have to.

    • I think it’s telling how you put it — “teach WordPress”. :) Not PHP, not web development. WordPress.

      That’s perfectly fine. I touch on this in the post — not everyone has to become a developer. Just enough.

      We need to make it easy it for people who have aptitude for it so that we are heading towards that enough. Core isn’t doing it. Core development takes pride in making life hard for (would be) developers, for the sake of catering to users.

      I think the trick is to bend that spiky uneven learning curve into something more meaningful.

      I estimate that it takes between one and two years of people using WP loop to get what is happening in it. The flowchart I made for it is probably one of the most famous and appreciated WP things I’ve ever done. It breaks the wall between being a “user” of code and helps you move toward actually being a developer, with conscious understanding of that code.

      We need learning materials that accomplish that. More so we need code that accomplishes that and isn’t a black box clusterfuck.

  • Once you dig a little deeper there is a layer of class/object code in WordPress too. The nuance is — it is far from what would actually be considered object–oriented. […] In these circumstances the modern code can only happen in extension space.

    The Customizer actually has quite a bit of “modern” OOP code.

    • Hadn’t looked at that subsystem, so no opinion. Not a fan of customizer for myself. It’s user-centric (as usual), I am talking that more things need to be developer-centric and that core isn’t doing it. Somewhat case in point. :)

  • @rarst : As you said “uneven learning curve “, “not everyone has to become a developer”, that’s undeniable, could not agree more.

    Still, I cannot teach WP tricks without PHP. Is that a good thing that people with no basic PHP knowledge start with WP, I don’t know, I’m gonna go with “not at all”. But at the end of the day “the sake of catering to users” is quite the same thing.

Comments are closed.