Beyond the README: Enforcing Application Guardrails at Runtime
Beyond the README: Enforcing Application Guardrails at Runtime
Beyond the README: Enforcing Application Guardrails at Runtime
Time-Travel Debugging: Replaying Production Bugs Locally
Testing Side Effects Without the Side Effects
Managing Side Effects: A JavaScript Effect System in 30 Lines or Less
The Innocent Loop
Lessons from David Lynch: A Software Developer's Perspective
Runtime Diagnostics: Catching Bugs as They Happen
Writing Composable SQL using Knex and Pipelines
Self-documenting Code
Avoiding if-else Hell: The Functional Style
Firewalling Your Code
Teaching Programming with BASIC
I Don't Trust My Own Code
Easy Application Deployments with Linux
Back to Basics in Web Apps
Reusable HTML Components Powered by Alpine.js Reactivity
Beyond Foreign Keys
Converting a Vue 2 App to Alpine.js
Code Examples and Guides of Functionality with Alpine.js
A comparison of a simple app in Vue.js and Alpine.js
I think you might be focusing on the execution of the request rather than the orchestration. The decision of when and why to make an API request is absolutely business logic. In imperative code, that logic is hard-coded to the execution. By separating the intent from the execution, we can test that decision flow without spinning up the infrastructure.