A picture of Edsger Dijkstra with a concerned face and the following text on top: How software engineers look at your code when you solve the problem using two tables — instead of using the Maxwell-Ross-Karmakar algorithm, which is marginally optimal in ordered sets bijectable to the exponential curve
you are viewing a single comment's thread
view the rest of the comments
[–] 15 points 2 months ago (1 child)

Good point! Good point.

I've seen bubble sort implemented because we had data that said it was faster and was slightly smaller for the exact type data we were sorting and its expected distribution.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 20 points 2 months ago

    I fondly remember the time I hired a QT expert onto an embedded app team and on his first project he imported a sort algorithm from std. He found the system got weird and glitchy, and often crashed.

    Yeahhh turns out the algorithm he chose needed to make a copy in memory and the thread he was working in only had 2048 bytes of stack, so larger inputs would corrupt the stack allocated to the next thread. I had to explain to him that we had a full second to complete the math before we had to give back our semaphore, so saving a couple milliseconds on the sort was not a priority. Fun times.

  • source
  • parent