SOLID: Dependency Inversion Principle

This is the last article about the SOLID principles and in my opinion the most important one…. » DEV Community | dev.to

5 de agosto de 2021 · 1 min · 22 palabras · Nacho Cano

Open-closed principle

Open-Closed Principle (or OCP for short) states: Objects or entities should be open for extension… » DEV Community | dev.to

15 de julio de 2021 · 1 min · 20 palabras · Nacho Cano

Design Patterns: Builder

Welcome back to our series on design patterns. This week are tackling the Builder pattern. It’s… » DEV Community | dev.to

5 de julio de 2021 · 1 min · 21 palabras · Nacho Cano

Understanding SOLID: Dependency Inversion Principle

What is the dependency inversion principle? The dependency inversion principle is one of… » DEV Community | dev.to

20 de junio de 2021 · 1 min · 18 palabras · Nacho Cano

S.O.L.I.D Principle - Open Closed Principle (OCP)

Open Closed Principle ini dapat didefinisikan sebagai berikut: 💡 Software entities (classes,… » DEV Community | dev.to

15 de junio de 2021 · 1 min · 17 palabras · Nacho Cano

Are you a SOLID developer?

SOLID is an acronym for 5 object-oriented design principles formulated by Robert Martin - @unclebobma… » DEV Community | dev.to

29 de noviembre de 2020 · 1 min · 20 palabras · Nacho Cano

The SOLID principles of Object Oriented Design

What is SOLID? SOLID helps you to write code that is easy to maintain, extend and understa… » DEV Community | dev.to

17 de noviembre de 2020 · 1 min · 22 palabras · Nacho Cano

Memento Design Pattern Overview

Memento design pattern is a software design pattern that is used to roll back an object to its previous state. It is a part of the behavioural design pattern which is concerned with algorithms and assignment of responsibilities between objects. » hackernoon.com | hackernoon.com

12 de junio de 2020 · 1 min · 44 palabras · Nacho Cano

SOLID CSS

CSS was meant to style academic documents and simple sites (eg. wiki, blogs) where the cascade and descendant selectors makes a lot of sense. Unfortunately many sites we build nowadays are way more complex than that, and what used to work on simple projects doesn’t scale very well. We need to find smarter ways to code CSS to avoid the common issues and re-think the way we do our work. We should learn from the experience of other devs working in different domains, and apply into our own domain. Things like separation of concerns, modularity, encapsulation, DRY can (and should) be applied to large scale CSS projects as well. The main problem is that most people who are good at CSS doesn’t necessarily have a Computer Science background, most of them started as designers and learned CSS by themselves (that was my case¦). That’s the main reason why I’m writing this post. I won’t get into too much details/examples but will try to explain briefly each concept. Some of the SOLID principles are open to multiple interpretations on the CSS context - since we are shoehorning the concepts - that’s one of the reasons why I decided to not give detailed examples. I also think we should understand the idea and not be tied to a specific implementation. ...

9 de octubre de 2012 · 2 min · 223 palabras · Nacho Cano

in which three programming methods are compared

There are, roughly speaking, three ways to develop large user-facing programs, which we will refer to here as 0) the Unix way, 1) the Emacs way, and 2) the wrong way. » technomancy.us

25 de junio de 2012 · 1 min · 33 palabras · Nacho Cano