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

I disagree with this. Writing a set of "technical objectives" that say how a thing will work takes an hour at most and it helps you think through it better than a conversation. It also helps you pass information to QA. If someone asks what the thing does, you can just send them the link. Ultimately, taking an hour to write it down pays dividends later on.



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

Search: