Cosmic Bento — AI-Driven Intelligence Modules | UIUX 🚀 dribbble.com/shots/27459253-… Work with us airzon.agency/ #BentoUI #DashboardGrid #AISaaS #DataAnalytics #SEOIntelligence #DarkModeDesign #ProductInterface #UIUXDesign

🚁 Sleek design meets sky-high innovation—explore how drone tech could look Tesla‑style in 3D. This concept reimagines Tesla’s aesthetic for a futuristic drone interface with clean 3D visuals, intuitive controls, and responsive layouts. What do you think of this concept? By Angel Villanueva for Orizon🚀 #UIDesign #UXDesign #UIUX #ProductInterface #TechConcept #UI #UX #Drone #Tesla #OrizonDesign

Using Object Manager in Magento code is still a pattern I see way too often in custom Magento modules. Let's fix it. ❌ BAD: ``` $productRepository = \Magento\Framework\App\ObjectManager::getInstance() ->get(\Magento\Catalog\Api\ProductRepositoryInterface::class); $product = $productRepository->get('my-sku'); ``` ✅ GOOD: ``` public function __construct( private ProductRepositoryInterface $productRepository ) {} public function getProduct(string $sku): ProductInterface { return $this->productRepository->get($sku); } ``` // WHY DOES THIS MATTER? Using Object Manager directly breaks dependency injection: - makes your code harder to debug - violates Magento's coding standards - doesn't create explicit dependencies in classes Injecting deps within the constructor keeps your dependencies clear and your code maintainable. The only time you should touch Object Manager? In factories, proxies, or backwards compatibility - and even then, think twice. What other Magento anti-patterns drive you crazy?

That sounds pretty confusing imo. I do like to do the same thing, but with variables, or class properties. (I.e. request a ProductInterface, but call the variable $product.

I agree with @max_pronko about the typo. However, I like to alias anything with Interface to eliminate that. For example, I’d alias HttpPostActionInterface to HttpPostAction. Or ProductInterface to Product. Interface really isn’t necessary in my opinion.

We collaborated with a #DataMapping platform to enhance their internal processes, #ProductInterface, and codebase through product interface #design, rapid feature #prototyping, and #development. #ThinkRefined21 thinkpo.st/interactive-mappi…

hi #magento folks, what do you think about removing dynamic parts from the ProductInterface at GraphQL? github.com/magento/architect…

This should help on a PHP framework level without DB reflection: /** @var Magento\Framework\EntityManager\MetadataPool $metadataPool */ $metadataPool->getMetadata(ProductInterface::class)->getLinkField()

The question is very similar to whether #Magento should use “Interface” suffix for php interfaces, like “ProductInterface” instead of “Product”. Both cases look like violation of encapsulation as code of business logic should rely just on external contract

It appears we are living in a #PlugAndPlay #era. On the plus-side, no more #PaperWaste on #Manuals ? #engineering #ProductInterface

Killer UX-design: “Een productinterface dat gebruikers het maximale doel laat bereiken met minimale weerstand. #UX #uxdesign