Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  <div class="vevent h-event"> <h1 class="summary p-name">Portland Perl Mongers – DCI: A new way to OOP.</h1> <div class='date'><time class="dtstart dt-start" title="2011-11-10T18:53:00" datetime="2011-11-10T18:53:00">Thursday, November 10, 2011 from 6:53</time>–<time class="dtend dt-end" title="2011-11-10T20:39:00" datetime="2011-11-10T20:39:00">8:39pm</time></div> <div class="location vcard p-location h-card"> <a class="url" href='http://calagator.org/venues/202389965'><span class='fn org p-name'>Free Geek</span></a> <div class="adr p-adr h-adr"> <div class="street-address p-street-address">1731 SE 10th Avenue</div> <span class="locality p-locality">Portland</span> , <span class="region p-region">OR</span> <span class="postal-code p-postal-code">97214</span> <div class="country-name p-country-name">US</div> (<a href='https://maps.google.com/maps?q=1731%20SE%2010th%20Avenue,%20Portland%20OR%2097214%20US'>map</a>) </div> </div> <div class="description p-description"> <p> speaker: Chad 'Exodist' Granum</p> <p>The DCI concept was created by Trygve Reenskaug, (inventor of MVC) and James Coplien.</p> <p> DCI Stands for Data, Context, Interactions. It was created to solve the problem of unpredictable emergent behavior in networks of interacting objects. This problem shows itself in complex OOP projects, most commonly in projects with deep polymorphism. This is a problem that Procedural/Imperative Programming does not have.</p> <p> DCI does not replace OOP, instead it augments it with lessons learned from looking back at Procedural Programming. It defines a way to encapsulate use cases into a single place. This provides an advantage to the programmer by reducing the number of interactions that need to be tracked. Another advantage is the reduction of side-effects between contexts.</p> <p> Another way to look at it is that a DCI implementation is much more maintainable as a project matures. Changes to requirements and additional features cause clean OOP project to degrade into spaghetti. DCI on the other hand maintains code clarity under changing requirements.</p> <p>You will Learn:</p> <ul> <li>How to think in DCI</li> <li>How the DCI cpan package helps you write DCI</li> <li>That you may already write things in a form of DCI</li> <li>How a DCI implementation compares to an OOP implementation (in a generic task)</li> </ul> <p> As usual, the meeting will be followed by social hour at the Lucky Lab.</p> </div> <h3>Links</h3> <ul> <li><a class="url u-url" href="http://pdx.pm.org">Website</a></li> </ul> </div>