> before realising I effectively hit "run" instead of "build and run". This used to happen to me all the time too. The solution I ended up going with was to st

> before realising I effectively hit "run" instead of "build and run". This used to happen to me all the time too. The solution I ended up going with was to standardize all my build scripts on `./build run` as the way to (build and) run the program, with the actual binary getting shoved in ./bin/ or something to discourage running it directly (which also reduces clutter). Basically, get rid of the "run without building" command entirely.