1 views collected around this technical thread.
This article explains how to design a consistent JSON response format for backend APIs, covering status‑code conventions, message handling, data payloads, a Result wrapper class, controller implementation, a @ResponseResult annotation, interceptor logic, and suggestions for further optimization.
This article explores how rapid AI tool advancements are reshaping designers' roles from repetitive executors to strategic creators, offering practical workflow integrations, essential skills to stay competitive, and a forward‑looking mindset for thriving in the AI‑driven design era.
This article narrates the messy history of API design, illustrating early AJAX conventions, the misuse of HTTP status codes, the challenges of maintaining Restful standards, ad‑hoc extensions, and the eventual abandonment of Restful in favor of a simplified POST‑centric approach, while highlighting practical lessons for backend developers.
This article outlines the rapid growth of AIGC technologies, describes key image‑generation and language models, demonstrates step‑by‑step design workflows, explores user‑experience research enhancements, and envisions future business uses while offering practical tips for mastering AI‑generated content.
When designing AI products, choosing between a Language User Interface—leveraging speech recognition, NLP, and conversational flexibility—and a Graphical User Interface—relying on visual icons, layouts, and intuitive interaction—depends on technology maturity, response speed, and user learning cost, while emerging multimodal designs increasingly blend both for richer, context‑aware experiences.
This article explains how to design a unified API response format for backend services, covering JSON structure, status code conventions, message handling, data payload, a Result wrapper class, controller simplifications, custom annotations, interceptors, and global exception handling to achieve clean and maintainable code.
This article critiques the Volcengine Python SDK's convoluted request‑signing design, demonstrates the problems with its custom classes and static methods, and proposes cleaner solutions using the requests library's AuthBase and Session mechanisms to simplify signing and improve maintainability.
This article outlines the JD Insurance UED team's recent explorations and achievements in leveraging AIGC technology to transform creative design workflows, highlighting key insights, visual examples, and recommended readings to inspire broader adoption of AI‑generated content tools across the industry.
This article walks designers through three progressive stages—Guard, Break, and Leave—to understand why data matters, how to select and apply it effectively, and how to avoid common pitfalls like Simpson's paradox, ultimately turning data into a strategic tool rather than a constraint.
The article presents the design principles, architecture, implementation details, and operational practices of Meituan's Business Correctness Verification Platform (BCP), a backend system that ensures data integrity and correctness across the company's services.
Between 2022 and 2023 the Taobao design team shifted from traditional 3D modeling to AI‑generated avatars, cutting costs and project time by up to 60%, expanding creative output by 150%, redefining designer roles, standardizing tools on the internal “Taobao Design AIGC” platform, and outlining future AI‑assisted workflow and quality standards.
The article examines why every business system accumulates technical debt over time, outlines the stages from initial creation to maintenance decay, analyzes the human and architectural factors that make legacy systems hard to work with, and proposes domain‑modeling and disciplined engineering practices to mitigate and delay that decay.
The article outlines the complete solution‑architecture lifecycle, describing each phase—from problem identification and context definition through requirements capture, backlog creation, detailed design, implementation choices, and production delivery—while emphasizing the architect’s role in aligning technical and business goals.
This article explains how MySQL indexes work, compares clustered and non‑clustered indexes, outlines their advantages and disadvantages, and provides practical design guidelines to improve query performance and maintainability.
Business systems accumulate technical debt as rapid growth, pseudo‑agile practices, unclear requirements, and staff turnover introduce hidden complexity, but systematic domain modeling, thorough analysis, disciplined design, and continuous learning can mitigate decay, keep code maintainable, and sustain developer motivation.
The article traces the historical evolution of front‑end frameworks—from static pages and jQuery to modern component‑based libraries like React, Vue, and Svelte—explaining why added complexity and compile‑time features such as Svelte’s runes improve maintainability, reactivity, and cross‑platform capabilities while weighing each framework’s design philosophy and trade‑offs for developers.
Fundamentals of color theory explain how light creates the visible spectrum, how additive (RGB) and subtractive (CMY/K) mixing generate colors, describe traditional pigment systems and Japan’s PCCS matrix, detail digital models such as RGB, CMYK, HSV and Lab, compare their gamuts, and illustrate commercial uses like Pantone’s standardized swatches for branding.
This article provides a comprehensive overview of API gateways, covering their basic concepts, design considerations, key features such as routing, load balancing, resilience and security, and compares popular implementations like OpenResty, Kong, Zuul, and Spring Cloud Gateway.
This article explains the three-stage design of a QR code login system—including pending scan, scanned‑pending‑confirmation, and confirmed phases—detailing how unique QR IDs, token exchange, and user confirmation ensure secure authentication across PC and mobile devices.
This article presents a detailed checklist of mandatory and recommended standards for database security, design, naming, indexing, SQL usage, and operational procedures, aiming to prevent low‑level failures in high‑concurrency, large‑scale internet applications.