dxatscale (@dxatscale) header
dxatscale (@dxatscale) profile picture

Open Source based Productivity boosters for Salesforce Developers #salesforcedevops

Joined May 2021
March 23 Release Notes have been published for the DX@Scale Team. New features and quality improvements are the theme of the month. Head over and review whats new at github.com/dxatscale/dxatsca… Thanks everybody for the support and collaboration!
1
3
559
February 23 Release Notes have been published for the DX@Scale Team. New features and quality improvements are the theme of the month. Head over and review whats new at github.com/dxatscale/dxatsca… Thanks everybody for the support and collaboration!
1
163
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/dxatsca… Thanks everybody for the support and collaboration!
1
1
185
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 🧵
1
6
1
19
2,054
sfpowerscripts November 22 Release Notes have been published. Head over and review whats new at github.com/dxatscale/dxatsca… Thanks everybody for the support and collaboration!
2
As of today, 150 Orgs are on a modular development model using @dxatscale practices and tools. Its easier than you think.. Get started today!
2
4
When I look at companies that are using Salesforce well (i.e. getting a high return on their Salesforce investment), I see a common theme: they all have a person or team managing the system that does the following 5 things well (in no particular order) (1/11) 🧵
10
39
11
260
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
The machines are already writing the code. Those machines are called compilers. We, programmers, simply specify the solution in sufficient detail so that the machines can write the code. Specifying the solution in sufficient detail will _always_ be a human endeavor.
26
242
11
1,326
If you are at all interested in packaging this #DF22 talk from the @dxatscale team is well worth your time salesforce.com/plus/experien…
1
6
15
Attending #Dreamforce make sure you attend our session ;) on how DX@Scale practices enable you to build a modular org @SalesforceArchs @SalesforceDevs reg.salesforce.com/flow/plus…
1
2
Thanks @scottthehokie for the shout out.
This Post is from an account that no longer exists. Learn more
1
2
We did an analysis of 1233 validation runs on ~ 25 member team for the last 1.5 months on with a lifespan of 4 years (orchestrator: validate is a check of metadata and selective apex tests based executed on every work items) Here are some observations..
1
5
14
While we are analysing the reasons, one reason we have infererred is 'impact analysis ', which triggers test classes that are impacted. Most devs dont trigger test classes other than for the one they are modifying. @nawforce fyi.
2
3