0 views collected around this technical thread.
Abstract classes and interfaces are core object‑oriented concepts that enable reusable, extensible, and maintainable code; this article explains their definitions, design considerations, and real‑world applications, illustrated with Java examples of a Control hierarchy and a Shape interface implementation.
This article demonstrates how to create and apply custom Spring annotations for AOP logging, implements the corresponding aspect, and discusses the strategic use of abstract classes and interfaces to separate business logic from data access in both MongoDB and MySQL contexts.
This article explains how Python's Abstract Base Classes provide interface‑like contracts for OOP, demonstrates their use with a payment‑gateway example, shows how to build a plugin system, and highlights the benefits of early error detection, clear conventions, and extensibility.
The article explains why declaring business data structures with TypeScript's interface or type is discouraged, illustrates practical problems such as property name changes and type mismatches, and advocates using classes to gain decorator support, combined behavior and data, and better extensibility.
This article explains how Go treats nil pointers within interfaces, why an interface containing a nil pointer is still non-nil, demonstrates the behavior with code examples, compares it to Java, and discusses practical implications for writing robust Go programs.
This article examines whether a Service layer in a Spring‑based backend should use interfaces, critiques the common justifications, proposes a top‑down coding workflow, explores AOP proxy options, and presents modular project structures for single or multiple implementations.
This article explains the zero‑size nature of Go's empty struct, demonstrates how its memory address behaves, shows its impact on struct alignment, and presents multiple practical patterns such as set implementation, large arrays, signal channels, no‑op methods, interface stubs, and the noCopy identifier.
This article explains PHP enums, showing how they improve code readability and safety, and demonstrates their integration with interfaces, traits, attributes, validation rules, casting, and matching mechanisms, providing practical examples and best‑practice recommendations for backend developers.
This article examines whether every Service and DAO class in a Spring‑based backend should implement an interface, discusses the three traditional reasons for using interfaces, explains why they often do not hold up, and proposes practical structuring alternatives for single‑ and multi‑implementation scenarios.
This article examines whether a Service layer in Java Spring projects truly requires interfaces, debunking common arguments, exploring development workflows without interfaces, discussing project structuring for single and multiple implementations, and concluding when interfaces are beneficial or unnecessary.
This article examines common TypeScript type‑reuse issues in a component library, compares type aliases and interfaces, demonstrates using utility types like Omit and Pick, introduces unified base props, shows tuple usage for hooks, and explains function overloads to improve code maintainability and type safety.
This article traces the evolution of the PCI Express (PCIe) standard from its 1.0 inception to the latest 6.0 specification, highlighting key differences in data rates, encoding schemes, equalization techniques, and test requirements that enable higher bandwidth and reliability for modern data‑center and AI workloads.
This article introduces PHP 8’s new Stringable interface, explains its purpose, shows how to implement it with example code, and demonstrates its seamless integration with common string functions such as str_replace, strlen, and substr for more concise string handling.
This article presents a comprehensive set of front‑back end collaboration standards, covering why a coordination protocol is needed, detailed workflow steps, interface design rules, common pitfalls with concrete code examples, and the measurable benefits of adopting a unified development contract.
This article explains the role of Java interfaces as communication protocols between modules, demonstrates their use with a computer‑assembly analogy, and covers Java 8 features such as default and static methods, method‑conflict resolution, and best practices for interface design.
This article provides a comprehensive overview of the PCIe interface evolution, detailing the specifications, version milestones, bandwidth improvements, encoding and signaling changes from PCIe 3.0 through PCIe 7.0, and their impact on data‑center, AI/ML, and consumer hardware.
The article discusses how abstraction and decoupling through Java interfaces—such as service layers, RPC APIs, and middleware adapters—can improve code maintainability, enable flexible implementation swaps, and clarify responsibilities, while also warning against over‑engineering in most business scenarios.
This article explains why and how to separate front‑end and back‑end responsibilities, introduces the SPA‑based architecture, outlines development processes, and provides a detailed API specification (including request/response formats, pagination, and special field rules) to improve collaboration and reduce integration effort.
The article examines whether the Service layer in a Spring‑based Java project truly requires interfaces, debunks common justifications, proposes practical development workflows, and outlines project structures for both single and multiple implementations, concluding with recommendations on when to use interfaces.
This article explains why front‑end and back‑end should be separated, describes the evolution from MVC to SPA, outlines responsibilities, development workflow, and provides a detailed version‑1.0.0 API contract including request/response formats, pagination, special data types, and mock‑server usage.