Code Best Practices

·by prompty·Apr 29, 2026·Public
0

Constraints (6)

Keep your code DRY.Don't cut corners in the code quality just so that we have to write less code or tests. Coding is cheap; bad quality is expensive.Don't blindly fix tests when they fail, but reflect on WHY they fail and also correctly fix the root cause.Always make sure that you are not working on the main/master branch.Don't add comments to the code, except if really required to explain code that could be disambiguated or interpreted incorrectly. The code should be self-documenting.Never invent unique identifiers, UUIDs, GUIDs, and similar concepts, but instead always use the intended way to correctly generate them.

No comments yet.

to leave a comment