This article catalogs twenty high‑frequency loop architectures that transform single‑call AI models into autonomous, self‑optimising agents, explaining each pattern’s purpose, workflow, concrete code example, and typical commercial scenarios such as content creation, compliance review, and strategic decision making.
The article presents twenty essential loop design patterns for industrial AI systems, explains how they differ from single‑call prompts, provides concrete examples, code snippets, and use‑case scenarios, and shows how these loops enable self‑improvement, memory, planning, exploration, and system optimization for AI agents.
The article examines how to regulate AI's visibility in products by applying a tiered interaction model, defining clear boundaries, and dynamically adjusting response intensity based on user intent and confidence, illustrated with real‑world examples such as Microsoft’s Clippy and data‑dashboard scenarios.
The article explains why indiscriminate use of the Java new operator leads to duplicated configuration, hidden complexity, and performance problems, and demonstrates how Factory, Builder, Object‑Pool, and Prototype patterns—illustrated with Spring Boot 3.5.0 code—provide clean, maintainable alternatives that distinguish junior from senior developers.
The article argues that building AI Agent Skills follows a nascent methodology built on three scientific principles—In‑Context Learning, attention distribution, and bounded rationality—organized into three methodological streams (design‑driven, engineering‑driven, auto‑optimization) and distilled into six reusable design patterns, with a roadmap for future evolution.
The article explains seven AI agent design patterns—workflow, routing, parallel, loop, aggregation, network, and hierarchy—illustrates their use with concrete examples and code, compares agent frameworks such as AutoGPT, Dify, AutoGen, CrewAI and LangGraph, and shows why multi‑agent architectures outperform traditional workflows in complex operational tasks.
The article breaks down twelve reusable Agentic Harness design patterns extracted from Claude Code, grouping them into memory, workflow, tool‑permission, and automation categories, explains the architectural pain points each solves, shows when to apply or over‑engineer them, and provides concrete Python implementations.
Most Java developers treat enums as simple constant lists, but modern frameworks like Tomcat, Spring Boot, and RocketMQ exploit enums for state machines, strategy patterns, lambda‑driven behavior, lightweight DSLs, and more, dramatically reducing boilerplate and improving type safety.
The article explains that software architecture is fundamentally about trade‑offs, categorises major architecture families such as DDD, Clean/Hexagonal/Onion, Microservices vs SOA, CQRS/Event Sourcing, MVC, PACELC, BASE, FLP, Repository and 12‑Factor principles, and shows how each addresses specific constraints to help engineers pick the most suitable design for their context.
This article expands the SOLID principles into a three‑layer framework—class, pattern, and component levels—clarifying common misinterpretations, presenting correct definitions with concrete examples, and showing how GRASP and design patterns operationalize these principles for stable, low‑coupling software.
Even after spending hours crafting a Skill, many LLM agents ignore it, leading to failed automation; this article analyzes why and presents five validated design patterns—linear flow, decision tree with lazy loading, iterative loops, baton passing, and multi‑stage checkpoints—plus concrete examples and a minimal Skill template to ensure reliable, production‑grade agent behavior.
The article breaks down six common agentic AI design patterns—Single Agent, Sequential Agents, Parallel Agents, Loop & Critic, Coordinator & Sub‑agents, and Sub‑Agents as Tools—detailing their implementation structures, strengths, weaknesses, and ideal application scenarios, helping practitioners choose the right architecture for scalable LLM workflows.
This article explains five practical design patterns—tool wrapper, generator, reviewer, inversion, and pipeline—for structuring AI agent SKILL.md files, showing when to use each, how they work internally, and how they can be combined for robust, maintainable agent behavior.
The article dissects Claude Code’s tool architecture, showing how a single generic triple (Input, Output, Progress) defined in src/Tool.ts unifies over 60 runtime tools, enforces type‑safe contracts, streamlines permission checks, progress reporting, and implements a fail‑closed default strategy.
The article traces the fictional rise and fall of design patterns from their 1994 debut, through a golden era of OOP and interview hype, to their eclipse by modern language features and AI‑generated code, ending with AI agents unintentionally reinventing the same abstractions.
The article distills Anthropic’s official skill‑authoring guide into fourteen reusable design patterns—grouped into discovery, context economy, instruction calibration, workflow control, and executable code—detailing their purpose, concrete examples, applicability, and trade‑offs for building effective Claude Agent Skills.
Many developers learn dozens of design patterns but still end up with fragile, hard‑to‑maintain code; the article explains that the real key is to identify system problems first and apply a disciplined engineering decision method, illustrated with concrete Factory, Builder, Strategy, Template, Decorator, Adapter, Observer and Mediator examples.
The article distills Anthropic’s production‑agent guidance into five groups of twelve concrete MCP patterns—covering tool surface design, interaction semantics, authentication, context economy, and packaging—explaining why each pattern matters, its trade‑offs, and how it helps build safe, stable, low‑cost agent integrations.
The article explains how, after format standardization removed the bottleneck for enterprise AI agents, the real challenge shifted to internal logic design, and presents five reusable Agent Skill design patterns—Tool Wrapper, Generator, Reviewer, Inversion, and Pipeline—complete with code samples, typical use cases, and best‑practice guidelines for combining and selecting them.
Google Cloud Tech’s recent article outlines five Agent Skill design patterns, building on Anthropic’s earlier work that standardized Skill format and loading, and shows how the community is shifting from merely defining Skill syntax to engineering robust, reusable workflow structures for AI agents.
The article distills Anthropic’s official skill‑authoring guidance into fourteen reusable design patterns—grouped into discovery & selection, context economy, instruction calibration, workflow control, and executable code—explaining their purpose, trade‑offs, and practical examples for building effective Claude Agent Skills.
The article critiques the classic interface‑plus‑N‑implementations Strategy Pattern for causing class explosion, then demonstrates how Java 17’s sealed interfaces and records together with Java 21’s pattern‑matching switch provide a more concise, type‑safe, and maintainable modern implementation.
Learn how to replace tangled if‑else login code with a clean, extensible architecture using Spring Boot, combining the Factory pattern to instantiate strategy beans and the Strategy pattern to encapsulate each login method (password, WeChat, SMS, etc.), enabling easy addition of new authentication types.
This article examines four core microservice design approaches—data sharing, aggregation, proxy, and asynchronous messaging—detailing their advantages, drawbacks, and ideal scenarios to help architects choose the right pattern for large‑scale systems.
Anthropic’s official skill authoring guide outlines fourteen reusable design patterns for Agent Skills—grouped into discovery & selection, context economy, instruction calibration, workflow control, and executable code—each with concrete examples, trade‑offs, and practical tips to help developers craft effective, token‑efficient Claude extensions.
This article systematically explains LangChain’s four fundamental design patterns—Command, Chain of Responsibility, Decorator, and Pipeline—showing their definitions, core implementations, and practical code examples to help developers understand and extend the framework.
The author recounts how maintaining and evolving a long‑lived production system exposed hidden costs of poor low‑level design, leading to a shift from pattern‑first thinking to change‑driven analysis, small incremental refactorings, and ultimately a calmer, more maintainable codebase.
Production AI agents require persistent memory to maintain continuity, learn from interactions, and recover from failures, but naïvely stuffing full conversation history into the LLM context incurs prohibitive latency and cost; this article outlines four memory types, a five‑stage pipeline, four design patterns, and practical metrics for building efficient, auditable memory systems.
The article demonstrates how to eliminate repetitive CRUD code in FastAPI projects by creating a type‑safe, generic repository using Python generics and SQLAlchemy, showing a concrete abstract base class, concrete implementations, custom filters, error handling, and real‑world metrics that cut repository code from hundreds to a few dozen lines.
The article analyzes the 2026 turning point where AI model intelligence plateaued and argues that mastering Harness—an infrastructure that wraps models—has become the decisive factor for building controllable, scalable Agent systems, tracing its necessity through three decades of software engineering evolution.
This article explores six practical AI Agent design patterns—ReAct, Tool Use, Reflection, Planning, Multi‑Agent, and Human‑in‑the‑Loop—detailing their principles, Java Spring AI implementations, advantages, drawbacks, and suitable scenarios, and provides guidance on selecting and combining them for robust AI applications.
This article provides a comprehensive overview of microservice architecture, outlining its core goals, design principles, and a wide range of decomposition, integration, database, event‑driven, observability, and cross‑cutting concern patterns, complete with practical examples and diagrams.
The article explains how excessive if‑else branching in backend services leads to fragile code, introduces a workflow engine and plugin extension mechanism to isolate business logic, shows concrete configuration and execution steps using the open‑source MemberClub project, and provides the full Java implementation of the FlowChain executor.
This article explains the design, principles, components, database schema, configuration, and usage of a generic asynchronous processing SDK that leverages Spring AOP, transactional events, Kafka, and a Vue UI to achieve reliable async execution and eventual consistency in Java backend systems.
The article dissects the accidental public release of Anthropic's Claude Code TypeScript source, revealing five concrete AI agent design patterns—including prompt‑cache segmentation, a coordinator‑fork architecture, a four‑layer permission model, file‑system memory, and on‑demand tool loading—while also detailing the underlying tech stack, source‑map exposure, and quirky easter eggs.
The article analyzes MyBatis’s 20,000‑line source code, showing how it applies more than ten classic design patterns—such as Factory, Singleton, Builder, Adapter, Proxy, Composite, Decorator, Template, Strategy, and Iterator—to decouple complex ORM scenarios, improve extensibility, and illustrate practical implementation details.
This guide translates Google Cloud Tech's Agent Skills design patterns, detailing five reusable architecture patterns—Tool Wrapper, Generator, Reviewer, Inversion, and Pipeline—that help developers create modular, maintainable, and composable AI agents using the Agent Development Kit (ADK).
The article explains seven multi‑agent design patterns—workflow, routing, parallel, loop, aggregation, network, and hierarchy—detailing their mechanisms, use‑cases, and trade‑offs, then surveys popular agent frameworks (AutoGPT, Dify, AutoGen, CrewAI, LangGraph) and why they are needed for complex, dynamic decision‑making tasks.
This article explains how Spring employs five core design patterns—Factory, Singleton, Proxy, Observer, and Template Method—detailing their roles, code examples, and how they contribute to Spring's modular, extensible architecture.
This article explains how to use class and object adapters in C++ to reconcile mismatched logging interfaces, allowing seamless integration of third‑party loggers without modifying existing system code, and demonstrates the transition from inheritance‑based adapters to composition‑based adapters for greater flexibility.
A C++ developer faces a mismatched logging API between an internal ILogger interface and a third‑party FastLogger library, and the article walks through class‑adapter inheritance, its limitations, and a more flexible object‑adapter composition solution that enables runtime switching across multiple logger implementations.
Google's ADK team outlines five recurring Agent Skill design patterns—Tool Wrapper, Generator, Reviewer, Inversion, and Pipeline—each solving a concrete pain point, with advantages, suitable scenarios, and ready‑to‑use YAML prompt examples for building more effective AI agents.
Google's engineers distilled five recurring design patterns for Agent Skills—Tool Wrapper, Generator, Reviewer, Inversion, and Pipeline—providing concrete guidance, example implementations, and visual decision trees to help developers craft more reliable and context‑aware AI agents.
This article dissects five practical design patterns—Tool Wrapper, Generator, Reviewer, Inversion, and Pipeline—explaining when each solves a specific problem, showing concrete SKILL.md examples, step‑by‑step instructions, and a GitHub optimizer tool that automatically refines your agent skills.
Google Cloud’s new guide outlines five validated Agent Skill design patterns—Tool Wrapper, Generator, Reviewer, Inversion, and Pipeline—explaining their structures, use‑cases, and how combining them can produce reliable, token‑efficient workflows for AI agents.
This article explores how to model clean, high‑cohesion Go structs using Domain‑Driven Design, value objects, entities, services, and proven patterns like functional options, builders, specifications, and repositories, illustrated with e‑commerce and payment system examples.
The article explains how the Builder pattern in Spring Boot eliminates the telescoping‑constructor and unsafe‑setter problems of complex objects, improves readability, immutability and maintainability, shows hand‑written and Lombok implementations, provides usage examples for DTOs, API responses and queries, and offers best‑practice guidelines.
A senior architect recounts a code review where a colleague wrapped a simple two‑payment‑method order system in strategy, factory, and abstract‑factory patterns, then explains why such over‑design hurts maintainability, when to apply complex patterns, and practical guidelines for clean backend architecture.
The article provides an in‑depth analysis of the Skills mechanism that gives large language model agents reusable procedural memory, detailing its core components, seven design patterns, real‑world security threats, evaluation benchmarks, and the challenges of safely scaling autonomous AI systems.
This article walks through the five practical levels of using C++ friend— from a quick syntax recap to operator overloads, factory functions, iterator access, swap idiom, and the Passkey pattern—explaining when and why each scenario warrants a friend declaration and how it impacts encapsulation and interview performance.
The article explains why a sprawling utils.py becomes a maintenance nightmare in Python projects, outlines three concrete patterns—module‑level placement, class‑based methods, and small dedicated modules—to restructure code, and provides decision criteria for when a function truly belongs in a utility module.
This article explains eight common software architecture patterns—from single‑database apps to microservices, caching, sharding, elastic scaling and multi‑datacenter deployment—detailing their designs, typical use cases, advantages, drawbacks, and practical implementation steps.
A code‑review anecdote shows that developers often apply heavyweight patterns like Abstract Factory, Event Sourcing, CQRS, and DDD to simple payment processing, leading to unnecessary complexity; the article explains why this happens, which patterns truly belong in micro‑service backends, and offers practical, lightweight alternatives together with concrete code examples and review guidelines.
A recent code review reveals a colleague using strategy, factory, and abstract‑factory patterns to build a payment system that only needs two methods, exposing how 90 % of classic backend architecture patterns become unnecessary over‑design in modern microservice and cloud‑native environments, and offering practical guidelines for when such complexity truly adds value.
This article explains how aspect‑oriented programming (AOP) addresses cross‑cutting concerns by defining joinpoint interfaces, describing their design, illustrating Java examples, and comparing static and dynamic weaving techniques used in frameworks like Spring.
The article explains why design patterns often feel useless in Spring Boot projects, introduces a three‑branch decision tree that maps common sources of complexity to suitable patterns, and demonstrates a concrete refactor of an if‑else payment service into a clean, Spring‑managed strategy‑based solution.
This article walks through seven core design patterns—Singleton, Factory, Builder, Strategy, Observer, Proxy, and Template Method—explaining their purpose, providing complete Java implementations, and showing how they are applied in JDK and Spring contexts.
This article explains why Java’s finally block normally runs, dives into the compiler’s code‑copying, the bytecode exception table, JVM dispatch, JIT optimizations, and the design trade‑offs that ensure reliable cleanup while highlighting cases where finally may be skipped.
The article explains why architecture matters, introduces ten essential Python design patterns—such as Dependency Injection, Strategy, Builder, Event‑Driven, Repository, Mapper, Pipeline, Command, Specification, and Plugin Registry—with concrete code examples and practical advice to transform messy scripts into clean, scalable applications.
This guide presents seven practical Kafka design patterns—single‑key single‑write, log compaction, multi‑consumer‑group fan‑out, retry and dead‑letter topics, exactly‑once processing with Streams, schema evolution with Avro, and choreography vs orchestration—detailing when to use each, core principles, code examples, tips, common pitfalls, and final recommendations for building reliable, observable, and maintainable event‑driven systems.
The article breaks down a common Netease interview task—hand‑coding a BlockingQueue in five minutes—by explaining the underlying lock‑and‑condition mechanism, the relevant design patterns and principles, common pitfalls such as spurious wakeups, and provides a concise, 50‑line Java implementation with step‑by‑step commentary.
This tutorial shows how to combine the Strategy and Factory patterns in a Spring Boot payment system, separating algorithm definition, creation, and execution to achieve a flexible, extensible, and maintainable architecture that adheres to the Open/Closed principle.
This article offers a systematic, high‑concurrency‑focused walkthrough of core Java design patterns—including Singleton, Factory, Strategy, Template Method, and Observer—complete with code examples, pros and cons, selection guidelines, and interview‑ready explanations to help candidates impress interviewers and secure offers.
This article explains the design and implementation of a generic asynchronous processing SDK for Java, covering its purpose, advantages, core principles, component choices, design patterns, configuration via Apollo, usage steps, safety considerations, and provides complete SQL and Spring configuration examples along with a GitHub repository link.
The article demonstrates how Claude 4.5 combined with Nano Banana Pro can automatically generate detailed design diagrams and analysis of Apache JMeter’s layered architecture, design patterns, extensibility mechanisms, and distributed execution model, showcasing the power of large‑model‑driven architecture inspection.
The article shows how tangled if‑else login code caused by adding password, SMS, WeChat, and Alipay authentication can be refactored using the Strategy and Factory patterns in Spring Boot, resulting in a clean, extensible, plug‑in‑style login module that requires no changes to existing code when new methods are added.
This article explains how to integrate a Human‑In‑The‑Loop (HITL) mechanism into ReactAgent, detailing the motivation, design of interaction, tool description, XML‑based UI rendering, Redis‑driven waiting loop, and the broader architectural parallels with design patterns and other agent frameworks.
A recent production incident caused duplicate order IDs due to a flawed custom Snowflake implementation, prompting a deep dive into the standard algorithm, analysis of the mistakes, and a set of best‑practice recommendations for designing robust distributed ID generators.
This comprehensive tutorial explains JUnit's definition, core components, annotations, assertion methods, test suite creation, custom test rules, and how common design patterns such as Factory, Decorator, Strategy, and Template Method can be applied to write flexible, maintainable Java unit tests, plus installation steps and advanced usage tips.
This article explains Java's static nested classes, covering their definition, key characteristics, sample code for an e‑commerce order model, and common scenarios such as helper utilities, callbacks, singletons, and data‑structure encapsulation.
This guide walks you through designing a scalable login module that supports dozens of authentication methods by combining the Strategy and Factory patterns with Spring Boot, providing clean code, easy extensibility, and robust testing without the tangled if‑else spaghetti.
This article examines how early PHP developers often wrote tangled, procedural code that mixes business logic with presentation, and outlines concrete steps—adopting OOP, design patterns, domain‑driven design, test‑driven development, and modern tooling—to shift toward a cleaner, more maintainable backend development approach.
The article shares eye‑opening ByteDance campus salary data, breaks down salary tiers, and then provides detailed interview preparation covering design patterns, HashMap concurrency pitfalls, MySQL indexing rules, query optimization, handling large JSON fields, stock‑decrement bottlenecks, RabbitMQ vs RocketMQ differences, and distributed‑transaction strategies.
This article explains how AIoT‑era embedded devices evolve from simple C/assembly code to reusable, portable frameworks by applying design patterns such as the Observer pattern and a custom responsibility‑chain model for low‑power management, complete with code examples, memory‑pool handling, and test cases.
This article breaks down Spring’s layered architecture and walks through ten core design patterns—factory, singleton, proxy, template method, observer, adapter, decorator, strategy, chain of responsibility, facade, and delegate—showing how they appear in real interview scenarios and how mastering them can turn a tough interview question into a winning advantage.
This article provides a comprehensive technical walkthrough of Tomcat, covering its connector and container architecture, lifecycle management, key design patterns such as Composite and Template Method, custom class‑loading mechanisms, hot‑reload process, and includes essential code snippets and diagrams for developers.
The article examines how MyBatis leverages around ten classic design patterns—grouped into Creational, Structural, and Behavioral categories—to decouple complex ORM logic, describing each pattern’s role, typical usage scenarios, and related components within the framework.
This guide explores key Go structural and architectural design patterns—Adapter, Decorator, Proxy, Bridge, Composite, Flyweight, Facade, Pipeline & Filter, Event Bus, Microkernel, and Dependency Injection—providing definitions, core ideas, Go implementations, and practical use cases to build scalable, maintainable systems.
This guide walks Go developers through essential creational and structural design patterns—Singleton, Simple Factory, Factory Method, Abstract Factory, Builder, and Facade—explaining their principles, Go implementations, pros and cons, and real‑world use cases to build scalable, loosely‑coupled systems.
This article explores four elegant design patterns—Strategy, SPI, Chain of Responsibility, and Rule Engine—explaining their concepts, advantages, and practical Java code examples to help developers replace tangled if‑else statements with maintainable, extensible solutions.
This article explains why traditional if‑else payment routing is hard to maintain, demonstrates how Java enums combined with functional interfaces and the strategy pattern can centralize behavior, improve extensibility, and integrate cleanly with Spring, providing a robust, testable solution for payment channel selection.
This article examines why excessive null‑checking clutters code, distinguishes when null is a valid response versus an error, and offers practical alternatives such as assertions, exceptions, returning empty collections, and the Null Object pattern to write cleaner, safer Java programs.
This article explains the fundamental differences between workflows and agents, introduces seven core design patterns—including three workflow patterns and four agent patterns—provides Python examples using Ollama, and shows how to combine these patterns to create robust, autonomous AI applications.
The article reveals Xiaohongshu’s unusually high 2023 campus recruitment packages—over 51 w annual total—while also providing an extensive backend interview preparation guide covering TCP vs UDP differences, design patterns, workflow versus rule engines, message‑queue selection, and Redis data structures and eviction policies.
This comprehensive guide explains why design patterns matter, links them to SOLID principles, enumerates the 23 classic GoF patterns with Java examples, compares commonly confused patterns, introduces modern architectural patterns, shows how they integrate with Spring, and offers a practical learning roadmap for developers.
This article presents over sixteen practical refactoring methods for Java, demonstrating how to replace tangled if‑else statements with clearer constructs such as early returns, ternary operators, switch‑case, guard clauses, optional handling, enums, reflection, strategy, and table‑driven approaches, each illustrated with concise code examples.
This guide shows how to replace verbose if‑else chains in JavaScript with cleaner techniques such as object mapping, Array.includes, ternary operators, logical shortcuts, switch statements, Proxy interception, functional patterns, state machines, and decorators, providing concise code examples for each method.
An in‑depth guide to microservice architecture explores its evolution, core characteristics, advantages and drawbacks, and walks through essential design patterns—Database per Service, Event Sourcing, CQRS, Saga, BFF, API Gateway, Strangler, Circuit Breaker, Externalized Configuration, and Consumer‑Driven Contract Testing—detailing when and why to use each.
Learn essential PHP object‑oriented programming techniques, including grouping data and behavior into classes, using access modifiers, initializing objects with constructors, chaining methods, and applying the strategy pattern, to boost code readability, maintainability, and flexibility.
This guide explains how to achieve clean decoupling in embedded software by employing a systematic layered architecture, leveraging event‑driven and pipeline‑filter patterns for data flow, and applying dependency injection, complete with practical C code examples and best‑practice recommendations for resource‑constrained devices.
This article showcases five recent UI/UX case studies—from Uber's waiting‑time game to Taobao's flash‑sale draw—illustrating how interactive design, gamification, data‑backed rankings, AI assistance, and clever reward mechanics can boost user engagement, reduce friction, and drive conversion across mobile products.
This article explains the Strategy (Policy) Pattern, illustrates its structure, and demonstrates a practical Spring-based implementation where different message types are processed by distinct strategy services, using an enum to map types to beans for flexible, interchangeable algorithms.
This article introduces the Strategy design pattern, explains its core concept of interchangeable algorithms, and demonstrates a practical Spring-based implementation that routes various message types to specific services using an enum‑driven bean lookup, enabling flexible updates to Elasticsearch for merchant search and analytics.
This article shares practical techniques for reducing verbose if‑else statements in Java, covering strategy‑enum patterns, ternary operators, Stream API methods, Map lookups, enums, and Optional, each illustrated with concise code examples to make conditional logic clearer and more maintainable.
This article compares traditional if‑else/switch‑case branching with the Strategy design pattern in embedded development, illustrating their differences through analogies and code examples, and explains when to adopt Strategy for better extensibility, lower coupling, and maintainability while noting scenarios where simple branching remains preferable.
This article explains how C++ implements polymorphism through virtual functions and vtables, covering static and dynamic polymorphism, memory layout, multiple inheritance, practical code examples, design‑pattern applications, and the importance of virtual destructors for safe resource cleanup.
This article outlines a step‑by‑step approach to mastering source‑code reading—starting from using the software, understanding its principles and architecture, learning its workflows, and finally dissecting implementations—to help developers answer interview questions and deepen their technical expertise.
Learn 15 practical code refactoring techniques—from extracting methods and introducing explanatory variables to applying design patterns like Strategy and Builder—that transform tangled Java code into clean, modular, and maintainable solutions, boosting readability and simplifying future enhancements.
This article explains why many PHP developers misuse Dependency Injection, outlines typical misconceptions such as equating DI with container usage, over‑reliance on constructors, and ignoring abstractions, and then provides concrete, testable solutions and best‑practice guidelines.
This article explains how to design a contract‑signing workflow in Java using the Chain of Responsibility and Strategy patterns, covering the processing steps, project structure, annotation‑driven bean injection, and complete code examples for each component.
