OpenLampTech No. 185
Optimal MySQL/MariaDB monitoring | WordPress AI Team | MindsDB AI interface | Fundamentals in the age of AI | Scaling your database
Thank you for reading the OpenLampTech newsletter!
If someone awesome shared this newsletter with you and you are not yet subscribed, please use the Subscribe button below and join:
OpenLampTech has sponsorship opportunities for your brand, product, service, or job listing in the weekly newsletter.
As an independent publication, collaboration is very affordable.
All commentary on the below curated content is mine unless otherwise directly quoted.
long_query_time for Optimal Query Monitoring
This article shares insights about the differences in using performance_schema and slow_query_log for query monitoring in MySQL and MariaDB.
Where slow_query_log includes information (i.e., execution plans) on queries that run as prepared statements, performance_schema does not.
[Shattered Silicon]
Security Tip: Don't Generate Your Own Passwords!
It's usually best to use well-established policies, practices, functionality, procedures—whatever you label them.
Specifically, when it comes to password hashing and encryption.
Stephen Rees-Carter of Securing Laravel shares examples and tips on why “rolling your own crypto” is a bad idea.
[Securing Laravel / Stephen Rees-Carter]
Announcing the Formation of the WordPress AI Team
This is one area in which I feel WordPress is/was behind compared to Shopify (especially with the release of the new default Horizon theme and some of its AI features).
Nowadays, AI is table stakes instead of optional, like it or not.
Perhaps this is an opportunity for the WordPress space to thrive as an open-source software and community.
Even rebuilding some of the damaged bridges from the last several months.
Chat with Your Data: MindsDB Launches Open-Source AI Interface for Databases and Documents
I thought we were already doing this with SQL queries. 😜
No, in all seriousness, this seems to be the direction in which many technologies are headed.
The plus, in my opinion, is that SQL was already quite readable.
Integrating SQL with natural languages may offer users who are less familiar with SQL the opportunity to interact with the database.
[ktla.com]
LUC #88: How to Approach Scaling Your Database
The main points I took away from this article (many of which I hadn't considered) that I want to highlight.
When scaling, these complexities can be introduced into the system:
Additional development time is needed to implement new features
You're now working with/dealing with a more complex system
Testing code is more challenging
Inconsistencies, bugs, and fixing breakage become more challenging
[Level Up Coding]
The Hidden Cost of Skipping the Fundamentals in the Age of AI
As I use AI more and more in my current role, you may see similar articles shared here in OpenLampTech instead of only LAMP stack-focused content.
I have (good) success utilizing AI (as a tool), and my general thoughts about it are mostly the same.
I knew how to program before AI, and those fundamentals cannot be replaced by AI.
This quote from the source article rings true:
“Working solutions created with limited understanding are often fragile, difficult to extend, and hard to maintain.”
[Coding Is My Craft]
WooCommerce and WordPress news and updates
WooCommerce 9.9 Release is Delayed (June 2nd, 2025)
Thank you for reading OpenLampTech. I hope you have a great rest of your week.
Take care.
Josh Otwell
Some links may be affiliate links from which I earn a small commission at no additional cost.