216 reputation
18
bio website twitter.com/#!/jdgwillard
location Pensacola, FL
age 26
visits member for 2 years, 8 months
seen Jun 9 '12 at 0:50

I'm a newly graduated web development guy. I enjoy gaming, writing, music, LEGO, literature, and a whole mess of other stuff. I'm passionate, focused, and enjoy a good debate. I use sarcasm liberally, so keep an eye out. :)


Apr
26
comment When accessing/manipulating complex data, is it better to store it in many small pieces or one large chunk?
Thanks for a great answer. +1 and the cigar.
Apr
25
comment When accessing/manipulating complex data, is it better to store it in many small pieces or one large chunk?
Do you not design databases before you build them? My question is on designing a database. Not troubleshooting one. I am not in the debugging stage yet, and even if I were, that would go to StackOverflow, not Programmers. Per the FAQ: Programmers covers algorithm and data structure concepts, design patterns, software architecture, software engineering... Not troubleshooting bottlenecks.
Apr
25
comment When accessing/manipulating complex data, is it better to store it in many small pieces or one large chunk?
Well, it's a web app. A lot of users are potentially going to be modifying data fairly frequently. I'd imagine a lot of factors like you mention affect it differently. I'm not so familiar with those specifics; that's partially why I'm asking here.