Azlam

Focus on improving Developer Experience for my fellow Salesforce Developers. Maintainer of @dxatscale. Views my own!

[Azlam @azlus]

Trying scratch orgs on your project? Here is what we have observed @SalesforceDevs @SalesforceArchs

[dxatscale @dxatscale]

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

[Azlam @azlus]

@zeeg It used to be the forte of Low Code Platforms

[Azlam @azlus]

@zeeg Dear Santa, please add code scan analysis (linters) , oss scan, like the test Analysis.. and sentry is all we need

[Azlam @azlus]

@opencode sdk is so easy to integrate. The ability to switch among differ providers itself is a big win. Building coding agents is now for everyone

Thanks @thdxr and team for the awesome stuff!

[Pablo Chacin @pablochacin]

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

[Azlam @azlus]

@adamlogic @render whats the eta for this one?

[Dave Farley @davefarley77]

Microservices are maybe not what you think they are, so here's a #Thread to describe them...

1/14

[Azlam @azlus]

@rohitforce @danielfe @SalesforceDevs Thanks @rohitforce will schedule some time up with you . Its not the metadata type . but rather the record based configuration and auto generated stuff from managed packages

[Azlam @azlus]

@danielfe @rohitforce Is there any improvements in the roadmap for a beefier scratch org? Something that has more file storage? This would help with imdustry cloud development or certain managed packages #sfdx @SalesforceDevs

[Charity Majors @mipsytipsy]

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

[Mitch Spano @MitchSpano]

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.

🤔

[Azlam @azlus]

@MitchSpano Agree with all of it here, metadata API needs some serious investment, Its so frustrating to see when a new type comes out , that can only be retrieved but not deployed ! The amount of work around we have to do in our tooling is growing every day

[Alex Skryl @ssskryl]

@stephen_wolfram @OpenAI 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 🤔

[Amjad Masad @amasad]

Convinced wee are witnessing the birth of a new kind of computer.

From: Memorizing Transformers https://t.co/ou5oXr9lp0

[Andrej Karpathy @karpathy]

Plot twist John Connor is not a soldier but a prompt engineer

[Peter Chittum @pchittum]

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

[The Software Engineer’s Guidebook @EngGuidebook]

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:

[Diéffrei Quadros @dieffrei]

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

[Attention Alchemist @alexbunardzic]

Interestingly, no one ever talks about the cost of not refactoring.

[Azlam @azlus]

@rsoesemann @RobSalesforce @karenfidelak @AndrewDavis_io Nope, it is definitely possible, thats what we do with @dxatscale ;) For starters, we even recommend version controlling manual pre/post steps . Its a bit more challenging for 'native devops platforms' to figure out the right representation to version control and make it readable

[Azlam @azlus]

@ruslankurchenko @dxatscale Woohoo . fantastic! What an exciting milestone. Lets keep pushing the boundaries