Shawn Dumas

Exciting Update for Adobe Commerce Merchants! Starting January 2026, Adobe Commerce will adopt a monthly patch release schedule to enhance security for all supported release lines. Here’s what you can expect: ✅ Monthly isolated security fixes for all supported versions ✅ Annual security patches every May (with possible additional patches in November) ✅ Full patch for Adobe Commerce 2.4.x LTS annually in May ✅ Beta patches twice per year (March & November) This change ensures a predictable, proactive, and simple approach to keeping your commerce platform secure and up to date. For more details, check out the official documentation: https://lnkd.in/gGHB_Zbm

5

Localization is more than translation. Pendo.io just rolled out our first localized experience—in Japanese 🇯🇵—designed for Japan’s fast-growing, AI-driven tech market. Go Pendo.io Japan ! From login screens to product areas, we’re bringing product-led growth to users in their language. Learn how we're doing it—and why Japan was first! 👇

2

I’m especially excited about this one. Starting today, agents can write directly to Figma files using the use_figma skill, with full awareness of your team’s design system. The infinite canvas has always been Figma’s magic - a space that’s a little messy, super collaborative, and perfect for turning early ideas into something real. Now agents get to show up in that same space, helping explore, iterate, and build. Proud of the team behind this, and excited to see what people craft with it! We'll keep improving it.

43

I wrote an article on how we translate user-generated content at scale at Mercari. It summarizes two years of work with various models, LLMs but not only, and how cost evolved, reducing it 100x over the period. I also go over non-AI features and user experience. https://lnkd.in/gbpQAQmX

39

2 Comments

Proud of our team and how hard we have been working to create an API that enables AI agents to make purchases. We are getting closer to making universal checkout a reality, focusing on security, performance, and scale. If you are curious about how we are tackling this problem, you can read our white paper here 👇🏾 rye.com/whitepaper

11

Developing a large ecosystem with both open- and closed-source components comes with some interesting challenges. Back when we were bootstrapping CKEditor, my purist mindset pushed us to develop each of our 30+ packages in separate repositories. The goal was to sort of "force" higher modularity and more responsible architecture for every component. As you can probably guess 😅, it did not scale. Later, we consolidated most of the packages into two monorepos – one open source, one closed source – while keeping a few granular packages separate where it still made sense. This helped a lot, but it didn’t fully solve the problem. We were still working across multiple repositories and kept running into issues like dependency coordination and lockfiles. Recently, we took another step forward. We migrated to pnpm and redesigned our overall approach. In this post, Filip Sobol explains the new setup implemented by the CKEditor 5 Platform team and what we learned along the way: https://lnkd.in/eHS28qxe

23

4 Comments

The data doesn't lie. 📈 The engagement spike we've seen over the last two weeks at Omniflow is proof that the "broken" way of building products, siloed docs/designs/code, is a pain point worth solving. By making the PRD a living, breathing part of the development loop, we're making product creation continuous. If you’re tired of "doc-rot," you need to see what we’re building. #Founders #ProductDesign #SoftwareEngineering #Omniflow

14

Great to read about my team's work on the AWS Developer Productivity blog! Tracking Amazon Q activity in Jellyfish lets you see the data in the context of other AI tools, metrics like cycle time, and helps you evaluate the tools you're using. https://lnkd.in/gXgRZvvs

21

2 Comments