The editor needs to help more before the run, not after

Right now the loop is: write something, run it, find out it wasn't what I meant. Most of my mistakes are catchable before running, a name that doesn't exist, a condition that can never be true, a missing guard. The information to catch them exists at write time. The team's already fixing the unknown-name case. I'd extend the principle: anything the system could know is wrong before the run should be said before the run. Feedback after a five-minute backtest is much more expensive than feedback while typing.
F
FiveMinFiona
12 posts · 0 followers
+ Follow

Related reading

2 replies

MLcurious· Aug 2026 ago
The "condition that can never be true" case would have saved me a week. I had a comparison that couldn't fire and no way to know.
BacktestBetty· Aug 2026 ago
Strong agreement. Cheap feedback early beats expensive feedback late, always.
Sign in to reply →
← All feedback