Daily Pattern (Software Architecture and Design, Refactoring)

Daily Pattern (Software Architecture and Design, Refactoring)

Public

Просмотреть канал

Не можете присоединиться? @dailypattern

0

867 Участники

Обновлено: May 25, 2026 at 4:55 AM

Daily Pattern (Software Architecture and Design, Refactoring)

Software design patterns and principles, tips, code quality, software architecture, refactoring Java, Scala, Kotlin Feedback, реклама: @dailypatternfeedbackbot

@dailypattern offers specialized information about patterns and code for subscribers interested in Кодинг и программирование

Рейтинг

Глобальный рейтинг

#34344

-2388

Рейтинг по языку

#26734

-2165

Рейтинг по категории

#194

-19

Рост участников (Последние 30 дней)

Всего: 867

Рост за 24ч: -1 0%

Loading...

Рейтинг

Требуется вход

Loading...

Loading recommended channels...

Последние посты

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

High availability (HA) is a characteristic of a system which aims to ensure an agreed level of operational performance, usually uptime.

Availability refers to the ability of the user to obtain a service, access the system, whether to submit new work, update or alter existing work, or collect the results of previous work.

If a user cannot access the system, it is unavailable. The term downtime is used to refer to periods when a system is unavailable.

What is High Availability: https://do.co/2RHh4fD
Wikipedia: https://en.wikipedia.org/wiki/High_availability

2,310

0

0

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Liskov Substitution Principle is the third of Robert C. Martin's SOLID design principles. It extends the Open/Closed principle and enables you to replace objects of a parent class with objects of a subclass without breaking the application. This requires all…

1,930

0

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Replace Type Code with Subclasses #refactoring

Problem:
You have a coded type that directly affects program behavior (values of this field trigger various code in conditionals).

Solution:
Create subclasses for each value of the coded type. Then extract the relevant behaviors from the original class to these subclasses. Replace the control flow code with polymorphism.

https://sapanparikh18.github.io/Refactoring-Part-2/

2,160

0

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Сommand pattern is a behavioral design pattern in which an object is used to encapsulate all information needed to perform an action or trigger an event at a later time. This information includes the method name, the object that owns the method and values for the method parameters.

Four terms always associated with the command pattern are command, receiver, invoker and client.

Using command objects makes it easier to construct general components that need to delegate, sequence or execute method calls at a time of their choosing without the need to know the class of the method or the method parameters.

Java example: https://bit.ly/3mc3I9h
Scala example: https://bit.ly/2FdcrXz
Wikipedia: https://en.wikipedia.org/wiki/Command_pattern

2,460

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Domain-Driven Design (DDD) is an approach to software development that centers the development on programming a domain model that has a rich understanding of the processes and rules of a domain. The name comes from a 2003 book by Eric Evans that describes the approach through a catalog of patterns. Since then a community of practitioners have further developed the ideas, spawning various other books and training courses. The approach is particularly suited to complex domains, where a lot of often-messy logic needs to be organized.

DDD by Martin Fowler: https://martinfowler.com/bliki/DomainDrivenDesign.html

Getting started with DDD: https://dzone.com/refcardz/getting-started-domain-driven

1,910

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Liskov Substitution Principle is the third of Robert C. Martin's SOLID design principles. It extends the Open/Closed principle and enables you to replace objects of a parent class with objects of a subclass without breaking the application. This requires all subclasses to behave in the same way as the parent class.

To achieve that, your subclasses need to follow these rules:

- Don't implement any stricter validation rules on input parameters than implemented by the parent class.
- Apply at the least the same rules to all output parameters as applied by the parent class.

Details and Java examples: https://dzone.com/articles/solid-design-principles-explained-the-liskov-subst
. NET explanation (and ducks example): https://blog.ndepend.com/solid-design-the-liskov-substitution-principle/

1,720

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

#refactoring
Lambdas and Clean Code: https://dzone.com/articles/lambdas-and-clean-code

1,700

0

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Event Bus Pattern

Imagine having a large scale application containing a lot of components interacting with each other, and you want a way to make your components communicate while maintaining loose coupling and separation of concerns principles, the Event Bus pattern can be a good solution for your problem.

The idea of an Event bus: you have some kind of pipeline and computers connected to it, and whenever one of them sends a message, it’s dispatched to all of the others. Then, they decide if they want to consume the given message or just discard it.

Read more: https://dzone.com/articles/design-patterns-event-bus

1,790

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

Covariance and contravariance

Understanding of covariance and contravariance is a key to understanding how generics work in different programming languages.

Variance refers to how subtyping between more complex types relates to subtyping between their components. For example, how should a list of Cats relate to a list of Animals? Or how should a function that returns Cat relate to a function that returns Animal?

Covariance means that the subtyping relation of the simple types is preserved for the complex types.

Contravariance means that the subtyping relation of the simple types is reversed for the complex types.

Java explanation: https://dzone.com/articles/covariance-and-contravariance
Why Is Contravariance in Scala so Hard: https://dzone.com/articles/why-is-contravariance-in-scala-so-hard
Variance, Immutability, and Strictness in Kotlin: https://kotlinlang.org/docs/reference/generics.html
Wikipedia: https://en.wikipedia.org/wiki/Covariance_and_contravariance_(computer_science)

Daily Pattern (Software Architecture and Design, Refactoring)

24 апр. 2026 г., 04:15

📷 Photo

#refactoring Decompose Conditional

Problem: You have a complex conditional (if-then/else or switch).

Solution: Decompose the complicated parts of the conditional into separate methods: the condition, then and else.

1,430

0

Showing 10 of 10 posts

No more posts