From 11b9f68b025d6d126839bfec47b6c9b87b9006f7 Mon Sep 17 00:00:00 2001 From: John Costa Date: Fri, 3 Apr 2026 21:01:36 +0100 Subject: [PATCH] update: Coding Review Process.md --- content/blog/Coding Review Process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/Coding Review Process.md b/content/blog/Coding Review Process.md index ef4db3b..74d9605 100644 --- a/content/blog/Coding Review Process.md +++ b/content/blog/Coding Review Process.md @@ -20,7 +20,7 @@ This should be done in a separate environment to the one you code in. For me, th 1. Does each commit _still_ make sense? 2. __High level overview__: Does it actually work? Are you wiring the correct functions to the correct place? We often miss the bigger picture when we're down in the code. 3. Does the architecture make sense? Are the functions you choose and the abstraction you made worth it? -4. Does it work E2E? +4. Does it work end-to-end? 5. __Nits__. Do the names make sense, is the spacing correct. Less important, but still very important. If you can't understand your own code, how can others? ## Optional: Have AI review your code