Data Structures we use everyday is nice post. It's still lower level of how an application works. Extend that how we are using in real life. Say list --> how we keep our contacts. But better would be to understand design patterns & how we apply them. Say API design, You expose only few calls allowed for few, few calls not allowed for few, only certain information etc. Suppose you are asked while having small talk with someone and they ask you sensitive details you will not reveal. The behavior exhibited by living beings and different computer related designs the concept is same the in design of underground logic at certain places. Like standing in queue so the name queue. rememberthemilk.com is old list maintainer & has apt name. LIke that.
Data Structures we use everyday is nice post. It's still lower level of how an application works. Extend that how we are using in real life. Say list --> how we keep our contacts. But better would be to understand design patterns & how we apply them. Say API design, You expose only few calls allowed for few, few calls not allowed for few, only certain information etc. Suppose you are asked while having small talk with someone and they ask you sensitive details you will not reveal. The behavior exhibited by living beings and different computer related designs the concept is same the in design of underground logic at certain places. Like standing in queue so the name queue. rememberthemilk.com is old list maintainer & has apt name. LIke that.