apex-recipes VS lwc-recipes

More information on testing HTTP callout methods and code samples can be found at the APEX Developer Guide as well as the APEX recipes Github repo.

When first starting out doing development, I did a lot of copy-pasting and editing existing code. There is no shame in this; it’s all part of the learning process. Luckily, in the APEX Recipes Github repository, we can find some APEX Recipes with bite-sized snippets of code for almost everything that you might need. The code samples found here are also “production quality,” so it would be a useful exercise to review and compare it with any existing code you’ve written to gain some insights into what Salesforce considers best practices.

You can get a free developers org (developer.salesforce.com) and play with it, which I suggest.

What I can do is point to a number of case studies where a company created a platform and then encouraged a community of 3rd party entities to build on top of that platform. Salesforce, Amazon Web Services, Lego, and pretty much any game developer, like Paradox, that supports a modding community, .

as a follow up comment, you can leave all the detail you want, they won't read it at first and ask you for details. I've written all kinds of painstaking details, and gotten "well, try this URL from developer.salesforce.com"

You can do the free courses and also spin up your own developer org: http://developer.salesforce.com

When you write JavaScript, your code editor is able to provide some sort of auto-completion based on the code you previously wrote. It does not work very well with plain JavaScript and we will see how to improve that by modifying the todoList.js file from Salesforce's LWC recipes repository. We are using Visual Studio Code as our code editor, but other IDE also have similar features.

There are also three good official blog sites admin.salesforce.com developer.salesforce.com and architect.salesforce.com with additional resources. I'd look at the Architecture and Admin ones in particular.