Congratulations, you’ve built a feedback report that someone else can use and question! Every number in it traces back to rules you agreed on and messages you can show.
In this course, you’ve:
- Agreed on a brief that fixes the topics, the label policy, the period, the output, and the unit: messages, not customers
- Composed your functions into
buildReport()and connected it to the report app - Counted messages for one reporting period with the supplied helper and, in the extension, compared two equal-length periods
- Kept the messages behind each count, with Needs review and Excluded listed separately
- Adapted one rule with an AI suggestion and checked it with cases you worked out from the brief
- Tracked down a surprising count yourself: expected versus actual, a small input, a specific hypothesis, one check, a focused fix, and a rerun
- Handed the report over with usage instructions, a checked example, and a concrete limitation
That last step is what the course was about. When the support lead asks why delivery shows 2, you can point to the two messages, name the rule that put them there, and say what the number doesn’t tell them.
Some things stayed outside the report on purpose: replying to customers, connecting the report to other tools, and having a model label messages as they arrive. They build on your ability to read code and check it against a brief, and are possible directions for your own next project.
