By July 2023, I will be retired from reviews.
There are a lot of reasons why, but none matter for the purpose of this post.
I’ve already written up and scheduled some posts about my time there, and things I’ve seen. One about when I realized the atmosphere in developers had made a serious shift (it involves plugin theft, NDAs, GPL, and impersonation), as well as why I hate most security plugins.
But my problem is that I have a lot of plugin stories to tell.
What kind of stories do you want to hear? What things have you always wondered about?
While I will not name names except in cases where the story happened in public. In my first post (July 5) I’ll explain why in a little more detail about why I don’t name, so don’t ask for that. Besides, if I name and shame, they’ll come after me and I’m too tired for that shit.
I’m weeding through my notes (yes, I have them for self protection) of stories that can be sanitized and retold, but not all can.
Do people want to hear about common mistakes? Do they just want to see someone losing their blob (that’s most of them)? The ones I think most people would want to hear is thinks like the guy who stole a plugin from the contractor he hired.
So. Comments are open. Do the thing. But be nice.
Comments
8 responses to “Plugin Stories: What Do You Want to Hear?”
As two of my plugins are in the security plugin genre, l’d love to hear why you hate them.
Oh I will 🙂
I find almost everything you post interesting, so I suppose I mostly hope to hear what you think is most interesting and useful to share with the community (or whatever you want, it’s you’re blog!).
That said, I’d really love to hear what you think about the future of WordPress and plugins from your unique vantage. Where are the biggest areas of growth for plugins? What is it that helps some plugins become so popular and others not? What are the 10 plugins you’d build given unlimited time and resources?
Those are great questions!
Now I’m sad ( that I cant think of great questions )
If it helps, I don’t hate any security plugins in specific. 🙂
For me, the most fascinating aspects of plugins are unanticipated problems at scale, seemingly harmless approaches to a problem that expose bizarre edge cases (both in Core or specific environments/implementations), etc.
“Hey this plugin changed this one line of code, and it exposed a 15 year old bug” type stuff.
I’ll have to dig through some old notes for that. I have vague memories of a couple times, but usually it went the other way. “Hey, Core changed this function and it broke WooCommerce.” I know there was one with EDD in specific that was wrong and dangerous, and they self-reported to core.