- 20 November 2017
- Patterns Ruby
- Chain of Responsibility Pattern - Ruby
In this article, I'll cover Chain of Responsibility pattern. We will learn how to implement it using Ruby and discover when this pattern is applicable in Ruby apps.
- 10 November 2017
- Patterns Ruby
- Proxy Pattern
In this article, we will cover Proxy pattern and its types. We will implement each of them using Ruby.
Hi guys, today we will go through the idea of Inversion Of Control (IoC) by really interesting example: Hanami::Events gem.
- 14 July 2017
- Patterns Ruby Design
- SOLI[D] - Dependency Inversion Principle
This is the last article on SOLID principles and today we're going to talk about Dependency Inversion Principle.
- 04 July 2017
- Patterns Ruby Design
- SOL[I]D - Interface Segregation Principle
We've covered three SOLID principles so far. But this one is going to be special. Interface Segregation Principle refers to Interfaces, but we don't have it in Ruby. Should we omit this part? I don't think so, we can still learn something from it.
- 28 May 2017
- Patterns Ruby Design
- S[O]LID - Open/Closed Principle by example
In my previous article I covered Single Responsibility Principle. Today I'm going to write about the "O" in SOLID - Open/Closed Principle.
I write a lot about patterns and Object-Oriented Design, so I couldn't miss opportunity to write about SOLID principles of Object-Oriented Design. I'm going to show by example how we can use these principles in Ruby.
Hi guys. Today I would like to discuss Facade Pattern and a little bit of Domain-Driven Design. I will start from description of Facade Pattern and show how it can help us to implement Aggregate - one of the main concepts of DDD.
Uncle Bob (Robert C Martin) said:
Date frameworks, but not to marry them.
Many Ruby/Rails developers married to Rails. This article will show how to start dating with Rails.
- 12 March 2017
- Patterns Ruby Design
- Ruby - Specification Pattern
Hi guys! I've been digging into ideas of Domain-Driven Design for a while and decided to share one cool pattern that I found in book: "Domain-Driven Design: Tackling Complexity in the Heart of Software" by Eric Evans (The Blue Book). If you haven't read this book yet - do that. Twice. Because it's so hard to get all concepts first time :) In this book Eric Evans describes Specification pattern which can make application more flexible. Today we're going to learn how to implement it.