Status starts as a column. Then someone asks “who was denied last Tuesday?” and the schema can’t answer. Model each status change as its own row from the start, without sacrificing read performance.
Some say interface tests are fragile and shouldn’t be written. I disagree. Here’s why I think they’re worth writing.
Keep the beauty of duck typing with no annotations while still catching missing methods, mismatched signatures, and accidental drift across classes.
The perils of a seemingly harmless ORDER BY clause.
Let’s look at an example of how custom enumerators can help on your day-to-day work.
Make your transactional web requests more maintainable with The Chainable Request Pattern.
Clarifying a few possible ways to implement transactional workflows when working with external APIs.
Clarifying a few possible ways to implement resumable workflows when working with external APIs.
Quando usar objetos de consulta e como eles podem ser estruturados?
When is it best to reach for query objects and how can we best structure them?