Laravel and JS frameworks are way ahead by being developer focused and fully documented with established best practices for a broad set of web primitives.
WordPress needs to reconsider the current focus on the editor or risk becoming invisible to the next generation of builders.
While CMSs obsess over better WYSIWYGs, AI is skipping ahead by generating raw code directly.
Assembling WordPress blocks with AI feels like a dead-end. The real unlock? Better PHP/JS APIs + clear patterns so that AI can build real products on WP.
Cursor is like the new hire — enthusiastic and way faster than everyone who has been around for a while (VS Code with Copilot).
I had the same project open in both and was checking who would fix an issue with ffmpeg integration in a Swift app first. Eventually, I fixed it manually (is that how we call coding by humans now?) with an answer from StackOverflow 🤷
Just got roasted by an AI 🔥 about my strategy on socials:
> You’re creating technically dense content for an audience that doesn’t want to be lectured or debug with you unless there’s something emotionally or practically in it for them.
Fair. Brutal. True.
Does this resonate with you? What are some tactics that have worked well for you?
Are you getting "SPF alignment issues" or "spf=neutral" for emails sent by WP?
Turns out that wp_mail() doesn't set the Return-Path email header which leads to PHPMailer populating that from the php.ini sendmail_from setting. While that is correct, email clients these days expect the FROM domain, Return-Path and DKIM p= domain to be equal to pass the DMARC checks.
Here is a crazy idea — use JSON with actual JS for config files. So many JS and PHP projects seem to embrace it now over plain JSON or YAML files.
Was listening to this interview with Sam Goodwin on devtoolsFM podcast about Alchemy and realized how cool it is to have actual programming language features for configs.
Native <video> in HTML is extremely good these days. Videos encoded with H264/AAC are universally playable and with HTTP chunk support you can serve the same video to all users.
However, browsers seem to request videos with preload=auto/metadata as soon as the page loads which is unnecessary. So I built this lazy-load solution that hides the src attribute (prevents loading) until an Intersection Observer callback.