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

If it's customary to store the cereal in the closet in a framework, then people will know where to look for cereal.

On the other hand, if you store your cereal under a squeaky board in the kitchen, that's not helping anyone.




Or, you know, you can build your own house AND keep the cereal in a normal place.


My analogy was terrible. I admit it. But in actual practice, software varies more than houses do.

You could easily walk into my house and find the kitchen. The stove and sink are both there as expected. But despite how carefully I thought it through and built it, and despite the fact that it made perfect sense to me, I doubt you'd find my custom-built intranet app easy to navigate.

On the other hand, my last Rails app has a structure familiar to any Rails developer. The actual business logic is unique, but that's the part that has to be unique. "How do we update the database schema?" is a given.

And if it's unfamiliar, there's plenty of documentation and blog posts to help you. With custom-built code, there's no help on the web.




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

Search: