Refactor a loop that builds paid order labels and total revenue without hiding the business steps. Keep -> transform -> accumulate The common trap is replacing a readable loop with one dense reduce that filters, formats, and totals inside an accumulator object. It works, but the reader has to reverse-engineer the data pipeline. Before One loop checks status, pushes ${order.id}: ${order.total}, and increments totalRevenue in the same block. After paidOrders = orders.filter(...); labels = paidOrders.map(...); revenue = paidOrders.reduce(...). Each name tells a data-shape story. Keep Create const paidOrders = orders.filter((order) => order.status === 'paid'). This step answers membership. It does…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in