The 19 shoulds of writing clean code

By

The 19 shoulds of writing clean code

  1. The code should be clean.
  2. The code should be beautiful.
  3. The code should be elegant.
  4. The code should be graceful.
  5. The code should be functional.
  6. The code should be maintainable.
  7. The code should be reusable.
  8. The code should be testable.
  9. The code should be efficient.
  10. The code should be well-documented.
  11. The code should be well-tested.
  12. The code should be well-designed.
  13. The code should be well-written.
  14. The code should be well-architected.
  15. The code should be well-engineered.
  16. The code should be well-structured.
  17. The code should be well-commented.
  18. The code should be well-organized.
  19. The code should be well-formed. 







Comments

Post a Comment

Popular posts from this blog

Top 36 effective ways to collaborate with other technology companies or developers to create innovative and high-value products or services

By
Top 36 effective ways to collaborate with other technology companies or developers to create innovative and high-value products or services Identify a common goal or problem that both parties are interested in solving, and work together to find a solution. Communicate openly and regularly to ensure that all parties are on the same page and working towards the same goals. Build trust and establish clear lines of communication and decision-making. Provide support and resources to help other parties succeed. Create a collaborative environment that encourages open communication and idea sharing. Establish clear roles and responsibilities for each party involved in the collaboration. Set up regular meetings or check-ins to discuss progress and challenges. Use shared tools and technologies to facilitate collaboration and communication. Share data or other resources to help support each other's efforts. Create a shared vision and mission for the collaboration, and work together to achieve
Read more

[PYTHON] Top 29 best practices for writing efficient and effective code in 2023

By
[PYTHON] Top 30 best practices for writing efficient and effective code Use the ` PEP 8` style guide to help you format your code consistently and readably. Use ` docstrings` to document the purpose and behavior of your code. Use ` assertions` to help you verify the assumptions and invariants in your code. Use  `try/except`  statements to handle exceptions gracefully and avoid crashing your program. Use ` with` statements to manage resources, such as files and connections, in a safe and efficient way. Use the ` if/elif/else` construct to express conditional logic in a clear and concise way. Use for and ` while` loops to iterate over data in a controlled and predictable way. Use ` list comprehension` and ` generator expressions` to write concise and efficient code for working with data. Use ` lambda` functions to define simple, single-purpose functions inline. Use ` map`, `filter` , and ` reduce` to apply functions to data in a functional style. Use ` decorators` to add funct
Read more

89 Tips to help you be a better coder and write clean code in 2022

By
Image
89 Tips to help you be a better coder and write clean code in 2022 Writing clean code is a must for any developer. Here are 89 tips to help you be a better coder and write clean code in 2022 from 'Clean code' by Robert C. Martin. General rules Follow standard conventions. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible. Boy scout rule. Leave the campground cleaner than you found it. Always find the root cause. Always look for the root cause of a problem. Design rules Keep configurable data at high levels. Prefer polymorphism to if/else or switch/case. Separate multi-threading code. Prevent over-configurability. Use dependency injection. Follow the Law of Demeter. A class should know only its direct dependencies. Understandability tips Be consistent. If you do something a certain way, do all similar things in the same way. Use explanatory variables. Encapsulate boundary conditions. Boundary conditions are hard to keep track of. Put the proc
Read more