For many of us, we spend our time heads down on projects trying to deliver solutions for a customers. That’s a Good Thing™, as far as I’m concerned. But every now and then, I think it’s also a Good Thing™ to take stock of where we – as a development community are – where we’re headed, and the things that we’re able to observe about ourselves. Now and again, I’ll write about my own opinions about WordPress (the software, the community, the economy, etc.). I don’t always have a direct point, though. Sometimes it’s just a smattering of thoughts about what I’ve seen. You know, like a digression. And that’s what this post has shaped up to be. A Digression on the State of WordPress There’s a constant discussion about the quality of the code that makes up WordPress core. This is bound to happen when you get opinionated people (read: developers) working with 10 year old software. 1. The Quality of Core For whatever it’s worth, I try to take a realistic stance on the quality of core’s source code: When it started out, WordPress started as a fork from an existing project. Developers contributed code in the best ways they knew at the time. The project grew, new paradigms entered the code, they
Share This