Hakkında
Mark Seemann is a Danish software developer based in Copenhagen, Denmark. His professional interests include functional programming, object-oriented development, as well as software development in general. Apart from writing two books he has also written numerous articles and blog posts about related topics.
Despite being mostly a .NET developer he takes most of his inspiration from sources across a wide range of technologies, including Haskell and lots of pattern books.
Originally poised to become a rock star or (failing that) graphic novelist (in the European tradition) he one day found himself with insufficient talent for either, a masters degree in Economics, and a desire for working with computers. He has been doing the latter intermittently since 1995.
When not working with software or spending time with his family, Mark enjoys reading, listening to and playing music, as well as preparing or consuming gourmet food and wine.
Okurlar
1 okur okudu.
Okur demografisi
Kadın% 0.0
Erkek% 0.0
0-12 Yaş
13-17 Yaş
18-24 Yaş
25-34 Yaş
35-44 Yaş
45-54 Yaş
55-64 Yaş
65+ Yaş
Reklam
Alıntılar
The advantage of loose coupling is the same in software design as it is in the physical socket and plug model: Once the infrastructure is in place, it can be used by anyone and adapted to changing needs and unforeseen requirements without requiring large changes to the application code base and infrastructure. This means that ideally, a new requirement should only necessitate the addition of a new class, with no changes to other already-existing classes of the system.
This concept of being able to extend an application without modifying existing code is called the Open/Closed Principle. It’s impossible to get to a situation where 100% of your code will always be open for extensibility and closed for modification. Still, loose coupling does bring you closer to that goal. And, with every step, it gets easier to add new features and requirements to your system.
Being able to add new features without touching existing parts of the system means that problems are isolated. This leads to code that’s easier to understand and test, allowing you to manage the complexity of your system. That’s what loose coupling can help you with, and that’s why it can make a code base much more maintainable.
Aspect Oriented ProgrammingYazılım
AOP as a paradigm focuses on working around the problem of repetition.
Sayfa 304 - Manning
Reklam
Reklam