4 ms·

Don't read it, always start with using a good framework. It will do everything for you

• ovao 9y ago
  That's a pretty bold and ultimately misguided assumption.
• xxxxxxxx 9y ago
  Wow! > Don't read it and listen to you instead? Wrong. > always start with using a good framework. Wrong. > It will do everything for you Extra wrong.
• solarengineer 9y ago
  Hi homakov, given your experience with security, could you please expand on _why_ we should not this particular guide? I do understand why we should start with using a good framework, and I have so far felt that reading guides also help us understand things to be aware of.
  • rhizome31 9y ago
    Given he got kind of famous for breaking GitHub using a Rails bug, I'm pretty sure he was being sarcastic. For reference: http://homakov.blogspot.fr/2012/03/how-to.html http://homakov.blogspot.fr/2012/03/how-to.html https://news.ycombinator.com/item?id=3663197 https://news.ycombinator.com/item?id=3663197
  • homakov 9y ago
    Because just reading a book or tutorial won't give you enough info to be comfortable with all terms there. For hobby or if you have spare time - yes go ahead, for practical business needs - waste of time. Good framework handles most of them better, and if it doesn't, it's not good one. So step 1 is always framework. Optional 2 is tutorials.