People these days often use .reduce with spread .... So it becomes O(n^2). There're lots of articles (even on dev.to) which showcase such an approach. My experience of interviewing says me that people don't understand that there's a problem.
I'm not sure I understand what you mean, do have an example that would illustrate this kind of situation? Thanks!
Where ...agg is potentially being spread for each iteration over users. Instead of an internal traversal, use any kind of loop for O(n) time instead of O(n^2).
reduce could be used, but was abandoned because it's absolutely unnecessary. for .. of (or any loop structure) could be used instead of .forEach. The latter was used as a manner of preference.
Note: it's actually something closer to O(n(n+1)/2) + O(n) where once coefficients and smaller figures are removed simplifies as O(n^2).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not sure I understand what you mean, do have an example that would illustrate this kind of situation? Thanks!
I think he means something like:
Where
...agg
is potentially being spread for each iteration overusers
. Instead of an internal traversal, use any kind of loop for O(n) time instead of O(n^2).reduce
could be used, but was abandoned because it's absolutely unnecessary.for .. of
(or any loop structure) could be used instead of.forEach
. The latter was used as a manner of preference.Note: it's actually something closer to O(n(n+1)/2) + O(n) where once coefficients and smaller figures are removed simplifies as O(n^2).