In the aftermath of the global financial crisis some experts proclaimed that a key issue was a need to ‘make banking boring again.’ That, essentially, money and drugs and Ferraris were the crux of the motivation behind the risk taking that led to the GFC.
Relatedly, I tend to believe that a lot of boring engineering issues actually generate a lot of value. But they aren’t sexy. So they often get ignored by relative newcomers. Eventually those newcomers will get bit by the risks associated with skipping the unsexy bits. Then they, too, will write relatively obscure blog posts about them.
Until then, I’d like to highlight a key issue for helping ensure data analytics projects are set up for success: clear definition of the problem to be solved.
Note that it is ‘problem definition’ (not ‘tool definition’). Which means that the problem definition does not dictate if machine learning will or will not be used. It just requires that the problem be stated so engineers can determine effective options for solving it.