Best Coding Practices

Within these castle walls be forged Mavens of Computer Science ...

— Merlin, The Coder

Introduction to General Coding Standards

Coding standards are the rules and techniques for writing clean, more readable, and maintainable code in a programming language.

Think of it like casting a spell inscribed on a magic book. The book represents a style guide on formatting the code to make sure it is efficient and free of errors. The spell is the operation being executed by the interpreter according to a set of instructions. Test it out for yourself by right-clicking on "inspect" to catch a glimpse of the markup on a web page.

Although different industries have their own standards, you should follow universal rules for documenting code to preserve its integrity and scalability. When learning to code, the key concepts are naming, commenting, indenting, debugging, scoping, and testing.

What are the Most Important Coding Conventions?

Best Practice

👍 #249

Flowcharts depict the information flow of an algorithm. For planning multi-step functions, flowcharts are your friend.

Best Practice

👍 #657

Use the appropriate capitalization on names:

• Types and protocols (for example, classes, objects) are UpperCamelCase (Pascal case)
• Everything else is lowerCamelCase (for example, variable, function, method)

Best Practice

👍 #359

For code readability, clarity is more important than brevity:

• Avoid long lines at all costs.
• Can someone else understand what it does?

Best Practice

👍 #563

Preconditions are your friend:

• They assert the state of a program before an execution.
• Include sufficient information for the message to be useful.

Best Practice

👍 #174

Great functions exhibit three vital properties:

• They are easy to read and comprehend.
• They are easy to debug if something goes wrong.
• They are easy to modify for solving a variation of the original task.

Best Practice

👍 #057

Don't declare variables outside of functions:

• Global variables are evil. They cause unintentional changes to the program.

Best Practice

👍 #207

Always use appropriate and descriptive variable names:

• Nouns are usually the most appropriate for defining variables.

Best Practice

👍 #208

Always use appropriate and descriptive function names:

• Verbs are usually the most appropriate for defining functions.

Best Practice

👍 #394

Exiting from a function in order:

• In general, don't exit a function in the middle.
• Return a function value only when the input satisfies a condition.

Best Practice

👍 #444

Avoid repetition whenever possible:

• DRY - Do Not Repeat Yourself
• DIE - Duplication is Evil
• Abstract duplicate code into a function

Best Practice

👍 #502

Determine the appropriate scope:

• The scope should not be wider than absolutely necessary.
• Think about the context of your coding project.
• Narrow it down into specific goals.

Best Practice

👍 #523

Select the appropriate loop (for loop, while loop) to iterate over a sequence or run a block of code repeatedly. Avoid breaking out of a loop midway.

Best Practice

👍 #029

Always use the appropriate indentation:

• White space is helpful for organizing blocks of code.
• Either 2 or 4 spaces are preferable.
• Use the proper closing braces and parentheses to contain multiple statements.

Best Practice

👍 #074

Use comments to help others update the code:

• Don't leave them in the dark about how it functions.
• Deliberate and helpful comments are ideal for explaining the logic.
• Avoid comments stating the obvious.

Best Practice

👍 #617

Add the appropriate nesting to keep errors at bay:

• Avoid deep nesting or the code will get buried.
• Avoid inappropriate nesting of functions that could cause confusion.
• Indent correctly according to the level of nesting.

Best Practice

👍 #831

Limit the horizontal line length. Vertical lines are easier to scan.

Best Practice

👍 #907

Organize the class files appropriately. Generally, one class per file is sufficient.

Best Practice

👍 #947

Hardcode only when there is no other choice:

• All other values should be one of the following:
  • Calculated in advance
  • Retrieved from configuration

Best Practice

👍 #959

Do not place extraneous files into the source control:

• Exclude all build artifacts.
• Exclude all "backup" files (e.g., main.swift~).

Best Practice

👍 #655

Clearly define issues in the Project Management System:

• Specificity: Ensure that the issue is well-defined and specific so it is clear to developers what needs to be done
• Context: Ensure that the issue includes sufficient context (such as error messages, logs, stack traces, screen shots, sketches) so that developers can find, diagnose, and resolve the issue
• Testability: Ensure that the issue can be tested so that QA personnel can verify its resolution
• Prioritization: Ensure that the issue is prioritized correctly based on its effect, severity, and urgency so that resources are used effectively

When the best coding practices are followed, you'll be able to create uniform code that other engineers and developers can reuse sharing the same codebase. The last step is to test your code for unusual cases, so it can handle exceptions quickly and go over the rest of the syntax.

If you choose to input hundreds of commands from a script, the computer needs to understand every line before it can carry out the desired tasks. This includes actions like uploading a PDF document or displaying a user's chat history.

Learning to write cleaner code is an essential skill to master for every aspiring developer.

Exercises

Exercises

•  M1297-28  Complete  Merlin Mission Manager  Mission M1297-28.

References

• API Design Guidelines (Swift Documentation)
• API Style Guidelines (Google Documentation)
• 6 best practices for beginner programmers
• Coding Best Practices (Rules to format code)