4 ms·
a good developer, maybe you're right. a great developer absolutely must know how to write a sorting algorithm, or three, and has to have a good idea how to sta
by baq 10y ago
a good developer, maybe you're right.
a great developer absolutely must know how to write a sorting algorithm, or three, and has to have a good idea how to start writing another five. great developers are building the infrastructure that good developers use to solve business problems. (not that great developers aren't doing that, too.)
- marcus_holmes 10y agoThat's a very specific role in the development community. There are great developers scattered in all sorts of roles in the community. Not just building infrastructure or contributing to open source projects. Besides, how many people need to write sorting algorithms before we say "enough! We know how to sort things now!"? I'd say that point was about 5 years ago. I think we can move on to other challenges now, eh?
- legedemon 10y agoNope, new sorting algorithms are still cropping up all over place. Already published sorting algorithms are still being implemented. And people are still accelerating the already existing implementations on GPU, SIMD-capable and FPGA devices. This doesn't even cover security issues such as side-channel timing or entropy attacks (hard to believe?) or handling of denormal numbers (which will reduce your processing speed by upto 100x). Ever heard of using Fast Fourier Transform to achieve asymptotically faster sorting under certain conditions? All of the above have practical applications. As you yourself said, there are interesting challenges in all communities. Let's not be dismissive of the algorithm design community.