Ramzi Akremi

Opinions are my own! Passionate about Software Engineering in the Salesforce space, and how to make the complex less daunting. "Go slow in order to go fast"

[Ramzi Akremi @rakremi]

@WenYuGe1 Homebrew

[Xi Xiao @xixiaofinland]

☊ #Salesforceway podcast 101 | The Ops in Salesforce DevOps (https://t.co/9T7F0pvdxI)

Guest: Azlam Abdulsalam @azlus
Video Teaser: https://t.co/DNPVeHlBMq

[Jason Lantz @jasontlantz]

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). https://t.co/SSQVVGcsE9

[dxatscale @dxatscale]

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 https://t.co/fXfLHTKG5A

Thanks everybody for the support and collaboration!

[Ramzi Akremi @rakremi]

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.
https://t.co/mVojdEkJ8x and https://t.co/h9AfBL9YAq
@SalesforceDevs @dxatscale

[Ramzi Akremi @rakremi]

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

[Ruslan Kurchenko 🇺🇦 @ruslankurchenko]

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 🧵

[dxatscale @dxatscale]

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

[Robert Sösemann @rsoesemann]

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 https://t.co/kGawr8pucC

[Ramzi Akremi @rakremi]

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

[Ramzi Akremi @rakremi]

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

[Ramzi Akremi @rakremi]

@rsoesemann haha, you tell me 😉

[Ramzi Akremi @rakremi]

@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.

[Ramzi Akremi @rakremi]

@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, ...)

[Robert Sösemann @rsoesemann]

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.
https://t.co/8d3jjIVGq7

[Ramzi Akremi @rakremi]

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

[Ramzi Akremi @rakremi]

@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

[Ramzi Akremi @rakremi]

@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)

[Ramzi Akremi @rakremi]

@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.