Skip to main content
fixed grammar
Source Link
Walter
  • 16.1k
  • 8
  • 59
  • 95

Simple is king. Every bit of complexity that is added needs to justify its existance. How does it make the code better? Is that benefit worth the added complexity? We always approach adding more complexity as an evil act to the code. Only once you determine the code can't really live without it, is it appropriate to add it.

If you can't quantify and justify the complexity then leave it out.

Simple is king. Every bit of complexity that is added needs to justify its existance. How does it make the code better? Is that benefit worth the added complexity? We always approach adding more complexity as an evil act to the code. Only once you determine the code can't really live without it is it appropriate to add it.

If you can't quantify and justify the complexity then leave it out.

Simple is king. Every bit of complexity that is added needs to justify its existance. How does it make the code better? Is that benefit worth the added complexity? We always approach adding more complexity as an evil act to the code. Only once you determine the code can't really live without it, is it appropriate to add it.

If you can't quantify and justify the complexity then leave it out.

Source Link
Walter
  • 16.1k
  • 8
  • 59
  • 95

Simple is king. Every bit of complexity that is added needs to justify its existance. How does it make the code better? Is that benefit worth the added complexity? We always approach adding more complexity as an evil act to the code. Only once you determine the code can't really live without it is it appropriate to add it.

If you can't quantify and justify the complexity then leave it out.