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

I don't think there is a correct answer, but I like that a developer has foresight.


The problem is you get more information in the future, but all this boilerplate is has been written before that information so the first instinct / seemingly least-resistance thing to do is to fit the new information into the old boilerplate / hierarchy.

Lots of people have OO scar tissue from getting weird impedance mismatches on newish OO systems designed this way.


Real foresight is understanding the cost of unnecessary technical debt.


This is a pretty common misconception. I have yet to see a bit of perfect abstraction that has been written before the problem occured.




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

Search: