Software Development
For Agile, Scrum, Kanban, XP, DevOps, TDD, etc.
-
How to use Codex during a working day, with six practical prompts
Use Codex to understand a project, clarify a change, build, investigate failures and prepare a useful handover. Includes one worked example and six copyable prompts.
-
How AI is reshaping development teams, from tickets to pull requests
Explore how AI is changing tickets, coding, pull requests and board updates, with a practical prompt and clear team responsibilities.
-
After launch: create a repeatable check for one important user journey
Create a repeatable check for one important user journey, with a fictional worked example, clear evidence, response ownership and a reusable record.
-
A “security audit” workflow can be the attack: how to review GitHub Actions
Review automation by its trigger, code, permissions and destinations. A practical GitHub Actions exercise informed by October 2026 GhostAction reporting.
-
How to start a career in tech engineering: choose a route and build evidence
Compare engineering routes through small tasks, then build a software project you can explain, test and change, including when you use AI.
-
Hiding a button is not access control: write a permission rule you can test
Turn a vague access requirement into a clear permission rule, with a fictional request tracker, five proposed checks and a reusable note for your next feature.
-
How to write an accessibility bug report a developer can reproduce
Turn an accessibility concern into a clear, reproducible issue with a worked example, a reporting template and a practical retest plan.
-
JavaScript recursion stuck? Trace the work left before changing the code
A stopping condition is only useful when each recursive call moves towards it. Practise with a small JavaScript example and a reusable trace sheet.
-
Better requirements: working with developers, standards and suppliers
Learn how to clarify requirements with developers and suppliers, make standards usable and plan for the failures an integration must handle.
-
Work keeps carrying into the next sprint? Investigate before changing the estimate
Use three recent unfinished items to understand what changed, then agree one focused experiment without blaming the team or lowering quality.
