Azlam
@azlusFocus on improving Developer Experience for my fellow Salesforce Developers. Maintainer of @dxatscale. Views my own!
Similar User
@rsoesemann
@AndrewDavis_io
@ch_sz_knapp
@ImJohnMDaniel
@MShaneMc
@pmd_analyzer
@ntotten
@PhilW_SF
@VivekMChawla
@dieffrei
@IllumCloud
@BobaliciousBob
Trying scratch orgs on your project? Here is what we have observed @SalesforceDevs @SalesforceArchs
What have we learnt working with several projects who have adopted scratch orgs, modular/package-based development over the last year? @SalesforceArchs @salesforce Let's begin by looking into Scratch Orgs, A thread.🧵
What people is missing is that because they designed the system as a set of decoupled services they could easily pack them together to save the overhead of data passing. Decoupling (which is the basic tenet of microservices) allows for more deployment options than a monolith.
Microservices are maybe not what you think they are, so here's a #Thread to describe them... 1/14
Nope. Disambiguating "deploys" from "releases" and using flags to manage releases will still make sense, even in a Glorious Future where deploys are just as instantaneous as flag flips. ☺️ But this is a terrific thought experiment!! Let's review the reasons why. 👉
I think this distinction makes sense in the status quo, where everything you mentioned under "Deploy" takes minutes at minimum, while config/feature flag toggling is usually instantaneous. It doesn't in a future where everything listed under "Deploy" is also instantaneous.
It's peculiar to me that the most challenging thing we do as Salesforce engineers is try to make DevOps work. Salesforce has created billions of dollars worth of challenges with their odd deployment mechanisms. 🤔
What’s funny to me, is that we spent so many years developing clever ways for machines to communicate with one another, and in the end we ended up with English as the RPC protocol 🤔
Convinced wee are witnessing the birth of a new kind of computer. From: Memorizing Transformers arxiv.org/pdf/2203.08913…
Plot twist John Connor is not a soldier but a prompt engineer
Happened upon this today. This is a document that quite literally changed my life. If you're a technical practitioner working with Salesforce and you've not read it. Stop what you're doing and read it now. #YoureWelcome architect.salesforce.com/fundamentals/p…
When 'architecting' a system - aka planning how to build it, what components to put in place, what technologies to use - what are considerations you should take? Here's an important one: capture the current business needs, and anticipate future ones:
Check out my latest blog post where I share some challenges we faced and how we improved our workflow using Scratch Org Pools. Learn how to speed up your scratch org creation and enhance your development experience. #salesforce #sfdx #dxatscale medium.com/@dieffrei/intr…
Interestingly, no one ever talks about the cost of not refactoring.
Apex didn't arrive until 2006 (triggers only), Visualforce in 2008 Sandboxes were in the Winter '06 release - BUT you had to recreate your changes manually in Prod Change Sets started in Beta in the Winter '10 release.... ...and weren't in GA until the Spring '11 release
ChatGPT is incredibly limited, but good enough at some things to create a misleading impression of greatness. it's a mistake to be relying on it for anything important right now. it’s a preview of progress; we have lots of work to do on robustness and truthfulness.
Here is the reasoning: Unclean code is hard to change, because it's hard to read, understand, test, and maintain.
”The quality of a system is defined by our ability to change it!” Great opening keynote from @davefarley77 at #YOW22
Never underestimate the institutional knowledge of the (largely undocumented) architecture of a complex software-intensive system, held by a few battle-tested souls.
Google has convinced everyone that they are qualified to practice general medicine and prescribe drugs. It is not gatekeeping to appreciate expertise. The same applies to software engineering. There are levels, and there are specializations. We are not universally qualified.
Here is the latest article from our resident expert @crazynammer for everyone who is considering modular development in Salesforce Modular Development Renaissance for Salesforce - Part 1 of 2 linkedin.com/pulse/modular-…
2. Ensure the code repository, build, and test environments have at least the same security protections as other critical network capabilities 💯 As @lorenc_dan always says "Treat build systems like production systems"
United States Trends
- 1. Thankful 70,5 B posts
- 2. Man City 39,2 B posts
- 3. #RTXOn 11,5 B posts
- 4. Sharon Stone 5.350 posts
- 5. Happy Thanksgiving 31,8 B posts
- 6. #PMSLive 5.451 posts
- 7. Hezbollah 188 B posts
- 8. Venmo 24,8 B posts
- 9. Feyenoord 46,4 B posts
- 10. Arsenal 173 B posts
- 11. Manchester City 44,6 B posts
- 12. Lebanon 208 B posts
- 13. Newsom 64,4 B posts
- 14. Whitmer 2.546 posts
- 15. Gabriel 141 B posts
- 16. Gyokeres 37 B posts
- 17. #RussianBankCollapse 4.755 posts
- 18. Ederson 4.248 posts
- 19. Dembele 20,1 B posts
- 20. Creighton 3.337 posts
Who to follow
-
Robert Sösemann
@rsoesemann -
Andrew Davis
@AndrewDavis_io -
Ch. Szandor Knapp
@ch_sz_knapp -
John M. Daniel ☁
@ImJohnMDaniel -
Shane McLaughlin
@MShaneMc -
PMD Code Analyzer
@pmd_analyzer -
Nathan Totten
@ntotten -
Phil W
@PhilW_SF -
Vivek M. Chawla
@VivekMChawla -
Diéffrei Quadros
@dieffrei -
Illuminated Cloud
@IllumCloud -
Rob Baillie
@BobaliciousBob
Something went wrong.
Something went wrong.