Skip to main content
Software Engineering

Return to Answer

deleted 1 character in body
Source Link
Robert Harvey
Robert Harvey
  • 200.1k
  • 55
  • 468
  • 679

Application code should only be as good as necessary, but library code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs tooto be good in all aspects, be it performance, robustness, or any other category.

Also, you need to think about performance when you design your application and when you pick algorithms. If it isn't designed to be performant, no degree of hackery can make it performant afterwards and no micro-optimizations will outweigh a superior algorithm.

Application code should only be as good as necessary, but library code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs too be good in all aspects, be it performance, robustness, or any other category.

Also, you need to think about performance when you design your application and when you pick algorithms. If it isn't designed to be performant, no degree of hackery can make it performant afterwards and no micro-optimizations will outweigh a superior algorithm.

Application code should only be as good as necessary, but library code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs to be good in all aspects, be it performance, robustness, or any other category.

Also, you need to think about performance when you design your application and when you pick algorithms. If it isn't designed to be performant, no degree of hackery can make it performant afterwards and no micro-optimizations will outweigh a superior algorithm.

added 101 characters in body; added 6 characters in body; edited body
Source Link
sbi
sbi
  • 10.1k
  • 6
  • 39
  • 56

Application code should only be as good as necessary, but library codelibrary code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs too be good in all aspects, be it robustness, performance, robustness, or any other category.

Also, you need to think about performance when you designdesign your application your applicationand when you pick algorithms. If it isn't designed to be performant, no degree of hackery can make it performant afterwards and no micro-optimizations will outweigh a superior algorithm.

Application code should only be as good as necessary, but library code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs too be good in all aspects, be it robustness, performance, or any other category.

Also, you need to think about performance when you design your application. If it isn't designed to be performant, no degree of hackery can make it performant afterwards.

Application code should only be as good as necessary, but library code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs too be good in all aspects, be it performance, robustness, or any other category.

Also, you need to think about performance when you design your application and when you pick algorithms. If it isn't designed to be performant, no degree of hackery can make it performant afterwards and no micro-optimizations will outweigh a superior algorithm.

Source Link
sbi
sbi
  • 10.1k
  • 6
  • 39
  • 56

Application code should only be as good as necessary, but library code should be as good as possible, since you never know how your library is going to be used. So when you're writing library code, it needs too be good in all aspects, be it robustness, performance, or any other category.

Also, you need to think about performance when you design your application. If it isn't designed to be performant, no degree of hackery can make it performant afterwards.