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

Except usually the code is shit, and that's ok. Sometimes I'm even talking about my own code and that's ok too.

The first step to fixing a problem is admitting the problem exists. Attempting to cover it up it with words like, "well I'm sure there is a good reason for that" or "Hrm that could be better but I know we had crazy deadlines." Are just excuses and don't really help.

If looks like shit and smells like shit... well it's probably shit.

We are all big kids here, no need to sugar coat things.

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