This article outlines practical learning mindsets, systematic study methods, deliberate practice techniques, and coding habits that can help software engineers accelerate their growth and become technical experts within three years.
This article outlines fourteen common algorithmic patterns that appear in programming interviews, explains how to recognize each pattern, and provides example problems for each, helping developers focus their preparation and solve interview questions more efficiently without endless brute‑force practice.
This article compiles lessons from various engineering blogs on why and how to conduct code reviews, covering their role in quality assurance, team learning, pull‑request preparation, constructive communication, and the importance of praise and positive tone.
The article challenges typical criticisms of Lombok—JDK compatibility, forced adoption, reduced readability, increased coupling, and perceived technical debt—by providing counter‑arguments that emphasize stable JDK usage, minimal learning curve, alternative Lombok features, and the practicality of the library in modern Java development.
Celebrating International Women’s Day, this article chronicles the pivotal contributions of female computing pioneers—from Ada Lovelace’s first algorithm and Grace Hopper’s COBOL legacy to Anita Borg’s advocacy, Joyce Weibecker’s early games, Margaret Hamilton’s Apollo software, and the six ENIAC programmers—highlighting their lasting impact on technology.
This article shares interviews with six iQIYI female engineers—from a junior algorithm specialist to senior managers—highlighting their career paths, workplace culture, gender‑related challenges, and practical advice for women pursuing tech roles in China’s fast‑growing industry.
This article outlines fourteen common algorithmic patterns—such as sliding window, two pointers, fast‑slow pointers, interval merging, cyclic sort, in‑place list reversal, BFS/DFS on trees, two‑heap, subsets, modified binary search, top‑K, K‑way merge, and topological sort—explaining when to use each, how they work, and example problems to help developers prepare efficiently for technical interviews.
Although intuition suggests that adding more developers speeds up delivery, software projects often suffer longer cycles due to communication overhead and coordination costs; the classic ‘Mythical Man-Month’ explains why a small, skilled team can be more productive than a larger, less coordinated one.
This article explains the importance of comments in C/C++ code and provides detailed guidelines for file, function, variable, spelling, and TODO annotations, including examples and best‑practice recommendations to improve code readability and maintainability.
In this reflective guide, a newly appointed CTO shares his career timeline, defines the CTO role, adapts a proven framework, and outlines fourteen practical lessons—from self‑belief and time management to delegation, handling chaos, and making smart decisions—to help technology leaders thrive.
This article explains why many technical proposals feel shallow, defines breadth and depth characteristics, introduces a four‑part methodology (essence, contradiction, system, evolution), and demonstrates its application through three concrete solution case studies.
This article details how iQIYI Knowledge's web frontend team designed and implemented a comprehensive componentization strategy that improves code reuse, development efficiency, and maintainability across numerous independent projects while ensuring product consistency.
The Linux 5.8 kernel, despite its record‑breaking size, remains maintainable thanks to a disciplined Git‑based workflow that follows seven fundamental principles, continuous testing, and a culture of trust that together set a gold standard for large‑scale open‑source development.
This article humorously explains 22 classic software design patterns—such as Factory Method, Builder, Abstract Factory, Prototype, Singleton, Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Chain of Responsibility, Command, Interpreter, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, and Visitor—by likening each to everyday dating and food scenarios, making the concepts easy to grasp.
This article profiles fourteen of the most renowned programmers worldwide, detailing their reputations, major achievements, and how the tech community perceives them, with each entry highlighting their contributions to software development, algorithms, open‑source projects, and computing history.
Drawing on years at Alibaba, the author shares insights on top‑level design, physical and application architecture, the evolving role of architects, and the essential skills—problem discovery, definition, solution, communication, breadth, and continuous learning—required to tackle complex, global system challenges.
A recent discovery reveals that Apple’s open‑source file make_tapi_happy.h includes a humorous "only god knows why" comment about WeChat compatibility, highlighting how business negotiations can leave quirky traces in source code.
This article explains why comments are essential for code readability, outlines consistent comment styles, details file, function, variable, spelling, and TODO annotations, and provides practical examples to help developers write clear, maintainable C/C++ documentation.
The biggest challenge for software engineers isn’t writing code but continuously questioning requirements, clarifying details, uncovering the real problem behind requests, and understanding the people behind the system, a mindset the article calls “upstream thinking.”
This article shares practical insights from a technical leader on designing robust system architecture, implementing comprehensive capacity planning, establishing reliable operations processes, strengthening security, and cultivating team awareness to achieve long‑term stability for large‑scale internet services.
This guide offers test developers actionable habits—from writing pseudo‑code and breaking tasks into manageable items to mastering version control, refactoring, commenting, solution hunting, embracing change, and automating repetitive work—to become more efficient and maintainable engineers.
The article shares a solution architect’s practical experience with microservice architecture, outlining five key insights, the cultural shift toward product‑centric teams, challenges of transitioning from monoliths, and why microservices, while powerful, must be adopted only after careful business evaluation.
A senior architect learns why he remains stuck while his former colleague climbs the ladder, discovering eight actionable habits—from reading all code and judging project direction to mastering meetings, version control, and pragmatic coding—that can transform technical expertise into real career advancement.
Brad J. Cox, co‑creator of Objective‑C and a pioneer in software reuse, passed away in 2021, leaving behind a rich personal history, influential publications, and a programming language that shaped Apple's ecosystem before gradually yielding to Swift.
This article showcases fourteen of the most renowned programmers worldwide, presenting their key achievements, notable honors, and memorable community quotes, while providing images that illustrate each legend's impact on software development, open source, and computer science.
This article shares practical insights and principles—from the importance of code review to concrete guidelines like KISS, composition, and transparency—helping developers write higher‑quality, easier‑to‑maintain software while avoiding common pitfalls such as duplication, premature optimization, and over‑engineered designs.
This article explores the essential reasons why engineers and leaders must practice code review, outlines common pitfalls such as duplicated code and premature optimization, and presents concrete design principles, model‑driven thinking, and Unix‑inspired guidelines to improve code quality and maintainability in large‑scale backend systems.
This article recounts a twelve‑year‑long French government software project that amassed over six million lines of C++ code, suffered from outdated technology, chaotic version control, absurd management policies, and ultimately collapsed, offering stark lessons for developers and project leaders.
This satirical guide lists seven counterproductive tactics—like hiring big‑company talent for a startup, misusing agile, ignoring proper role ratios, over‑managing, false startup culture, line‑count performance metrics, and unnecessary middle‑platforms—that can cripple a small software team.
This article examines iQIYI's low-code Quqiao platform for data synchronization, detailing the software engineering background, business data flow, development challenges, research of existing solutions, platform architecture, key features, and future improvement directions.
The article examines common problematic comment styles—such as embedding contact info, design details, "how" instead of "why", usage instructions, and algorithm explanations—and suggests modern Git‑based practices to keep code clean and maintainable.
In this interview, Tencent front‑end lead Li Qinglong explains how low‑code platforms boost development efficiency, outlines when they’re advantageous, shares the IMWeb team’s evolution since 2015, and predicts a growing role for low‑code in both tech firms and traditional industries.
This article presents ten concrete Java refactoring techniques—from extracting duplicate code and splitting long methods to optimizing nested conditionals and removing temporary variables—each illustrated with clear before‑and‑after code examples and practical advice for improving code readability and maintainability.
Based on a sample of 352,948 programmers collected in January 2021, the nationwide average monthly salary was 14,915 CNY with a median of 12,500 CNY, and the report details city‑wise average wages and a comprehensive comparison of salaries across dozens of technical job functions between January 2020 and January 2021.
This article explores the core principles of clean code—from effective naming and expressive functions to purposeful comments and rigorous testing—illustrating how disciplined practices like meaningful identifiers, single‑responsibility functions, and the FIRST testing criteria can dramatically improve code readability, maintainability, and reliability.
This article explores how Test‑Driven Development and Google Test can improve quality and enable incremental refactoring of a complex, legacy online navigation system by addressing the shortcomings of traditional diff‑based testing, introducing unit‑testing fundamentals, and sharing practical implementation details and lessons learned.
This article examines why many developers hit income plateaus at junior, senior, and architect levels, identifies the specific technical and mindset bottlenecks at each stage, and offers concrete strategies to overcome them and accelerate career and salary growth.
This article presents a curated list of ten insightful resources covering Google’s OKR guide, code coverage best practices, code health principles, software product team efficiency metrics, unit testing responsibilities, quality assurance case studies, effective code review, Microsoft’s testing transformation, agile misconceptions, and related engineering topics.
This article presents a detailed overview of Alibaba's KAITIAN project, covering its background, multi‑layer technical architecture, plugin system, real‑world examples, its impact on frontend R&D workflows, and future trends of cloud‑native remote IDEs.
In 2020 Meituan’s tech team highlighted its eight most‑read technical articles—spanning Java thread‑pool design, mobile UI consistency, trillion‑scale KV storage, AI search estimation, Java GC troubleshooting, delivery A/B evaluation, ZGC tuning, and marketing design patterns—while also showcasing the most‑viewed posts, thanking 260,000 readers and inviting new talent for the coming year.
This article explains the concept, requirements, tool selection criteria, comparative analysis of Sonar, Infer and TscanCode, and practical integration steps—including CI pipeline, Jenkins, and project‑management linkage—to demonstrate how static code scanning can be effectively deployed and measured in a production environment.
This article explores why and when to refactor legacy projects, outlines common pitfalls such as missing functionality and inadequate testing, and offers practical guidance on assessment, testing, branching, feature toggles, and A/B testing to ensure a successful rewrite.
The article humorously outlines seven destructive tactics—such as poaching talent from big firms, misapplying agile, enforcing unrealistic role ratios, neglecting proper technical management, promoting false startup culture, using line‑count performance metrics, and building unnecessary middle‑platforms—to illustrate how to deliberately cripple a small‑to‑mid‑size tech team.
This article introduces the highly starred ‘developer‑roadmap’ repository, outlines its comprehensive learning paths—including frontend, backend, DevOps, Android, React, and PostgreSQL DBA—and provides a detailed breakdown of the backend learning roadmap, encouraging readers to use it as a key reference for their backend career development.
The article examines why many programmers face a steep career decline after age 35, explores the technical and managerial tracks available in large tech firms, and offers practical strategies for continuous skill growth, direction clarification, and leveraging experience to remain valuable in the industry.
The article reflects on how most members of technical teams are passively driven, examines the unsustainable management practices that try to force active drive, draws parallels with education and economic sustainability, and proposes a more balanced, sustainable team culture that respects individual differences and long‑term growth.
In this concise recap of Morgan's (程墨) talk at Peking University, a veteran software leader shares six career stories, key reflective questions, and practical insights on leaving jobs, becoming a senior engineer, aligning with company values, leading teams, and the essential role of integrity.
This article presents sixteen practical coding habits—from self‑testing and parameter validation to thread‑pool usage and cache consistency—that help developers avoid common bugs, improve reliability, and write cleaner, production‑ready code across backend systems.
The article offers practical guidance on preparing and delivering project experience during technical interviews, emphasizing confidence, detailed preparation, highlighting key achievements, avoiding common pitfalls, and strategically guiding interviewers to showcase relevant skills and technologies.
This article distills key recommendations from Effective Java, covering static factory methods, builder patterns, singleton safety, utility class design, object creation, memory management, garbage‑collection, equals/hashCode contracts, immutability, generics, enums, collections, exception handling, and performance‑aware coding practices for robust Java development.
This article lists ten common "toxic" Java code patterns—ranging from offensive method names and misleading sorting to hidden performance traps—and explains why they are harmful, how they affect maintainability and runtime, and what clean, efficient alternatives should be used.
This article outlines the scoring criteria used in interviewing.io mock interviews, highlights five frequent problems candidates face—such as coding too fast, half‑thought ideas, lack of clarifying questions, assuming all rules belong to the interviewer, and not seeking help early—and offers practical advice on communication, design, and practice to improve interview performance.
The article provides a concise overview of Google’s software engineering organization, detailing key roles such as engineering managers, software engineers, research scientists, SREs, product and program managers, and explains the performance, reward, and promotion processes that shape career development.
This article explains what code quality means, outlines its essential characteristics, discusses how to measure it with metrics and coverage, and introduces static analysis tools such as Checkstyle, PMD, and CPD to help Java developers maintain reliable, maintainable, and secure code.
The article presents a comprehensive guide on why developers and leaders must perform code reviews, identifies common pitfalls such as duplicated code, premature optimization and over‑engineered OOP, and offers concrete principles, model‑design advice, and Golang examples to improve code quality and maintainability.
This article provides a comprehensive overview of the 23 GoF design patterns, categorizing them into creational, structural, and behavioral groups, explaining each pattern’s purpose and core essence in a concise one‑sentence description, and includes visual diagrams to aid understanding.
This article compiles sixteen classic coding habits—from self‑testing changes and validating parameters to handling concurrency, cache consistency, and idempotency—providing practical guidance that helps developers avoid common bugs and improve overall software quality.
This article describes how a hotel pricing platform was refactored using Domain-Driven Design, detailing the strategic, tactical, and implementation phases that clarified domain boundaries, introduced a layered architecture, standardized processes, and delivered faster development, better maintainability, and improved operational visibility.
This article compiles sixteen classic Java coding habits—from self‑testing changes and validating method parameters to handling resources, avoiding runtime errors, and ensuring thread‑safety and cache consistency—providing practical guidance that helps prevent most non‑business bugs.
This article explains the importance of code review for improving code quality, fostering team knowledge sharing, enforcing consistent standards, and provides practical guidance on allocating time, choosing review formats, timing reviews, and setting clear expectations for reviewers and reviewees.
The CISSE 2020 conference in Guangzhou invites researchers to submit original English papers on communications, satellite links, big data, blockchain, embedded systems and software engineering before December 14, with peer review, publication in EI‑indexed proceedings, a writing workshop, and full contact information provided.
The article traces the evolution of software development—from early machine code and assembly, through high‑level languages, the first and second software crises, structured and object‑oriented programming, to the rise of software architecture in the 1990s—explaining the historical forces that shaped modern architectural design.
This article explains why refactoring is essential for maintaining legacy systems, defines refactoring as a controlled code‑restructuring technique that preserves observable behavior, and provides a step‑by‑step process—including when to start, when to stop, prerequisites, and practical tactics—to improve code quality and reduce technical debt.
The article presents a systematic, automated platform that captures, replays, and compares API requests using intelligent sampling and vertical/horizontal privilege checks to detect authorization flaws, dramatically reducing manual testing effort, uncovering over twenty issues monthly, and outlining future CI integration and AI‑enhanced detection.
This article analyzes the 2021 Robert Half salary guide, presenting average and percentile compensation for the 24 highest‑paying software development roles in the United States and comparing them with Chinese tech giants' salaries to reveal global market trends.
This article explains how layered thinking guides architecture design, covering cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA three‑tier models, the role of decomposition and integration, and practical layering patterns for technical, application, and functional architectures across various domains.
The article examines the common belief that programmers become obsolete after 35, analyzes four reasons behind this bias, and proposes two viable development routes—deep technical specialization and line‑level management—so senior engineers can continue to add value and grow.
This article outlines the three-stage journey from junior programmer to senior executive, detailing essential upgrades in goals, learning, thinking, perseverance, responsibility, action, collaboration, achievement, strategy, and influence, and provides practical guidance for engineers aspiring to become effective managers and leaders.
This guide outlines a multi‑stage roadmap for developers to grow into software coaches, covering essential Java fundamentals, agile practices, algorithms, testing, design patterns, JVM internals, distributed middleware, big‑data ecosystems, architecture design, performance tuning, and emerging fields like AI and IoT.
After the Double‑11 shopping frenzy, many developers grabbed new programming books, and this article curates the 25 most acclaimed titles—covering classic fundamentals, design patterns, algorithms, software craftsmanship, and career development—to help readers choose the most valuable resources for their growth.
Meituan’s tech leaders stress that mastering technical fundamentals—such as coding standards, design patterns, and testing—through continuous practice, rigorous standards, and regular reflection is essential for engineers to improve efficiency, quality, and long‑term career growth.
This article examines how Lombok reduces boilerplate in Java by generating getters, setters, equals, hashCode, and toString methods, but also introduces version compatibility issues, hidden dependencies, reduced readability, increased coupling, and potential technical debt for backend developers.
This article presents a practical approach to applying layered architecture and Domain‑Driven Design (DDD) to a Java‑based fresh‑food e‑commerce microservice system, outlining five layers, their responsibilities, design principles, domain partitioning tips, and common pitfalls to help engineers build maintainable, scalable back‑ends.
An irreverent translation of a classic tongue‑in‑cheek article enumerates absurd programming practices— from misleading variable names and deceptive comments to overloaded functions and chaotic testing— that deliberately make software hard to understand, maintain, or debug, serving as a cautionary parody for developers.
This article explains how companies at different development stages can identify talent needs, interview and hire the right people, and organize work to create truly efficient, non‑bullshit teams by mapping project phases, defining role levels and categories, and offering practical leadership and hiring advice.
This article explains practical code quality evaluation standards—coding conventions, readability, maintainability, duplication, and testability—and introduces the five dimensions used by Iceworks Doctor to score projects, helping teams adopt consistent, high‑quality coding practices.
This article explains how software architects can perform effective software design by modeling domain problems and system architecture, outlines the essential UML diagram types, and shows how to use them across requirement analysis, conceptual design, and detailed design to communicate and control development costs.
This guide outlines the essential knowledge, learning strategies, practical steps, and common pitfalls for aspiring full‑stack engineers, highlighting the advantages of mastering both front‑end and back‑end technologies and how this breadth improves development efficiency and cross‑team collaboration.
The article outlines practical guidelines for naming variables and methods—emphasizing clear intent, avoiding misleading or abbreviated names, leveraging IDE autocomplete, ensuring searchability, and maintaining consistent conventions—to improve code readability, maintainability, and overall software quality.
The article examines why many software engineering interviews rely on poorly designed algorithmic questions, outlines the essential technical and non‑technical competencies interviewers should assess, and proposes concrete criteria for crafting effective, open‑ended interview problems that reveal a candidate’s real engineering abilities.
Becoming a full‑stack engineer requires mastering core web fundamentals, continuously learning diverse languages, frameworks, and infrastructure, practicing rigorous design and code quality, and bridging front‑end, back‑end, and operations knowledge to boost development efficiency, solve problems quickly, and earn peer trust across the tech stack.
This article examines Lombok—a popular Java library that generates boilerplate code—by showing before‑and‑after examples, then detailing five major drawbacks such as JDK incompatibility, forced dependencies, reduced readability, tighter coupling, and overall cost‑benefit imbalance that can turn a seemingly elegant solution into a maintenance liability.
This article explores how software engineers can improve their work by clearly defining roles, applying systematic refactoring strategies, and enforcing quality through team consensus, testing practices, and a strong engineering culture, drawing on over two decades of industry experience.
This guide compiles an extensive collection of online tutorials, video courses, e‑books, official documentation, blog communities, and open‑source platforms covering front‑end, back‑end, mobile, database, cloud, and other fundamental programming topics, helping developers continuously learn and improve their skills.
This comprehensive guide walks you through the fundamentals of system design, covering core concepts, analytical thinking, modeling techniques, architecture classification, design tools, and best‑practice principles to help you build robust, scalable software systems.
In a Cloud+ community salon, three Tencent Cloud senior engineers dissect the three‑stage evolution of software architecture—from monolithic to distributed to AI‑driven—share the iterative design of Tencent Cloud Disk, outline request‑centric high‑availability metrics, advise systematic project takeover, and stress hands‑on learning, proactive incident response, and future‑ready practices while inviting talent to join.
This article explains how software architects can use UML modeling to capture domain problems and system designs, produce clear design documents, and communicate functional, non‑functional, and cost requirements across all stakeholders throughout the development lifecycle.
This article explains how to define appropriate software quality measurement goals, choose quantitative or qualitative methods, apply periodic and lifecycle‑wide metrics, and use visual dashboards to turn measurement data into actionable improvements throughout the development process.
This article explains why quality operation is needed for a transaction platform, describes the origin and problems that motivated the Quality Month, outlines a seven‑element operation plan with goals, strategies, resources, data collection, and evaluation, and shares the results and lessons learned.
This article reports on Tencent’s Gongfeng version‑control system receiving top‑level DevOps standard assessment at the 14th GOPS Global Operations Conference, includes an interview with the system’s director about its design, deployment challenges, future plans, and the broader Chinese DevOps standards initiative.
This article recounts how John Washam, a non‑CS graduate, self‑studied for eight months, created a popular GitHub interview guide with over 130 k stars, and leveraged flashcards, language selection, algorithm fundamentals, and interview tips to secure a six‑figure software engineering position at Amazon.
This article recounts an eight‑year journey from a C++ internship to senior roles at Alibaba and Ant Group, highlighting how mastering Node.js, embracing code review, unit testing, open‑source contribution, and continuous sharing can accelerate a software engineer's career.
In this personal narrative, a former Microsoft engineer shares how embracing versatile learning, solid computer‑science fundamentals, and a professional attitude guided his transition from Mac Office development to front‑end work at Bing Ads and ultimately to leading online document products at Alibaba, offering valuable insights for developers seeking sustainable career growth.
The article explores why peers with similar early abilities diverge over time, shares the author’s own rapid rise after graduation, and outlines five key characteristics—curiosity, optimism, refusing mediocrity, humility, and sound judgment—that consistently distinguish high‑performing young professionals.
From rockets exploding to financial crashes, this article chronicles twenty historic software bugs, detailing their losses, how they unfolded, and the programming mistakes that caused them, illustrating the massive economic and societal impact of faulty code.
The article shares a veteran engineer's reflections on choosing technologies, contrasting trendy versus familiar tools, weighing maintenance costs against productivity gains, and offering a pragmatic decision‑making framework illustrated with real‑world examples from Etsy, Mailchimp, and other projects.
This article offers practical advice for software engineers facing mid‑career challenges, outlining eight actionable principles—from avoiding stagnation and maintaining competitiveness to diversifying income and planning for a transition beyond coding—to help them sustain growth and resilience in a demanding industry.
In this talk, a former Alibaba front‑end leader shares his personal journey from a junior developer working on Taobao’s early YUI projects to leading large, growth‑focused teams, offering practical insights on technical mastery, continuous learning, and effective team management.
This article presents a curated list of twenty essential books for programmers at every stage—from junior to senior, full‑stack, architect, and leader—detailing why each title matters, its key lessons, and how it can guide technical growth, soft‑skill development, and career planning.
Discover a comprehensive overview of common programming positions—from full‑stack software engineers to data scientists, DevOps, and specialized domain experts—highlighting ideal personality traits, responsibilities, and how aligning your interests and strengths with these roles can lead to a fulfilling tech career.
