Hacker News Reader

I like to think that our programming philosophies aren't carved in stone. (KISS, DRY, YAGNI, etc.)

To quote Captain Barbossa: ... the code is more what you'd call "guidelines" than actual rules.

Also, "A foolish consistency is the hobgoblin of little minds"

I like to think so to - guidelines are basically what best practices are. And behind every best practice there's a programmer who at one point failed and fixed their mistake. If you buy more ram/cpu/disk, are you allowing them to fail, or are you just "patching" the problem yourself?

Reply on news.ycombinator.com