To each his own. :-)
On May 21, 6:45 pm, Anil <[EMAIL PROTECTED]> wrote: > On May 19, 11:21 am, kurosh <[EMAIL PROTECTED]> wrote: > > > > > 2) A software engineering paradigm that is neither procedural or > > object oriented. > > Progress log: > > To resolve the complexity of variable interdependency in a complex > > system the following is proposed: > > To abstract algorithmic complexity as an interconnection of electrical > > circuit elements. To build an equivalent circuit model and use the > > laws of circuit analysis to analyse any conflicting components. To > > hence serve as a debugging model and further as a synthesis tool to > > design fail-proof systems. > > When I read this, I laughed. In my copy of the circuit theory textbook > (Van Valkenburgh) when I was in college, I had written (18 years ago > in India): certain real world problems e.g. traffic or blood flow or > money in an economic system are probably mappable or analogous to > electrical circuit problems. so we can use circuit theory to massage/ > analyze them and map the results obtained, back into their problem > domains. > The point I am making is, it is no use having some grand idea written > down - just like I did; you will spend the rest of your life in > frustration and regret. Instead, take your idea and actually work on > it, perhaps in a University. That will really bring out whether it is > useless or not - or already done by someone else. > my 2 cents. > Anil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Challenge" group. To post to this group, send email to android-challenge@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-challenge?hl=en -~----------~----~----~----~------~----~------~--~---
