My favorite part about my job @laravel is when a customer presents me with a way their app does something specific that I don’t know the answer of how it will work on Cloud and I get to relentlessly pressure test that theory.
Outcome Driven Development means you as the engineer define the Outcome exactly as you intend the app to work.
- How many clicks to reach the goal. - What screens, or lack there-of, and with what details. - What authentication and authorization is required for each detail
Thanks to @AmpCode’s amazing harness my grand theory of “Outcome Driven Development” that I’ve been refining over the last year is becoming much simpler to execute on.