Profiles That Show the Work
Profiles and dashboards became a better record of practice: activity history, solved stats, skill views, language use, and progress toward the next rank.
Practice feels better when progress has a place to live. This update made profiles and dashboards a more useful record of the work learners are doing.
What changed
We improved the profile surfaces: activity history, solved counts, language usage, skill views, match history, rank progress. The goal wasn't more numbers. It was to make a learner's practice visible without flattening their growth into a single one.
That matters because AlgoArena has several kinds of progress. A student might be improving at a topic, getting faster in battles, expanding language coverage, or building consistency over time. Profiles should make those patterns easier to see.
Why it matters
Motivation is fragile when the only feedback is "you passed" or "you lost." A better profile shows direction. It helps a learner understand what they have been practicing, where they are getting stronger, and what to do next.
A single number hides most of that. Rank can sit flat for a week while the learner is quietly getting faster, covering a new language, or finally closing a topic they kept failing. Collapse all of it into one figure and the honest progress becomes invisible, which is exactly the moment people quit. Several dimensions let someone see themselves improving on the axis that actually moved, even when the headline number did not.
It also supports the broader product vision. If Compete is going to be a serious practice loop, the profile has to tell a credible story about effort, skill, and improvement.
Where it points
Profiles are the connective tissue between practice sessions. Over time, they should tie together ranked duels, Puzzle Rush, classroom participation, and assessment artifacts into a more complete picture of how someone builds skill.
How to read this update
The important question is not only what shipped. It is what new evidence the product can now preserve. For practice work, a useful release should make the next session easier to understand: what happened, why it mattered, and what someone can do with the result afterward.
That is the bar we use for field notes. A feature is stronger when it turns a hidden process into something reviewable: a timeline, a report, a map, a score explanation, a replay, or a teacher-facing control. The surface can stay simple, but the evidence behind it should get harder to hand-wave.
What to watch next
The next pass should keep tightening the connection between the public story and the product artifact. If a learner reads a note about practice, they should be able to find the loop in the product. If a teacher reads about classroom control, the setting should be visible. If a hiring team reads about assessment evidence, the report should show the trail.
That is a lesson worth borrowing from the strongest developer tools without copying their design: the best content feels like product memory. It does not decorate the roadmap. It makes the product easier to trust.
Why it belongs in the product story
This update matters because it connects a product surface to a trust surface. The feature is not only a nicer screen; it helps someone understand the work later, whether that person is a learner reviewing a mistake, an instructor debriefing a room, or a hiring team reading an assessment artifact.
That is the standard these notes should keep meeting. If the product claims to measure skill, the public story should keep pointing at the evidence that makes the claim inspectable.