CPIICyL organizes: Object Oriented Programming must die

132 visits  
EnglishEspañol
    Finalized

Is it possible that OOP is the root cause of most of overdesign making just write code unnecessarily complex? What alternatives exist? Is there any way of “Judgments” OOP complexity and keep the “good parts”? Why is it essential to maintain simplicity when code bases over one million lines?

Discover the answers to these questions and many more in Valladolid, the 3 December to the 17:30h in the Science Park Campus Miguel Delibes with the presence of the following experts:

  • José Daniel García: Associate Professor at the Carlos III University and leader of the Spanish Committee for Standardization of C . Doctor, expert in high perf computing and web infrastructure, author and an active member in the evolution of C .
  • Javier Garzás: Expert consultant in Software Engineering. Professor at the Universidad Rey Juan Carlos. Doctor in Computer Science and author of numerous books and bloghttp://www.javiergarzas.com

Agenda

  • 17:30 – 18:00 Opening of the day.
  • 18:00 – 18:20 Introduction to the problem of over-design software in large codebases + practical problem – Pablo Santos, Dean of CPIICYL and Development Manager Plastic SCM.
  • 18:20 – 18:40 Risks, problems and alternative OOP – José Daniel García.
  • 18:40 – 19:00 The strengths of OOP ~ @ ~ S Javier Garzs.
  • 19:00 – 20:00 Roundtable on benefits, disadvantages and alternatives to OOP with case studies and intervention of the public.

Approach
A skilled programmer solves problems writing code much simpler than a novice. The simple code, structures and designs simple and easy to understand are a sign of experience.

The simplicity and readability are also essential in projects with large code bases.

“Programs must be written for people to read, and only incidentally for machines to execute”. Is the famous book “The Structure and Interpretation of Computer Programs”. If writing simple and readable code is as essential, then why is there such a strong tendency to write complicated code and authentic castles that end up being unnecessary? It seems that we all agree that the ~ @ ~ overdesign ~ @ ~] is one of the deadly sins of software. And it seems that it is a condition that takes years to heal, because almost all rookies have greatly complicate your life to solve any problems.

We all assume the “premature optimization” as a clear factor leading to over-design and unintelligible code but, What if the object orientation was also a problem in itself? When we learn object orientation were settling a number of concepts “what is right” and “what is wrong” then take a long time to overcome. An example is the abuse of inheritance: used extensively heritage is a good sign to show that dominate OOP when you cursas the relevant subjects, however what used to pass an exam (logical, on the other hand, to show that the essential techniques are known laboratory cases) need not apply in the real world.

Unnecessary hierarchies, confusion of member variables with global variables in disguise and a clear trend “construct general solutions” (generalize) are some of the “smells” that follows the OOP.

Will they be truly intrinsic problems of OOP? Are learn better and faster if we formed us directly in object orientation? What are the alternatives?

 

All this and much more in the session "The OOP must die"

Limited places! Join now!

Registration Link: https://laoppdebemorir.eventbrite.es/

✔ Events