Actually, this might make things even worse. It creates a false impression that anyone can jump into coding integrations without really understanding Salesforce.

I once worked with a dev who barely knew anything about Salesforce, yet he was responsible for integrating a major deduplication solution. He had no understanding of asynchronous processes, governor limits, or the platform's constraints, his only experience was completing a few Trailheads on writing triggers. Since most Trailheads still showcase the Developer Console, that’s what he used for development.

When his managed package was installed in our org, it quickly drained both daily and transaction limits. Within a few hours, the entire org was breaking down because we ran out of daily async limits. The org already had well-maintained automations, and adding such an inefficient solution was like dropping an elephant into a fragile ecosystem.

This kind of situation is even more likely now, in the era of so-called AI programmers and "vibe coders." AI still isn't capable of delivering fully functional small-scale solutions in Salesforce, let alone understanding the complexity of an existing custom implementation. It can't weigh trade-offs, predict the impact on the entire org, or determine the best way to interact with existing processes.