Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 6
    Of particular note, with things like sorting functions, it's much faster (in dev time) and easier to make a dumb simple algo do the right thing in all cases than to get an elegant algo fully functional and bugless. (Tho the only reasons to write a sort algo outside of acadamea are if you're building a library or working on a platform without one…) Commented Oct 25, 2016 at 10:13
  • 5
    I think you need to add the link to shouldioptimize.com :) Commented Oct 25, 2016 at 12:34
  • 13
    I think the 90/10 comes from the well known 80/20 Pareto Principle en.wikipedia.org/wiki/Pareto_principle Commented Oct 25, 2016 at 16:19
  • 3
    @StarWeaver Which is why languages that make writing super-efficient sorts as easy as or easier than a crappy bubble-sort are important there, like C++. Such "prepackaged" algorithms and code can be really heavily optimized without causing complexity at point of use. Commented Oct 25, 2016 at 17:18
  • 6
    @IvanKolmychek That site is misleading. Sure, that kind of cost analysis is one factor to consider, but there's other factors like user experience. You might save a lot of money by not optimizing, but you might also miss out on a lot of income if people leave your site frustrated. Commented Oct 25, 2016 at 20:42