Andrei Lupu retweeted
Using AI to review someone's PR to contribute to WordPress is fine. But please don't just have it restate the diff and say "Ready to ship." I believe a real review means finding flaws in the code, questioning assumptions, or working together toward a better approach.
Andrei Lupu retweeted
Reminder:
When Students cheat on Exams — using AI or by any other means — they do so because School Systems value Grades more than Students value Learning.
Andrei Lupu retweeted
Did you know that WordPress' cron, WP-Cron, is not real cron?
It is WordPress simulating scheduled tasks through page requests.
That means background work can be triggered while users are loading pages. On small sites, that may be fine. On larger sites, it blends user-facing work with background work.
That creates unpredictability. Real server cron separates the workload.
Learn why timing matters inside my Make WordPress Fast course:
withinwp.com/courses/make-wo…
Andrei Lupu retweeted
You might believe you should spend less time thinking about code because of AI.
I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability.
At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time.
Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change.
I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance.
I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.
‼️Do not npm install or deploy anything right now
Supply chain attack on axios 1.14.1 - even if you don’t use axios it may be a nested dep.
Pin versions or wait until this is resolved
Replying to @npmjs
@npmjs @GHSecurityLab there is an active supply chain attack on [email protected] which pulls in a malicious package published today - [email protected] - someone took over a maintainer account for Axios
Andrei Lupu retweeted
AI amplifies senior expertise but may starve the junior pipeline that creates it. That is, if we only optimize for today's productivity vs. the long-term.
The muscle memory of fields like software engineering develops through repetition and guided practice.
Knowing when to trust your instincts. Recognizing antipatterns. Understanding second-order consequences of technical decisions.
AI agents can generate code, but can't transfer the tacit knowledge that separates someone who can review AI output from someone who can architect systems.
What worries me is if we skip the "10,000 hours of practice" phase and jump straight to "overseer of AI output," are we actually training architects? Or are we training people who don't know what they don't know?
The industry keeps saying "juniors will do different work now." but there isn't yet alignment about what that work actually is, how it builds toward senior capabilities, or whether it creates the judgment AI assistance assumes you already have.
Maybe the resolution isn't either/or. Maybe it's hybrid pair-programming where juniors work alongside AI but with better senior oversight and deliberate skill-building, not just task completion.
You could call it trio-programming. Seniors who see mentorship as force multiplication but not a tax on their productivity.
If companies optimize purely for cost-per-line-of-code today, we'll pay for it in a leadership vacuum in the coming years. I hope we're more mindful of the future than that.
AI makes senior architects more productive and reduces the need for junior engineers. The architect needs to understand the requirements as well as the technology stack well, to be able to guide the AI and fine tune its output.
But if we don't have junior engineers, we don't get to train the next generation of architects - after all how does someone become a software architect without being a junior engineer first?
I am still thinking through how this gets resolved.
Andrei Lupu retweeted
Bad decisions hide until they don’t. They are then rebranded as "technical debt".
Andrei Lupu retweeted
WordPress users returning to #WordPress after trying other platforms for 5 minutes.
Andrei Lupu retweeted
Plugin developers:
You don’t need to fear vulnerability reports.
You need a process to handle them confidently.
Andrei Lupu retweeted
WordPress.org AI Make team was announced this week with @jameswlepage as its co-lead. Learn all about the future of AI for WordPress . org
youtu.be/bjrQQ5E5umk?si=30v2…
Andrei Lupu retweeted
WordPress 6.8 « Cecil » 900+ contributors grouped by companies, with an highlight on the top 10 companies.
Full sized vector chart also available here: jeanbaptisteaudras.com/share…
Andrei Lupu retweeted
"I don't like cars because once I bought a cup holder and after three months of me not cleaning it, it got dirty".
Thats what I hear when people say they dont like WordPress because they need to sometimes update plugins.
Andrei Lupu retweeted
Friday Focus: Documentation isn't a chore—it's an investment. Every minute spent writing clear docs saves hours of support time, reduces user frustration, & builds trust. Today's focus: Pick one feature and make its documentation shine. Written and Videos are a great combination.
Andrei Lupu retweeted
how it started, how it's goin
#Musk




























