Azlam (@azlus) header
Azlam (@azlus) profile picture

Focus on improving Developer Experience for my fellow Salesforce Developers. Co founder at Flxbl

Melbourne
Joined July 2009
Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)Photo by Azlam (@azlus)
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.🧵
5
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.
1
7
485
Microservices are maybe not what you think they are, so here's a #Thread to describe them... 1/14
19
180
32
575
127,953
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. 👉
Replying to @mipsytipsy
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.
8
29
4
151
71,124
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. 🤔
4
1
1
28
3,000
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 🤔
2
2
33
3,270
Convinced wee are witnessing the birth of a new kind of computer. From: Memorizing Transformers arxiv.org/pdf/2203.08913.pdf
23
135
26
1,625
610,107
Plot twist John Connor is not a soldier but a prompt engineer
56
118
9
1,366
191,091
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/fun…
12
1
47
5,470
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:
3
56
2
397
79,361
Interestingly, no one ever talks about the cost of not refactoring.
14
14
1
77
11,766
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 – at Folkestone, England
6
5
58
3,923
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.
762
2,997
744
25,366
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
4
17
What does your ops team do in your Salesforce programs? @SalesforceDevs
61%I don't have an Ops team
33%Deployments, Environments
0%Minor declarative changes
6%Something else
18 votes • Final results
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.
19
43
6
427
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"
1
1
1
8
"I could build Twitter in a weekend" Yeah okay. A lot of people told me they could build Stack Overflow in a weekend too. But then a decade went by and it never happened. So, ya know, good luck with that.
163
296
96
4,852
Also this: if a system / screen is super hard to understand, you’re probably working with a poorly designed system.
I don't know who needs to hear this but if you are working with a system that makes it easy for you to make mistakes then you are working with a _poorly designed_ system.
3
11
68
This one definitely is ringing a bell for me.
I don't know who needs to hear this but if you are working with a system that makes it easy for you to make mistakes then you are working with a _poorly designed_ system.
3