Skip to main content

Opt greseli de design care ne pot afecta aplicatia

Am inceput sa studiez design patterns si am inceput cu o carte de a celor de la Gof (Gang of Four). In aceasta carte am gasit opt greseli de design care ne pot afecta aplicatia:
  1. Crearea unui obiect folosind numele unei clase explicit. In acest fel ajungem sa fim legati direct de o anumita implementare. Pentru a evita acest lucru putem sa folosim o interfata, iar instanta sa o cream in mod indirect, de exemplu printr-un factory.
  2. Dependinte directe fata de sistemul hardware sau software. In cazul in care aplicatia noastra depinde in mod direct de anumite resurse ale sistemului portabilitatea scade in mod direct. Pentru aceaste cazuri putem sa incercam sa folosim un patern precum bridge, pentru a scadea dependintele.
  3. Dependintele fata de o anumita operatie. Cand specificam o anumita operatie, limitam ca lucrurile sa se intample intr-o singura varianta si numai una. Modific─ârile care o sa apara in viitor o sa necesite mai mult timp, deoarece totul este hard-codat.
  4. Dependinta fata de algoritm. De obicei pe parcursul dezvolt─ârii unei aplicatii un algoritm se schimba, din aceasta cauza algoritmii ar trebuii sa fie izolati si schimbati cu usurinta.
  5. Extinderea functionalitatilor prin subclase. In momentul in care trebuie sa adaugam o noua functionalitate, putem foarte simplu sa mostenim din clasa parinte si sa adaugam o noua functionalitate. Dar acest lucru implica sa cunoastem foarte bine clasa de baza, iar in timp poate sa duca la existenta unui numar foarte mari de clase. Acest lucru se poate rezolva prin delegation si composition. Aceste doua mecanisme ne permite sa adaugam functionalitati fara sa avem o inlantuire de subclase.
  6. Clase strans legate intre ele. In momentul in care ajungem sa avem o colectie de clase care sunt strans legate intre ele sistemul devine monolit. Orice modificare ajunge sa fie extrem de greu de facut si necesita cunoasterea foarte buna a sistemului.
  7. Imposibilitatea de a modifica anumite clase. Uneori avem nevoie sa modificam clase la care nu avem acces la codul sursa sau necesita modificarea unui numar mare de subclase. Pentru a evita acest lucru putem sa folosim Adapter sau Visitator pattern.
  8. Dependinte directa fata de un obiect sau o implementare. Este reprezentat in cazul in care o clasa conoaste modul in care o alta clasa functioneaza si este implementat. Modificarea aceste clase poate sa cauzeze modificari in cascada la toate clasele care folosesc clasa respectiva.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.


Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms


Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming


Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…