Your feedback is more than a grade. It shows exactly how your engineering practice compares to your cohort — and what it takes to reach the next level.
Skill Certification
Your certification level is not just a score — it is a signal of where your professional engineering practice sits relative to your peers, benchmarked against real industry expectations.
Bottom 50% of cohort
You demonstrate foundational professional practices. You are working consistently and meeting the baseline of professional engineering conduct.
Top 50% of cohort
Your engineering habits are well-established. You work incrementally, engage with code reviews, and manage your workflow with discipline.
Top 25% of cohort
You demonstrate the habits of a professional engineer. Your practice is consistent, intentional, and aligned with industry standards.
Top 10% of cohort
You are among the strongest in your cohort. Your engineering practice is exemplary — a benchmark for peers and a signal to future employers.
Cohort Leaderboard
Ranked by engineering quality — not by how many commits you made. The three dimensions measure how well you work, not how much.
#2
Priya Sharma
#1
Alex Chen
#3
Jordan Williams
Names are illustrative. Your actual leaderboard shows real cohort data after your educator runs a grading pass.
Milestone Formative Feedback
At every milestone you receive structured feedback on each criterion — not just a score, but a specific explanation of what your repository evidence shows and what to do differently before the next milestone closes.
Commits cluster near the deadline
Spread your work across the week. One focused commit per working session is the target — not ten commits the night before.
PRs are merged without review
Request a review on every PR and wait for it. Responding to feedback — even just explaining your reasoning — is the skill.
CI failures go unaddressed
A failing pipeline is a broken product. Fix it within 24 hours. Do not merge around it.
Test suite is thin or absent
Add at least one test per feature before merging. Coverage does not need to be perfect — it needs to exist and grow.
Commit messages describe what, not why
"Fix race condition in token refresh" is useful. "Fix bug" is not. Add the context that makes future-you grateful.
PR comments are surface-level
Challenge design decisions. Suggest alternatives. Ask why. A review that only catches typos is not a review.
Tests written after features
Commit tests in the same PR as the feature they cover. This is the discipline that separates intentional from reactive.
Tasks closed on deadline day
Close 80% of your milestone tasks a day before the deadline. The last day is for polish, not delivery.
Strong in most criteria but not all
Distinguished requires consistency across every dimension. A single weak criterion — even one — disqualifies you from the top 10%.
Reviews are good but not systematic
Every review should be a teaching moment. Not just "looks good" — explanations, alternatives, links to documentation.
CI pipeline runs but is not optimised
Add linting, coverage thresholds, and security scanning. A professional pipeline catches more than passing tests.
Performing well, not leading
Distinguished students set the standard others are measured against. That is the target — not topping a leaderboard, but defining what excellent looks like.
Path to Distinguished
Each commit does exactly one thing. The message explains the why, not the what. Future readers — including your future self — can reconstruct your reasoning from the history alone.
A failing build is never ignored and never worked around. Pipelines include linting, test coverage gates, and security scanning — not just "does it run".
Every code review includes an explanation. You suggest alternatives, ask why a decision was made, and link to documentation. "LGTM" is not a review.
Issues are created before work begins. Milestone tasks are closed incrementally. The deadline is for submission, not delivery.
Tests are written with features in the same PR, not added afterwards to satisfy a checklist. Coverage is a byproduct of good design, not a target chased at the end.
Distinguished is not about excelling in one area. It requires high performance across every criterion, every milestone. Partial excellence is not Distinguished.
Access Your Feedback
Enter your unit code (e.g. FIT5136-S1-2025) and GitLab username to access your personalised feedback report.
Look up my resultsURL pattern: /results/FIT5136-S1-2025/@mux0044