Topic
Engineering Practice
Page 3 of 30 articles about Engineering Practice, newest first.
Browse the complete article archive →Unit, Integration, or End-to-End Test? Put the Check at the Right Layer
Choose test layers by failure mode with a filled checkout coverage map, a reproduced SQLite boundary defect and an honest record of remaining journey gaps.
Update a Dependency with a Reviewable Diff and a Recovery Plan
Review direct and indirect dependency changes, reproduce a consumer failure, and recover a matching manifest and lockfile with a complete isolated npm example.
Use a Performance Budget Before a Web Release Gets Slower
Set a page-specific performance budget with clear units and failure gates. Use an actual local payload failure and a filled resource trade-off decision.
Use an Error Budget to Decide When Reliability Work Takes Priority
Use a filled error-budget calculation and pause/resume record to connect reliability evidence with release priorities, reviewed exceptions and named owners.
Use Canary Releases to Compare a Small Rollout with the Stable Version
Compare a canary release with the stable version using a filled evaluation packet, checked sample arithmetic and bounded expansion or withdrawal records.
Use Contract Tests to Catch Integration Mismatches Before Deployment
Catch API mismatches with consumer contracts and provider checks. Review a local HTTP example, breaking change and version compatibility decision matrix.





