Azlam

571 posts

Azlam banner
Azlam

Azlam

@azlus

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

Melbourne Katılım Temmuz 2009
780 Takip Edilen334 Takipçiler
Azlam
Azlam@azlus·
@zeeg Dear Santa, please add code scan analysis (linters) , oss scan, like the test Analysis.. and sentry is all we need
English
1
0
0
52
Azlam
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!
English
1
0
2
1.1K
Azlam retweetledi
Pablo Chacin
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.
English
0
1
7
481
Adam McCrea
Adam McCrea@adamlogic·
Queue-based autoscaling for @render is getting very close! Let me know if you want to be part of our early-access group over the next two weeks.
GIF
English
1
1
12
2.3K
Azlam retweetledi
Dave Farley
Dave Farley@davefarley77·
Microservices are maybe not what you think they are, so here's a #Thread to describe them... 1/14
English
20
180
582
127.9K
Rohit Mehta
Rohit Mehta@rohitforce·
@azlus @danielfe @SalesforceDevs What metadata type is running up against the file limit? Do you have an example that you could share? I’m happy to get on a call if it’s not in a public repo.
English
1
0
0
56
Azlam
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
English
1
0
0
118
Azlam retweetledi
Charity Majors
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. 👉
Lewis Liu@lewisl9029

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

English
8
30
153
71.1K
Mitch Spano
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. 🤔
English
5
1
29
3K
Azlam
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
English
0
0
2
116
Azlam retweetledi
Alex Skryl
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 🤔
English
2
2
32
3.3K
Azlam retweetledi
Andrej Karpathy
Andrej Karpathy@karpathy·
Plot twist John Connor is not a soldier but a prompt engineer
English
56
120
1.4K
190.6K
Azlam retweetledi
The Software Engineer’s Guidebook
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:
The Software Engineer’s Guidebook tweet media
English
3
56
403
79.3K
Azlam retweetledi
Diéffrei Quadros
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 @dieffrei/introduction-to-salesforce-scratch-org-pools-e1616772499c" target="_blank" rel="nofollow noopener">medium.com/@dieffrei/intr…
Amsterdam, The Netherlands 🇳🇱 English
0
3
6
383
Azlam retweetledi
Attention Alchemist
Attention Alchemist@alexbunardzic·
Interestingly, no one ever talks about the cost of not refactoring.
English
14
14
78
11.8K
Azlam
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
English
0
0
4
137
Robert Sösemann
Robert Sösemann@rsoesemann·
@azlus @RobSalesforce @karenfidelak @AndrewDavis_io Are you saying it's impossible today, to have a decent amount of YML pipelines + Shell scripts in Git where you see who, what, when, and why it changed? Instead, do we need the process hidden inside Copado, Gearset, or DevOps Center? Feels like going from Apex code to Flow XML.
English
2
0
4
252
Robert Sösemann
Robert Sösemann@rsoesemann·
DevOps experts say: Version Everything Code, Config, Data, and Infrastructure. Why do Salesforce DevOps tools claim to be better than script-based solutions (like Github Actions) but then hide crucial pipeline artifacts away from Git? @RobSalesforce @karenfidelak @AndrewDavis_io
English
11
0
13
4.6K
Ruslan Kurchenko 🇺🇦
Ruslan Kurchenko 🇺🇦@ruslankurchenko·
I can express my gratitude enough to @azlus, Vu Ha, Ramzi, and the @dxatscale community. You guys supported me tremendously in implementing our CI/CD pipeline. Thank You! Please, reach out to me any time if you need anything 🙏 4/4
English
2
0
4
240
Ruslan Kurchenko 🇺🇦
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 🧵
Ruslan Kurchenko 🇺🇦 tweet media
English
1
7
19
2K
Azlam
Azlam@azlus·
@rsoesemann @RobSalesforce @karenfidelak @AndrewDavis_io I would say getting there eventually.. as the complexity and number of environments increase, eventually the need arises for devops platform scripts to be version controlled, years back, jenkins configuration was visual and stored within, so was azure devops and many others
English
2
0
3
292

Keşfet

@zeeg @opencode @thdxr @kelseyhightower @diegosucaria @adamlogic @render @rohitforce