I think calling it a &quot;map&#x2F;reduce (functional) style&quot; is an understatement. The presenter is suggesting that when a problem must be solved in parallel, don&#x27;t just code the low level parallel implementation. Analyze the problem, divide-and-conquer, then use high level abstractions that make parallelism a responsibility of the underlying implementation.<p>This concept may be familiar to you, but talks like this will be necessary until parallelization is as seamless as garbage collection.