http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/ Recent content in Software Design on RAVR Lab Hugo en-us Wed, 30 Apr 2025 00:00:00 +0000 http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/design_prncpls/ Wed, 30 Apr 2025 00:00:00 +0000 http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/design_prncpls/ Actually usable: Separation of Concerns EAFP — it is easier to ask for forgiveness than permission Blurry: SOLID (OOP-related) KISS — keep it simple stupid YAGNI — you ain’t gonna need it http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/gof/ Wed, 30 Apr 2025 00:00:00 +0000 http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/gof/ Software design patters are reusable solutions to common problems that arise during software development. The most popular book on that matter is: Design Patterns: Elements of Reusable Object-Oriented Software (1994) (also known as «Gang of Four») Patterns from Gang of Four: Creational: Factory Abstract Factory Builder ProtoType Singleton Structural: Adapter Bridge Composite Decorator Facade Flyweight Proxy Behavioural: Chain of Responsibility Command Interpreter Iterator Mediator Memento Observer State Strategy Template Visitor Other related patterns: http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/oop/ Wed, 30 Apr 2025 00:00:00 +0000 http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/oop/ OOP Terminology Classes: Class — blueprint for creating objects. Instance — general «concept» of being an object of class. Object — actual entity in memory. Abstract Class (vs Concrete Class) — class that cannot be instantiated (Python: ABC and @abstractmethod). Can contain abstract methods. Subclasses of abstract class are required to provide implementation for abstract methods. Subclass (Derived Class) — class that interits from Superclass (Base class). Metaclass — class which instances are classes. http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/architectures/ Wed, 30 Apr 2025 00:00:00 +0000 http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/architectures/ Software Architectures: Layered Onion Hexagonal (Ports and Adapters) Microservices Event-Driven GUI Architectures: Paradigms: Immediate mode (ImGUI) Retained mode (Qt) MVC variants: Model View Presenter Model View Controller (MVC) Model View View-Model Model View Adapter Model View Update (Elm architecture) Exotic: RP and FRP (Reactive), 1-way-binding, 2-way-binding Lisp CLOS Erlang BEAM Approaches: Clean Architecture Domain-Driven Design Imperative shell, Functional core http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/antipatterns/ Fri, 04 Oct 2024 00:00:00 +0000 http://ravrlab.ru/en/cs/progr_and_sdes/csdsgn/antipatterns/ Main: Spaghetti code (poorly structured code architecture, confusion, complexity for understanding) Gold hammer (overuse of patterns where they are not appropriate) Magic numbers (using numbered constatns to identify data — without any semantics) overly-Hard code (program is unportable to other devices) overly-Soft code (excessive tuning of program is allowed) Accidental complexity (complexity that comes not from business domain, but from the coding approach) Boat Anchor (unusable parts of program are left in the code) Reinventing the wheel (ignoring already existing, more superior solution) Lava flow («I don’t know how it works, but it works») Programming by permutations (mindless games with +1, -1 and such) Blind faith (insufficient check of outer world data) Mindless commenting (non-informative comments) God Object (object that stores too many functions/data of various usage scenarios) Code smells (symptoms that there might be smth bad with the code):