Also this: if a system / screen is super hard to understand, you’re probably working with a poorly designed system.

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

2. Ensure the code repository, build, and test environments have at least the same security protections as other critical network capabilities 💯 As Dan Lorenc always says "Treat build systems like production systems"

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 Vu Ha for everyone who is considering modular development in Salesforce Modular Development Renaissance for Salesforce - Part 1 of 2 linkedin.com/pulse/modular-…

What does your ops team do in your Salesforce programs? Salesforce Developers

Here is the reasoning: Unclean code is hard to change, because it's hard to read, understand, test, and maintain.

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.

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

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

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…

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:

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

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

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 🤔

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

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

Kelsey Hightower Diego Sucaria 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.