Secure Software Design
A Feature Flag Is Not an Authorisation Check
Separate feature rollout from access control so a hidden interface cannot become the only protection around a sensitive server action.
SOFTWARE · SECURITY · DESIGN
Journal
Software & Systems
Verify a Webhook Before Letting It Change an Order
A webhook’s JSON can look correct and still be untrusted. Keep the original body, verify the signature and test failure before processing the event.
Software Reliability
A Delete Button Needs an Answer to What Happens to Related Records
Define how deletion affects related records, user expectations and recovery before implementing the button or choosing a database cascade rule.
Software Reliability
A Cache Key Must Keep Private User Content Apart
Decide which responses may be shared, preserve authorisation checks and test caches with separate users before enabling them for account pages.
Reliable Software
Design a Database Migration That Older App Versions Can Survive
Plan a database change around overlapping application versions, separating schema expansion, data backfill and removal of obsolete fields.
Reliable Software
A Retry Button Should Not Create a Second Order
Design retries around one intended operation so a timeout does not become a second order, with clear keys, state checks and provider-specific rules.
Better Workflows
A Scheduled Email Needs a Time Zone, Not Just an Hour
Prevent scheduled-email mistakes by making the intended time zone, daylight-saving behaviour and test result explicit before sending.
Secure Software
A Password-Reset Message Should Not Reveal Who Has an Account
Design password-reset responses that help legitimate users without confirming account membership, and support the interface with secure server behaviour.
Usable Interfaces
A File Upload Limit Should Be Clear Before the Customer Hits Send
Make upload requirements visible before submission and provide an error that tells customers how to recover without losing the rest of their work.