Hacker News new | past | comments | ask | show | jobs | submit login

Have an idea of what should happen, compare it to what actually happens.

Even if it's not the thing you're actively working on, something being out of place tends to stick out as wrong and will help you notice problems earlier. An example from pairing with someone at work recently: "Wait a minute, that ran way too fast, there's no way it actually succeeded" - indeed, it had failed in a way the system couldn't detect.

I kinda thought everyone does this at at least a basic level. How else would you realize your code has the wrong output?




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: