From 274e13c87c2000f48be65cb821931de75412ae0b Mon Sep 17 00:00:00 2001 From: Patrick McElhaney Date: Wed, 30 Aug 2023 18:50:43 -0400 Subject: [PATCH] Pretty happy with this. Just need to fill in the usage section. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9c7c7f6e..1bf278bc 100644 --- a/README.md +++ b/README.md @@ -35,9 +35,9 @@ However, over the course of several years, I found ways to minimize the effort t | Implementing a typical feature takes | days? weeks? | minutes | | Can be gradually replaced with production code | - | yes | | Running locally requires | runtime, database, etc. | node | -| Maintainable by front end devs | maybe? | +| Maintainable by front end devs | maybe? | yes | | See code changes | after compile + restart / deploy | when you hit save | -| Change behavior without losing server-side state | wait, what? | yes (hot reload) | +| Change server-side code without losing state | wait, what? | yes (hot reload) | | Interact with the server in a REPL | not likely | yes | | Reproducing weird stuff that happened in prod | hard / impossible | easy | | API response time | varies | immediate | @@ -88,7 +88,7 @@ Using the Swagger Petstore as an example: ### In a few minutes
-Enhance auto-generated mocking code with business logic and state. A few small changes can go transform your totally fake endpoint to a fully functional replica of the real one, or anything in between. +Enhance auto-generated mocking code with business logic and state. A few small changes can transform your totally fake endpoint to a fully functional replica of the real one, or anything in between.