I have strong .net background with mostly pretty legacy code and I'm amazed that this talk is so "wow" for some people. Till this point I wasn't aware people ha

I have strong .net background with mostly pretty legacy code and I'm amazed that this talk is so "wow" for some people. Till this point I wasn't aware people has such problems like described in this talk. Maybe I'm just getting old, but SQL was my first idea to solve problem. I think for most reporting related tasks simple SQL will do. I think some people just get caught in their bubble and forgot the basics: choosing right tool for a task. Of course SQL has its issues: e.g. it is problematic to test it and to manage db model changes (code first aproach wins there, hands down), but for data extensive tasks it is the way to go. This whole talk just remind me some of legacy code I was investigating one time, where developer just though he can implement everythin on his own better than standard library. Probably you need some distance when looking on particular problem to see more just "how I would just loop through all this data an calculate this".