Re:Programmers should stop calling themselves engineers (2015)
by roenxi on Sunday May 26, 2019 @07:34PM
(#20018309)
No rule is free from exceptions I suppose. The distinction I'm trying to draw is between the decision to use QuickSort and the actual implementation - so if someone is thinking ahead and decides that QuickSort is the best option on a given architecture (considering a couple of options) is doing engineering.
Someone who codes up QuickSort is probably, at the time of coding, not making engineering decisions because the decisions inside a QuickSort implementation have largely already been made. This is simply a view on where the dividing line sits between an engineering decision and something else.
How about when it involves getting the best possible performance out of the given hardware architecture?