Jeremy DESVAUX (@jdmweb) header
Jeremy DESVAUX (@jdmweb) profile picture

Fractional CTO. I help companies structure, pilot, or produce their web projects. Certified Opquast and Green IT consultant. WordPress expert.

Montpellier, France
Joined February 2009
Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)Photo by Jeremy DESVAUX (@jdmweb)
Jeremy DESVAUX retweeted
I strongly believe that if you're using LLMs to generate code, it's super super super important that you (human) can still: → understand the logic → analyze/verify the logic → modify the logic Otherwise you're automating the creation of LLM-flavored black boxes that become impossible to maintain.
39
58
14
766
166,254
Jeremy DESVAUX retweeted
Hey there! So, if you have the new Slack experience and your #1 beef is that you can no longer see all your workspaces on the left… good news! It’s back! (Piping hot off the code grill; you might need to refresh to see it.) We’re sorry. But, we’re listening!
156
87
59
466
157,614
Spent the last 4 hours banging my head on the desk because my new meta controls weren't saving data... didn't hook the register_post_meta calls to anything, so it was trying to save invalid meta via the rest api. Sure would be great if there were some warning or notice.
1
1
5
356
⚛️ A question I get asked a lot: Q: How do you know if a calculation is expensive enough to justify memoization? A: Add a console.time('calculation') before and after the calculation. If the time adds up to more than 1ms, it might be a good candidate for memoization (useMemo).
8
31
309
35,171
Jeremy DESVAUX retweeted
Replying to @marcelpociot
Is there a recommended convention for managing Bun versions between projects and in CI yet? (e.g. nvm equivalent)
1
1
244
Lusion, pushing the web forward once again with their new website. Just incredible.
The wait is over! We're thrilled to announce the launch of our refreshed studio website. Check it out now! 🚀 lusion.co
1
12
1,498
Jeremy DESVAUX retweeted
WordPress 6.3 sort aujourd'hui ! Quelles nouveautés nous réserve cette nouvelle version ? 🔍 On vous les présente dans notre dernière vidéo ⬇️ youtube.com/watch?v=5P79Wg0J…
2
1
5
801
Did you know there's an overview of common APIs in use in WordPress and the WordPress.org ecosystem? You'll find it here: developer.wordpress.org/apis…
2
2
9
1,130
Hello, Pour un side project, je recherche des gens qui ont déjà ou veulent créer une entreprise / un produit / un nouveau service. J'aurai quelques questions toutes simples à poser, mais cela m'aiderait beaucoup. Merci d'avance 🫶🏻 Poke @Mans_lifestyles ☺️
1
2
1
455
Jeremy DESVAUX retweeted
The latter, like this wpengine.com/builders/page-c…
1
1
1
67
Does anyone have any update on php8.n compatibility for @WordPress core? The working doc says the same as always..
1
1
1
152
WonderWp 1.6.0 is out! Including improvements within 5 sub components (sanitizer, form, media, search, customposttype). For every detailed information about the changes : github.com/wonderwp/wonderwp… #WonderWp #WordPress #Framework #PHP
1
1
2
123
Jeremy DESVAUX retweeted
#WordPress 6.2 est dispo 🎉 Il apporte des évos majeures côté #webperf : - amélioration globale du TTFB sur les pages non en cache - TTFB et LCP à la baisse sur les pages construites avec Gutenberg - LCP en nette hausse sur les thèmes officiels TwentyXXX RT pour 1 web + rapide 😊
1
8
16
3,446
In the same way that we have witnessed the emergence of "mobile first" applications, I am pretty sure that we will see more and more applications, built in the form of APIs, intended for "chatbots first" use. Chatbots will be the frontend above your APIs.
1
2
1
393
My pro tip for reading the #WordPress Block Editor Handbook: Open it in @github Turn on Github's new "Code View" feature Expand the outline on the right Boom- you got yourself some decent, easy-to-read documentation. github.com/WordPress/gutenbe…
2
6
23
3,606
Jeremy DESVAUX retweeted
Two things a Pull Request description MUST have: 1. The changes you have decided to implement in the PR. It should be a simple summary of each file or a pattern of what you did with multiple files. 2. The business reason for it. Put simply the "why" for your PR.
3
7
35
5,615