Ramzi Akremi

@WenYuGe1 Homebrew

New Mac, what do you install first?

☊ #Salesforceway podcast 101 | The Ops in Salesforce DevOps (salesforceway.com/podcast/the-op…) Guest: Azlam Abdulsalam @azlus Video Teaser: youtu.be/qP9rf4BOpt0?si…

Introducing D2X, a new open source Salesforce DevOps tool designed to make it easy to launch projects fully configured to leverage all of GitHub that align with the Salesforce Well-Architected principles of Adaptable (Resilient and Composable). muselab.com/d2x

January 23 Release Notes have been published for the DX@Scale Team. New Craft-First Frameworks available and as new features in sfpowerscripts to explore. Head over and review whats new at github.com/dxatscale/dxat… Thanks everybody for the support and collaboration!

Our lightweight trigger framework and associated sample bypass strategy are now open source. To help you decouple your components if you have embarked on your Salesforce modularisation journey. bit.ly/409Ygrp and bit.ly/408n576 @SalesforceDevs @dxatscale

@ruslankurchenko @azlus @dxatscale Thank you @ruslankurchenko. Amazing to see what you have achieved in such a short period!

I can express my gratitude enough to @azlus, Vu Ha, Ramzi, and the @dxatscale community. You guys supported me tremendously in implementing our CI/CD pipeline. Thank You! Please, reach out to me any time if you need anything 🙏 4/4

It has been about 6 months since we adopted @dxatscale in @khealth. It is the best time and effort investment for our Salesforce delivery pipeline. To make it even more precise - I can't imagine working with other CI/CD solutions on this platform in the future. #sfruslan 1/4 🧵

As of today, 150 Orgs are on a modular development model using @dxatscale practices and tools. Its easier than you think.. Get started today!

We all agree: Dev Teams need rules to be successful. But where is the sweet spot between anarchy and bureaucracy? My answer: Craftsmanship plus a few simple Ground Rules. I did a presentation about the rules I use at #SFSummit22 today. Here's the recording youtube.com/watch?v=khSSaY…

@adamwathan, silly question: What is the "tailwindcss" way for the "font-stretch" property? Seen Mona Sans and Hubot from @github, and they look gorgeous!

@afalker @dxatscale Yes! It does not need to be org dependent. As long as you declare the package dependency.

@rsoesemann haha, you tell me 😉

@rakremi If it contains also a ton of lousy Apex…

Watched this Youtube Series of this guy refactoring real-world code and loved it. Would anybody be interested in doing a channel where we do this for Apex? youtube.com/watch?v=p-oWHE…

@AndrewDavis_io @dxatscale @ramziakremi The other benefit that I didn’t talk about is how that eases the data setup when you are testing the business logic.

This level of unit test performance on the Salesforce platform is unheard of. @dxatscale @ramziakremi #FastFeedback #ContinuousDelivery salesforce.com/plus/experienc…

@AndrewDavis_io @dxatscale @ramziakremi The beauty of testing in isolation. The Ruby or Elixir communities were our main source of inspiration. This requires to tuck away everything that triggers IO (database, network, ...)

2022 seems to be the year of Open Source Apex Parsers. Just 2 weeks ago #aheber published this one. It's JS-based and uses the Tree-Sitter parser generator. github.com/aheber/tree-si…

@rsoesemann @theodoorvd @azlus So the screenshot with the exclamation mark is your service?

@theodoorvd @rakremi @azlus I believe keeping ALL business logic in ONE place is more important than everything else. I get why Services (I call them Commands) should be context-free. Here is an example of how I achieve both. Primarily by moving context & filtering into variants of the Command constructor.

Practical wisdom from Top-of-the-edge experts. This is what makes @Dreamforce - beyond marketing and party - a real conference. Sessions like the one about Decomposing the Happy Soup & Packaging at Scale. Thanks @rakremi & @azlus from @dxatscale. You rock! salesforce.com/plus/experienc…

@rsoesemann @azlus So finally, I think that I am going to land on: the trigger handler responsibility is to re-create the business context, format and to rely on the Service to execute the business logic. The handler is still a View :D

@rakremi @azlus why do move the filtering of records into the trigger? In most cases, this relevance decision is part of the business logic. I put all decision into the Service classes.

@rsoesemann @azlus The reason why we did that was that we didn't want the Service to handle the maps populated by the trigger. The Service should be re-usable no matter what is triggering it (trigger, LWC, inbound integration)

@rsoesemann @azlus We had instances where we wanted to check the modification of a specific field and trigger the associated logic. That "filtering" logic or better context creation was done in the handler.