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

Every one of these language toolbox books should come with a disclaimer for new devs up front about how the mark of a good craftsmen is knowing when to use the tools, when to bend or break their rules and guidelines, etc. I know it certainly might have saved me a fair bit of grief and oddly written code.



But then they wouldn't sound "authoritative" enough. The dogma-cult that keeps its leader well-fed wouldn't survive.

I think the best authoritative-sounding counter-quip is "Best practices are best not practiced."




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

Search: