Professional and Enterprise Development submission

Not a build, a professional-practice module, and its own assessment reflected that: structured documentation, reflection, and formal reporting rather than code. The module asked for a level of self-assessment most technical modules don't, tracking my own development as a professional across the year rather than a system's.

It sits deliberately next to the heavier technical projects in the same cohort of modules, a reminder that the degree assessed more than whether something compiled: how clearly I could document decisions, reflect on what went well or badly in a piece of work, and report on it in a way a non-technical reader could follow. Less visible on a project list than a shipped system, but a real, separately graded piece of the same year's work, not a footnote to it.