During two sessions Dino will tell us more about the following topics:

1st Session: Dependency Injection: Old Good Principles and New Powerful Tools.
Designing a software system is challenging because it requires you to focus on today’s requested features while ensuring that the resulting system be flexible enough to support changes and addition of new features in the future. A lot has been done in the IT industry to make a systematic approach to software development possible. Methodologies, design principles, and finally patterns have been developed to help architects to envision and build systems of any complexity in a disciplined way. In this talk, we discuss one of these key design principle that is currently gaining momentum in the .NET space (after becoming just a standard chore in the Java space). The principle is known as Dependency Inversion and it represents the conceptual foundation of Dependency Injection (or Inversion of Control) containers so popular today. We’ll see how to apply dependency injection to class design and to improve the testability and even security of our classes.

2nd Session: Past, Present and Future of AJAX
AJAX pushes a change of paradigm in the design of Web applications. Simply put, the new generation of Web applications should communicate with the back end by sending requests and getting responses instead of proceeding submitting forms to get pages. No framework exists today to *fully* support this model. We have a lot of new patterns, we may appreciate the elegance and effectiveness of the REST model for services, we always think of the back end. But what about the users? Paradoxically, we claim that AJAX is about the user experience; but then developers have not adequate tools to build this user experience effectively. The demand of AJAX developers is not properly supported by browsers—that’s the (sad) reality. We are building a new Web always using the same basic set of tools which sparked the Web to life 15 years ago. But if we move towards a richer set of tools in the browser, we break the astral conjunction which brought to have 99% of the browsers to support the same features—ultimately the only reason for the success of AJAX. With a browser model out of date, security, offline storage, rich graphics and media, effective layout is all on the developers’ shoulders. Options? Come and share your thoughts…