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

So you are neatly packaging your knowledge, publishing it and marketing it (at least here and on reddit, not the smallest websites, possibly elsewhere) but somehow it's still a "personal document" and your "best practices" shouldn't be followed?

> "In the context of our team I can afford to make more sweeping statements"

As soon as you publish your document and market it the context of your statements changes. A lot. Think about all the *-killers that pop up every single day: the Internet loves to bash them when they fail.



I see your point. This started off as a personal/close-knit reference for me and my teams’ best practices. Then I thought I might as well share it, even if only one other person finds it useful then that’s better than keeping it to myself. I packaged it with caveats and disclaimers and you can take the advice or leave it.

A document was created for a small audience, sharing it was secondary, and an afterthought. It is not up to me to decide who follows them and who doesn’t; I merely made them public and people have the ability to pick, choose or even ignore at will.


You have some interesting opinions.

It would be better if you viewed your code less emotionally, and focused on getting the job done. Maybe then you'd be more productive?




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

Search: