While you are right that some feature engineering is needed, there's no reason DL can't be a part of your workflow.
https://www.slideshare.net/agibsonccc/anomaly-detection-and-...
https://www.slideshare.net/pacoid/humanintheloop-a-design-pa...
For more of the basics, my book on deep learning might help as well (minimal math vs the standard text book):
I (and, I believe, the earlier poster, too) never implied you can't use deep learning on such examples. What we (I think, both) were referring to was the claim that it would absolve you from feature engineering. (Which I understand you also refute.)
> For more of the basics, my book on deep learning might help as well
Congratulations on your book, I know how much hard work that is!
Disclaimer: I make money with deep learning, too... ;-)
I guess what I wanted to do was add a bit of nuance. It can help reduce the amount of feature engineering needed. Of course you still need a baseline representation though. More feature engineering also doesn't hurt. I always think of deep learning in the time series context as a neat SVM kernel with some compression built in. With the right tuning it can give you a better representation which you can use with clustering and whatever else you'd like.
Do you have an opinion on the fast.ai and deeplearning.ai courses? I finally have some time to work through these and since the deeplearning.ai series starts on December 18th, I'm wondering which one to dive into since I can't tell from the outside how they compare.