3 ms·
Your "Holy Grail" is what Fred Brooks called a "Silver Bullet": http://en.wikipedia.org/wiki/No_Silver_Bullet http://en.wikipedia.org/wiki/No_Silver_Bullet
by mbrubeck 17y ago
Your "Holy Grail" is what Fred Brooks called a "Silver Bullet":
http://en.wikipedia.org/wiki/No_Silver_Bullet http://en.wikipedia.org/wiki/No_Silver_Bullet
- srid68 17y agoI have seen this before and this is what i have tried to solve. Cannot today say i am successfully but I can see some light. As Fred Brooks noted Software has to be Organically grown through Incremental development. Currently this leads to most software becoming a Ball of Mud through continuous change/fixes. It is allready well established that loose coupling between components will lead to better systems, then it means that no coupling will also lead to better but useless systems since a single component may not have all the features required. If I can take the coupling and abstract it out from the component, then i should be able to build a framework which uses a meta data of coupling to create useful functionality from zero coupled components. This way i can grow the complexity of the component organically and replace components. This is what I have achieved using my experimental rudimentary framework by taking a simple domain as a web page, but hoping to extend it for building a new contract job work which involves building our own simple document management system/simple workflow management system for the Architecture firm. My question is why is tough? sorry for being Naive. Then how