A couple of counter-points.. 1. You’re about to spend 100k+ tokens on generated code, why add 1-2 seconds of valuable human time backtracking to fix a typo or

A couple of counter-points.. 1. You’re about to spend 100k+ tokens on generated code, why add 1-2 seconds of valuable human time backtracking to fix a typo or typing slower to avoid a typo. At 100tok/s that’s 10ms/tok. Can you spell correctly at an upper bound of 20ms slower vs a keyboard mash to save those 2 tokens at zero net cost? Haven’t done the math but I feel like that’s well over 100wpm delta.. 2. If you spend your mental load typing with correct spelling you might make a grammatical ambiguity that adds a round trip - adding 10-120sec of human time. I’m not saying this advice is penny wise / pound foolish in 100% of circumstances, and it’s great to see the data; but there’s a bigger picture to think of. Premature optimization, and all that.