Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You should never write Go code by swallowing errors first and promising yourself you'll clean it up later. You should be coding the error path first, and backfilling your business logic. The error path directly informs your method definitions and the structure of your code, which resist modification once they're in-place.


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

Search: