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

That's exactly right: it depends so much on the context and (expected) access patterns. Sometimes you really do need to plan ahead, but even that's more about not painting yourself into architectural corners rather than specific tech.

What I see also is not just scalability over-engineering, but the same in the solution domain. When you don't really understand your customers needs sometimes there's a desire to create something with ultimate flexibility.

In the days of Xp we used to say YAGNI when people would be overly general. I'm trying to bring that back into fashion.




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

Search: