This article explains the Dependency Inversion Principle, shows why traditional layered architectures suffer from maintenance and reuse problems, provides concrete Java and web examples, and demonstrates how refactoring to abstract interfaces resolves these issues for more flexible, decoupled software design.
This article explains what makes good code, introduces SOLID and other design principles, defines unit testing, outlines its benefits, provides before‑and‑after Java refactoring examples, and reviews essential testing tools like Fast‑tester, JUnit and Mockito along with coverage metrics.
This article explains how the six STEPPS principles—Social Currency, Triggers, Emotion, Public, Practical Value, and Stories—can be applied to product design to create compelling, memorable experiences that drive user engagement, word‑of‑mouth promotion, and stronger brand influence.
This article shares the author's insights on why engineers and leaders must conduct code reviews, identifies common causes of poor code such as duplication and premature decisions, and presents a set of design principles, model‑driven thinking, and concrete Go code examples to help improve software quality and maintainability.
This article explores why massive distributed applications quickly become complex, identifies cognitive load and collaboration cost as the two main dimensions of software complexity, and offers practical design, naming, testing, and documentation strategies to keep systems maintainable over time.
This article traces the history and development of pandemic data visualization—from 19th‑century cholera maps and early 2000s SARS charts to sophisticated COVID‑19 dashboards—while outlining five essential design principles that make such visualizations clear, engaging, and impactful.
The article explains why having constructors perform excessive work is a design flaw, describes how to spot this problem through code symptoms, discusses its impact on testability and maintainability, and provides concrete refactoring strategies such as dependency injection, factories, and builder patterns.
This article explores the importance of code review for engineers and leaders, examines common pitfalls such as duplicated code and premature optimization, presents core software design principles like KISS and composition, and offers practical guidelines and Golang examples to improve code quality and maintainability.
This article shares practical principles and concrete guidelines for effective code review and backend engineering, covering why reviews are essential, common pitfalls like duplicated code and premature optimization, design philosophies such as composition over inheritance, and actionable rules for maintaining clean, maintainable Go codebases.
This article explains what an architecture diagram is, why it matters, and provides a step‑by‑step methodology—including business and system modeling, abstraction techniques, and quality criteria—to create clear, purposeful diagrams for software projects.
The article argues that keeping software architects hands‑on with coding improves team communication, design accuracy, tool awareness, and product ownership, while highlighting the pitfalls of architects staying away from code and offering practical solutions for better collaboration and architecture evolution.
This article explains the core benefits, essential design principles, and common limitations of microservice architecture, offering practical guidance on functional scope, cohesion, API integration, data isolation, traffic management, automation, and monitoring to help teams build scalable, resilient software systems.
This article explains the six core object‑oriented design principles—Single Responsibility, Open/Closed, Liskov Substitution, Dependency Inversion, Interface Segregation, and Law of Demeter—detailing their definitions, benefits, and Java code examples to illustrate proper application.
This article explores the essential constraints of logical architecture, discusses software design principles and patterns for reuse, examines various reuse strategies, and details how logical architecture can be layered and partitioned across different granularities to improve maintainability, scalability, and efficiency.
This article outlines how to create solid software architectures by presenting a process for forming design principles, detailing fifteen universal architecture guidelines, and explaining service‑splitting and key design rules that together help build scalable, maintainable, and resilient systems.
This article explains the concept of microinteractions, outlines their four essential components—trigger, rules, feedback, and loop/pattern—provides design guidelines for each, and illustrates the ideas with practical case studies from BaseUI, Meitu XiuXiu, and Snapseed, highlighting how thoughtful micro‑interaction design enhances user experience.
This article explains what onboarding (new‑user guidance) is, why it matters for reducing friction, outlines seven core design principles, presents six reusable design patterns, and shows how advanced applications like Taobao’s Gold Coin feature apply these concepts to improve retention.
The article announces Ant Design 4.0, outlines its new design specifications, component rewrites, and reduced bundle size, then delves into the underlying philosophy of "happy work" by presenting core design assumptions, value propositions, and the shift from traditional WIMP interfaces toward more natural, proactive user interactions.
This article showcases ten award‑winning children’s product designs—from color‑changing bottles to convertible cribs—while outlining essential design principles such as safety, age‑appropriateness, fun, motivation, feedback, challenge, exploration, and fault tolerance to guide creators in delivering superior experiences for young users.
This article explores the fundamentals of architecture and model thinking, defining their core elements, principles, and roles, and shows how architects and model thinkers use structured frameworks and abstract models to identify contradictions, devise optimal solutions, and guide system improvement across software, organizations, and broader contexts.
This article distills the core concepts of the book “Clean Architecture,” outlining software system value, architecture goals, programming paradigms, design principles such as OCP, SRP, DIP, and practical guidelines for component splitting, dependency handling, and boundary design to build maintainable systems.
This article explains three core design principles—consistency, fault tolerance, and readability—showing how they reduce learning costs, prevent user errors, and improve text clarity, ultimately making designs more persuasive and user‑friendly.
This article compiles twenty core design theories and psychological principles—from Nielsen's usability heuristics to Maslow's hierarchy, Fitts's law, the Kano model, and the aesthetic‑usability effect—providing UX designers with a comprehensive toolkit to justify design decisions and create more intuitive products.
The article explains how leading tech companies like Uber and Skype design massive systems using simple, informal diagrams and collaborative documentation instead of formal architecture tools or dedicated architects, emphasizing simplicity, team autonomy, and practical trade‑offs over rigid patterns.
This article explains the distinction between software design and architecture, outlines core principles for building service‑oriented systems, provides a step‑by‑step method for creating new services, and shares practical strategies for refactoring and migrating legacy code without creating future technical debt.
This article presents a comprehensive graphic design learning plan that covers the four fundamental design principles, the role of proportion and grid systems, the effective use of point, line, and plane, and practical tips with visual examples to help designers build a solid design foundation.
This article explains why accurate, clear, and elegant visualizations are essential, compares popular tools such as Excel and Tableau, outlines how to choose the right chart and visual encoding, discusses design principles like Gestalt laws and cognitive load, and shows a step‑by‑step case study of improving a capital‑budget chart.
This article introduces the six fundamental object‑oriented design principles—SRP, OCP, LSP, DIP, ISP, and LoD—explains their definitions, benefits, and real‑world Java examples, and shows how they together form the SOLID guidelines for clean software architecture.
This article presents thirty practical software architecture principles—covering simplicity, YAGNI, iterative development, automated testing, ROI, user focus, modularity, statelessness, concurrency, CAP theorem, and more—to guide architects in building scalable, maintainable, and user‑centric systems.
The article explains how modular design leverages cognitive psychology—highlighting the brain's limited information‑processing capacity—to simplify complex products, improve user comprehension, and reduce development costs, using real‑world examples from everyday life and product development.
This article distills the core ideas of "Clean Architecture"—explaining software system value, architecture goals, programming paradigms, design principles, component splitting, dependency handling, and boundary management—to help engineers build maintainable, extensible systems that stand the test of time.
This article explains the four core graphic design principles—contrast, repetition, alignment, and proximity—and shows how applying them to financial product interfaces improves readability, influences price perception, builds trust, and guides user behavior through thoughtful visual hierarchy and currency presentation.
iOS developers should learn Android to broaden their skill set, grasp the component‑centric design philosophy and core elements like Activities, Services, Intents and Manifest files, and stay competitive in the big‑front‑end era where cross‑platform frameworks demand fluency in both iOS and Android ecosystems.
This article outlines three core architecture design principles—appropriateness, simplicity, and evolution—illustrated with Taobao’s journey from a simple PHP site to a sophisticated, self‑developed distributed system, showing how fitting solutions, keeping designs simple, and iteratively evolving with business needs lead to sustainable scalability.
The article explains essential object‑oriented design principles—SOLID for class design and six package‑level rules—showing how proper dependency management and modular organization create flexible, reusable, and maintainable software, and why developers must understand these concepts beyond basic procedural programming.
This article explains the six SOLID design principles—Single Responsibility, Liskov Substitution, Dependency Inversion, Interface Segregation, Law of Demeter, and Open‑Closed—using iOS‑oriented examples, code snippets, and practical advice to help developers write cleaner, more maintainable software.
This article explains how to formulate an architecture vision and goals, outlines the hierarchical levels of vision from system-wide to code-level, describes the process of deriving vision from requirements, and details quality attributes and design principles for effective software architecture.
Discover 15 timeless architecture principles—from redundancy and rollback design to monitoring, horizontal scaling, and non‑intrusive components—that guide engineers in creating robust, scalable, and maintainable systems while balancing cost, risk, and future growth.
The article explores how rapid business growth and evolving technology have turned software from a deterministic, document‑driven process into a continuously changing infrastructure, urging a shift toward internal determinism, documentation‑as‑code, and object‑oriented business design.
Microservice architecture, likened to the human body's independent systems, breaks monolithic applications into loosely‑coupled, high‑cohesion services with isolated data stores and well‑designed APIs, enabling flexibility, scalability, and continuous delivery, while requiring careful scope definition, automation, monitoring, and handling of added DevOps complexity.
This article explains what software architecture is, why it matters for growing teams, outlines key responsibilities, presents practical best‑practice diagrams and decision criteria, and offers guidance on how engineers can evolve into effective architects.
This article explains what software architecture means, outlines how to start designing an architecture that aligns with business needs, describes the key characteristics of a good architecture, highlights common misconceptions, and offers concluding advice for architects seeking practical, business‑driven design guidance.
This article explains what software architecture is, why it matters for growing teams, outlines common challenges, presents best‑practice modeling techniques, offers criteria for boundary and middleware decisions, describes characteristics of a good architecture, and outlines how to grow into an architect role.
This article outlines the ADMEMS approach’s ten essential guidelines for robust graph modeling, covering rules, simplified syntax, discovery of responsibilities, incremental modeling, and practical tips to avoid over‑detailing, helping designers create clear preliminary designs for complex systems.
This article explains the purpose of software architecture design, identifies sources of complexity such as performance, availability and scalability, outlines three guiding principles—appropriateness, simplicity, and evolution—and presents a practical step‑by‑step design process illustrated with diagrams.
This article summarizes the core object‑oriented design principles—including SOLID, the Law of Demeter, and composition/aggregation reuse—explaining their definitions, analyses, advantages, and real‑world examples to help developers write more maintainable and extensible software.
This article summarizes key object‑oriented design principles—including the SOLID rules, Dependency Inversion, Interface Segregation, Composite/Aggregate Reuse, and Law of Demeter—explaining their definitions, analyses, advantages, and practical examples such as Spring MVC component separation and Java code illustrations.
This article explores software architecture fundamentals, covering object‑oriented design principles, SOLID, DRY, KISS, logical vs. physical layers, service and business logic layers, SOA, data access strategies, stored procedures, and the MVC pattern, providing practical insights for building maintainable systems.
This article explores how careful font selection, Chinese‑Western typeface separation, punctuation spacing, and the four core design principles of proximity, alignment, repetition, and contrast together create clear, visually appealing typography for both small and large text blocks.
This article summarizes Red Hat's cloud‑native container design principles, explains each rule—from single concern to runtime confinement—shows how they extend classic software design concepts, and provides practical best‑practice tips and reference links for building resilient, observable, and immutable containerized applications on Kubernetes.
This article compares B‑end (B2B) and C‑end (B2C) products, explaining their core nature, characteristics, usage scenarios, and offering practical design considerations for each, highlighting how sharing drives consumer apps while collaboration drives enterprise solutions.
This article explains the six core SOLID principles, introduces additional design guidelines such as composition, acyclic dependencies, and Hollywood principle, and lists other essential software design rules like DRY, KISS, high cohesion, and separation of concerns to help developers build robust, maintainable systems.
This article explains the microservices architecture style, compares it with monolithic and SOA approaches, outlines design principles, communication mechanisms, data decentralization, integration patterns, and discusses the advantages and disadvantages of adopting microservices in modern software systems.
This article explains how psychological and physiological responses drive the need for balanced color schemes, covering cold‑warm relationships, complementary colors, light‑dark gradients, and black‑white‑gray harmony, and provides practical tips and visual examples for designers.
This article explores how habit‑forming product design leverages behavioral psychology, the habit loop, and the Fogg model to persuade users, reward actions, and encourage investment, offering practical frameworks for creating engaging, habit‑driving digital experiences.
This article shares a designer’s three‑year experience creating live‑streaming features for an education platform, outlining the end‑to‑end workflow, key design considerations before, during, and after broadcasts, and practical principles for balancing user needs, technical constraints, and product goals.
This guide explains why onboarding matters, outlines its three core functions—greeting, information delivery, and engagement—and provides practical design tips such as prioritizing content, using custom illustrations, concise copy, animation, clear pagination, and optional skip options to create a smooth first‑time user experience.
The article outlines 17 essential questionnaire and interview design principles—covering question wording, option construction, and interview conduct—to help designers conduct reliable user research and obtain objective, actionable insights.
This article demystifies Jakob Nielsen’s ten usability heuristics, translating each principle into clear, actionable advice with examples and visuals to help beginners understand how to create intuitive, error‑resistant user interfaces.
This article explains why visual hierarchy is crucial in interface design, outlines four key dimensions—size, spacing, content form, and color—and demonstrates their application through real‑world case studies that improve user focus and reduce cognitive load.
This article explains why merely meeting product metrics isn’t enough, advocates adding emotional connection and “soul” to designs through purposeful principles, fun elements, the KANO model, and persuasive communication with stakeholders, offering concrete examples and actionable guidelines for product designers and managers.
This article explores the evolution of intelligent voice interaction—from its roots in natural language processing and early products like Siri to its potential to become a primary human-computer interface, discussing technical challenges, design principles, comparative advantages over graphical interfaces, and suitable application scenarios such as automotive, education, and customer service.
SOA design should stay as simple as possible, guided by nine core principles—including standardized contracts, loose coupling, abstraction, reuse, autonomy, statelessness, discovery, composition, and collaboration—that together ensure robust, reusable, and maintainable services across enterprise systems.
In an era of information overload, this article explores how emotional and psychological principles—instinct, behavior, and reflection—drive user experience design, illustrating the three layers of emotional design with examples from UI elements, emojis, and game interfaces, and showing how both positive and negative emotions can be leveraged to create more intuitive and engaging products.
This article summarizes key software design principles such as DRY, KISS, SOLID, New Jersey style, Separation of Concerns, and YAGNI, explaining their meanings, benefits, and practical code examples for writing cleaner, more maintainable code.
The article explains why programmers need to create clear technical diagrams, how diagramming enhances abstract thinking, communication, and problem‑solving, and provides practical guidance on shapes, colors, aesthetics, and tool choices to produce effective architecture visuals with minimal effort.
In this article, Baidu senior UX manager Wang Wentao shares his career background, explores why designers need authority, presents core design principles illustrated with registration page case studies, and answers practical Q&A on user experience, design processes, and future trends.
This article shares Facebook’s four design principles for B2B products—helping users grow, balancing efficiency with effectiveness, turning complexity into simplicity, and delivering precise predictions—illustrated with real‑world examples, A/B test results, and the evolution of their advertising platform.
The article explains how designing products around user behavior—considering hardware dimensions, emotional factors, habits, and subconscious cues—creates more intuitive, adaptable solutions than purely user‑centric methods, and outlines practical principles for applying behavior‑centered design in everyday objects.
This article explains Google App Engine's core design philosophies—including reuse of Google technologies, statelessness, hard limits, Protocol Buffers for service heterogeneity, and distributed storage—then details its front‑end, Datastore, service group, language‑specific implementations, and a typical HTTP request flow.
This article explores how designers creatively repurpose everyday shadows to enhance visual hierarchy, depth, and user experience in user interfaces, illustrating the concept through a series of striking examples that demonstrate practical techniques and design principles.
This article introduces Java developers to essential object‑oriented design principles—including DRY, encapsulation, Open/Closed, SRP, DIP, composition over inheritance, LSP, and Interface Segregation—explaining their benefits, proper usage, and common pitfalls to help write high‑cohesion, low‑coupling code.
The article outlines practical principles for designing scalable software, covering reduced processing time, partitioning, concurrency, clear requirements, continuous testing, architecture‑first thinking, and a global view to ensure systems can handle more users, work, and data efficiently.
This article explores the concept of Exformation and demonstrates how strategic whitespace can enhance web design through ten curated examples, illustrating minimalist aesthetics, focus on content, and creative visual balance for modern websites.
This article outlines twenty fundamental principles of user interface design—from clarity and interaction focus to visual hierarchy and cognitive load reduction—providing actionable guidance that helps frontend developers create intuitive, efficient, and aesthetically balanced digital experiences.
This article explores how designers can strike a balance between minimalistic aesthetics and functional complexity in mobile app form design, covering reductionist approaches, eye‑catching UI techniques such as blurred and dark backgrounds, clear visual flow, and user‑experience strategies that reduce input, provide helpful prompts, and minimize forced actions.
Splash screens in Android apps, especially in many Chinese releases, waste startup time, disrupt users’ task focus, consume unnecessary resources, and replace better branding options, so modern hardware and design guidelines recommend eliminating them to improve speed, flow, and overall user experience.
This guide details Google Glass’s user interface components, design principles, common patterns, and visual style, covering timeline organization, dynamic and static cards, voice interactions, immersion mode, layout grids, color palettes, typography, and copy best practices for creating effective Glass applications.
This article explores the design principles, user‑experience guidelines, and real‑world examples for creating effective Google Glass applications, emphasizing context‑aware simplicity, non‑intrusive notifications, timeliness, and safety to help designers craft compelling wearable interfaces.
This article outlines six fundamental UI design guidelines—clarity, simplicity, familiarity, responsiveness, consistency, and visual appeal—to help designers create interfaces that enhance user experience and improve the success of web projects.
LeTV’s chief designer shares how quantifying user experience, embracing large‑sample data, and designing for cross‑device consistency can turn video streaming into measurable value, while emphasizing subtle, natural interactions that keep users engaged across PC, mobile, and TV platforms.
This article shares a curated reading list and resource guide for product managers, explaining how personal mindset, industry knowledge, strategic insight, interaction design, and fresh perspectives shape effective product leadership and recommending specific books, reports, podcasts, and platforms to explore.
Fool‑proof (poka‑yoke) design uses intuitive constraints, sensory cues, and proactive feedback to eliminate mistakes for non‑expert users, offering practical examples from everyday objects to digital interfaces and outlining six interaction strategies that keep users focused and error‑free.
This article presents a reflective set of ten guiding principles for user experience strategy, exploring its origins, challenges, and practical commandments that help UX strategists align business goals, ethical considerations, and human‑centered design to drive sustainable value.
