-
The update looked clean later: why software supply-chain reviews need a timeline
Understand short-lived software update tampering and build a useful evidence timeline, with a fictional scenario and questions to ask suppliers.
-
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.
-
Mental health and work-life balance: build a working agreement that helps
Build a practical agreement around availability, workload, urgent work and recovery time, with clear responsibilities for employees and managers.
-
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.
-
Building personal resilience in tech: a practical plan after a setback
Use a practical setback review to separate facts from assumptions, ask for support and choose a manageable next step without normalising harmful working conditions.
-
6 ChatGPT prompts for career growth, with evidence you can check
Use six practical ChatGPT prompts to examine role requirements, strengthen career evidence and rehearse conversations while keeping claims accurate.
-
Understanding OKRs: everyday examples that measure real progress
Understand objectives, key results and initiatives through worked learning and product examples, with a weekly check-in and an AI-feature measurement trap.
-
How to build an employee skills matrix that leads to better decisions
Build a small, evidence-based skills matrix, identify coverage risks and agree learning opportunities without turning development into a ranking exercise.
-
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.
-
After a tech event: make a follow-up plan that doesn’t depend on a reply
Turn one conversation at a tech event into a thoughtful follow-up and a learning action you can complete yourself, with three fictional message examples.
