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

Yes, it is absolutely more valuable to know what the code "should" be doing than to know what the code is doing

Otherwise there is no way to know what is expected behavior or just a mistake built into it by accident




Especially on teams where deviance has been normalized, and broken things are just expected. I've been bitten both ways before: is this an obvious mistake? Or the lynchpin holding up the house of cards? Of course, if someone had just written some text explaining it, or perhaps a decent commit message instead of just "WIP", maybe we wouldn't have to do archaeology every single time.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: