1 views collected around this technical thread.
This article explains how to determine whether an integer array contains any duplicate values by iterating through the elements, using an associative map in PHP to track occurrences, and returning true if a repeat is found or false otherwise, including code examples and analysis of time and space complexity.
This article explains the principles of queues and stacks, demonstrates how to simulate a FIFO queue using two LIFO stacks in PHP, provides full source code, usage examples, complexity analysis, and discusses practical applications and possible extensions.
This article provides a detailed introduction to common sorting algorithms—including bubble, selection, insertion, shell, merge, quick, heap, counting, bucket, and radix sorts—explaining their principles, time complexities, stability, and offering complete Python implementations with step-by-step explanations and visual demonstrations.
This article outlines twelve leverage points for system transformation, ranging from simple parameter adjustments to paradigm‑shifting rule changes, and illustrates each with real‑world Chinese policy examples, helping readers choose the most effective intervention for social, economic, or environmental challenges.
This article explores eight common system‑thinking traps—such as policy resistance, the tragedy of the commons, goal erosion, and rule avoidance—and offers practical strategies to transform these pitfalls into opportunities for wiser, more holistic decision‑making.
Mathematical modeling thrives on useful approximations rather than flawless precision, as illustrated by Keynes’s economic insights, Box’s famous quote, and real‑world examples like weather forecasting and epidemic models, showing that simplified, “good enough” models often provide more actionable guidance amid complexity and uncertainty.
Drawing on a decade of front‑end experience, the article explains why many developers mistakenly view front‑end work as simple, explores the hidden complexity of modern web technologies, cross‑platform development, and the importance of strong fundamentals, while urging respect for the role.
The article explains what software complexity is, classifies its types, describes the negative impacts of high business complexity, identifies common causes, and presents practical methods such as domain decomposition, layered architecture, structured decomposition, annotation, configurability, and coding standards to effectively reduce complexity.
This article explores system theory, architectural design, and complexity, presenting a structured view of systems, their characteristics, modeling approaches like 4+1 and C4, microservice concepts, and the Cynefin framework, offering developers practical insights to manage and evolve software systems effectively.
Aliaksandr Valialkin criticizes Go 1.23’s new iterator feature, arguing it adds hidden control‑flow, memory overhead and readability challenges to an already minimalist language, and warns that such complexity undermines Go’s goals of simplicity, productivity, and performance.
This article explains essential software architecture concepts such as entropy and broken‑window effects, the sources and symptoms of complexity, the importance of orthogonality and consistency, and classic design principles like SOLID, DRY, and layered abstraction to guide architects in building maintainable, flexible systems.
The article explains that good software architecture must be deliberately designed and continuously refactored to combat entropy and the broken‑window effect, balancing behavior and architecture value while managing complexity through principles like Ockham’s razor, orthogonality, DRY, stable dependencies, layered abstractions, and clear boundaries, supported by UML visualizations.
This article examines the history, design motivations, and trade‑offs of modern frontend frameworks—covering Svelte’s new runes feature, the rise of component‑based architectures, template abstraction, cross‑platform compilation, and the differing philosophies of React, Vue, and Svelte—to explain why added complexity ultimately improves developer productivity and code maintainability.
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.
This article combines a light‑hearted Valentine’s Day introduction for programmers with a detailed presentation of the classic Two Sum problem, including problem description, constraints, example inputs and outputs, multiple language implementations, and a complexity analysis.
The article argues that complexity in software systems cannot be eliminated but only shifted, emphasizing the inevitability of leaks, the limits of local consequence, and the practical value of layering and eliminating duplication to make frequent changes easier and code more understandable.
The article argues that complexity in software systems is unavoidable and must be consciously placed, managed, and reduced through thoughtful architectural decisions, prioritizing high‑frequency changes, eliminating duplication, and accepting that perfect local consequences are impossible.
The article argues that complexity is an unavoidable aspect of software development and architecture, urging engineers to acknowledge, manage, and strategically place it rather than trying to eliminate it, while illustrating the trade‑offs in tooling, abstractions, and micro‑service design.
The article explains how the traditional VUCA model has become insufficient for describing today’s chaotic world and introduces the BANI framework—Brittle, Anxious, Nonlinear, Incomprehensible—as a more precise lens for interpreting modern volatility, uncertainty, complexity, and ambiguity.
This article introduces system thinking by defining systems and explaining its three core mindsets—deep, holistic, and dynamic thinking—while detailing causal loop diagram components, common reinforcing and balancing loops, and five foundational models that together help analyze interdependencies, uncover behavior patterns, and support wiser decision‑making.