Development Principles (Software development methodology)

YAGNI (You aren't gonna need it)

  •  do the simplest thing that could possibly work

 KISS (Keep it simple, stupid)


  • Simplicity is the ultimate sophistication

 DRY (Don't repeat yourself)

SOLID Principles:

  •  Introduced by Robert C. Martin in the early 2000s.
  • Helps to create a system that is easy to maintain and extend over time.
  • It is typically used with test-driven development, and is part of an overall strategy of agile and adaptive programming.

  1. Single responsibility principle: the notion that an object should have only a single responsibility.
  2. Open/closed principle: the notion that “software entities … should be open for extension, but closed for modification”.
  3. Liskov substitution principle: the notion that “objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program”.
  4. Interface segregation principle: the notion that “many client specific interfaces are better than one general purpose interface.
  5. Dependency inversion principle: the notion that one should “Depend upon Abstractions. Do not depend upon concretions.”.Dependency injection is one method of following this principle.

Comments

Post a Comment

Popular posts from this blog

SignalR (Push Services with Hubs)–Part 1

ASP.NET SignalR is a library for ASP.NET developers that simplifies the process of adding real-time web functionality to applications. Real-time web functionality is the ability to have server code push content to connected clients instantly as it becomes available, rather than having the server wait for a client to request new data. Push services is something like whenever data changes in any of the devices (web, mobile, ssms) the data displayed on other devices will be updated instantly. Push Pattern: Push services are not an official pattern. Technical approaches for push Periodical polling Long polling Forever Frame Service Sent Events (SSE) Web Sockets SignalR: A server side framework to write push services A set of client libraries to make push services communication easy to use on any platform Optimized for asynchronous processing Two Programming Models Persistent connections Hubs NOTE: SignalR packages are available through NuGet ...
Read more

Adapter pattern:[Structural]

Image
A class that would be useful to your application does not implement the interface that requires. Does not support multiple inheritances. Match interfaces of different classes. It is also known as “ Wrapper ”. Adapter is a wrapper that helps one object integrates with any other object's interface. Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces. Types: Class Adapter pattern Object Adapter pattern N OTE: Normally adapter pattern used in DataAccess layer to adapt the ADO.Net adapter classes like SQLAdapter.
Read more

Singleton Pattern:[Creational]

Image
The Singleton Pattern ensures the class has only one instance and provides a global point of access it. Only one instance of the object to be created and shared between the clients. In singleton constructor is private, so other classes cannot instantiate it. Here instances & methods are static, so we can access it in global point. Ex: public sealed class ClassicSingleton {     //single instance     private static ClassicSingleton instance;     private static object syncRoot = new Object();       //private constructor     private ClassicSingleton() { }       public static ClassicSingleton Instance     {         get         {             if (instance == null)            ...
Read more