Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
8-17-2011 @ 12:05PM
Adam Holisky said...
Some of it is definitely lazy developers, don't get me wrong, but a large portion of it is the evolution of programming thought. It's common place nowadays to build in extensible systems with absolutely no hard limits. 10 years ago when the bank and storage space was built? It wasn't at all.
There's also the factor of super high-performance computing, where reducing DB reads by even 1 or 2 reads can lead to significant performance gains. Even in a caching scenario that can be huge when applied to millions of accounts. I do a fair amount of programming (and DB work), and when moving things to a high performance embedded situation, I (and everyone I know) commonly takes shortcuts by hard coding some things.
So I don't think it's all bad programming. Def a combination of old coding/design standards and meeting the demands of the situation.