For large orgs, Lightning pages are like rabbits: they multiply quickly and most of them look the same unless you are really close. To keep the page population under control, use a unique Developer Name and provide a description of its properties when customizing record pages that will be assigned to anything other than Default.
A frequent concern I hear from people tasked with learning a new technical skill on their own time is that it can be difficult to fully digest what they are reading about or putting in to practical terms some of the paint-by-numbers lessons often provided. The cure I found for myself to this dilemma is subscribe to support sites for the technology or product and work on answering problems for other people. It gives me real-world scenarios in which to apply the skill, and I when it is something I only partially understand it expands my skills by learning other solutions. And the folks who receive the answers are helped as well. Win-win!
Much better organized than my own page (which is so lame it is hidden):
https://dev.to/bobbyiliev/the-only-bash-scripting-cheat-sheet-that-you-will-ever-need-55c7
Always request reviews of your work (code, documents, designs, plans, etc.) and make time to review others work when asked. Reviewing and being reviewed improves the quality of our work and our capabilities as consultants.
Developers learn to create and apply reusable objects in their code to improve efficiency in development and maintenance. This also applies to designs, project plans, matrices, etc. Look for templates and examples before creating your own and ask others in your organization if they exist if you cannot find them. While it will almost always be necessary to modify it for a specific project, starting from something that already exists will save time and provide inputs that you may not have come up with on your own.
Murphy’s Law is your friend. Use it plan what will be monitored, how it will be monitored, when automated alerts will be generated and bot the process and frequency of reviewing monitoring history and metrics. It is great to have common tools across the enterprise and important to be specific for each component how the tools are utilized. The systems are not static so the monitoring process cannot be if it is successful.
Whenever possible, make it (solution, design, steps, instructions) simple to save time (effort, thought, debugging, explanations) for when it can’t be simple. And remember that what seems simple to you right now may not be to someone else or even yourself in the future.