The article explains how a quality management plan serves as a formal blueprint to identify user needs, define standards, assign responsibilities, select tools, and continuously control processes, ultimately ensuring customer satisfaction and business success.
This article outlines best practices for Git branch management—including naming conventions for master, develop, feature, release, and hotfix branches—and provides detailed commit message guidelines based on the Angular style, complete with example commands and formatting rules to improve workflow and code traceability.
This article outlines agile software development design strategies, covering practical agile design activities, underlying design philosophies, and how design fits throughout the entire agile lifecycle, emphasizing iterative modeling, test‑driven development, and the balance between documentation and flexibility.
This article explains the purpose of Git branching, compares four mainstream branch models—TBD, Git‑Flow, GitHub‑Flow, and GitLab‑Flow—highlights their characteristics, pros and cons, and provides practical guidance on selecting the most suitable strategy based on team size, release cadence, and product complexity.
The author recounts bugs uncovered during a web‑based QA session—ranging from mismatched character‑length limits and inconsistent filter defaults to fragmented documentation—highlighting how overlooking tiny validation rules can cause costly defects and why unified standards and professional testing are essential.
This article offers a systematic approach to selecting and reading technical books, distinguishing methods for beginners and experienced developers, and illustrates the process with a PostgreSQL case study, emphasizing repeated reading and hands‑on practice as the key to mastering technical material.
This article compares major Git branching strategies—including Trunk‑Based Development, Git‑Flow, GitHub‑Flow, and GitLab‑Flow—detailing their workflows, advantages, drawbacks, and suitability for different team sizes and release cycles, and offers guidance on selecting the optimal model for your project.
Redis creator Salvatore "Antirez" Sanfilippo announced he will stop daily coding for the project, sharing his reasons, the history of Redis, the challenges of maintaining a popular open‑source database, and his plans to become a technical advisor while pursuing personal interests.
Youzan’s Efficiency Improvement team introduced project‑based management to bring transparency, empower part‑time PMs, and foster self‑organization, then layered Large‑Scale Scrum across component teams, enabling dynamic equilibrium between order and chaos and evolving the R&D organization toward agile, scalable efficiency.
The article compares large‑scale, highly regimented development teams with small, autonomous squads, explaining how the latter achieve faster delivery, higher innovation, and better resource efficiency while still handling complex projects, and discusses Conway's Law and practical implications for modern software organizations.
This article explains Git's origin, its snapshot‑based data model, the differences between centralized and distributed version control, and provides a concise guide to the 12 most frequently used Git commands for local operations, remote interaction, and branch management.
This article explains what Git is, why version control is essential, compares local, centralized, and distributed systems, describes Git's storage mechanisms and object types, and outlines the typical Git workflow with practical examples.
This article explores the communication gaps that hinder software projects, introduces Event Storming as a visual, collaborative workshop technique, walks through its syntax and practical coupon‑distribution example, connects the outcomes to Domain‑Driven Design, and shows how the method improves alignment between product, business, and engineering teams.
This article provides a concise, step‑by‑step checklist of common Git exceptions—including file recovery, branch deletion, commit amendment, branch renaming, commit rollback, merge reversal, and branch restoration—along with the exact commands and explanations needed to resolve each situation efficiently.
The article examines the historical development of PC and mobile operating systems, explains why China has not produced a mainstream OS or programming language, and argues that future opportunities will depend on aligning technological timing, geographic advantages, and human resources within China's growing IT ecosystem.
The article outlines best practices for remote software teams to keep pull requests small, fast, and well‑communicated, emphasizing frequent reviews, clear labeling, context provision, reviewer support, CI automation, and a collaborative, non‑authoritative culture to improve code quality and team productivity.
This article examines seven modern programming languages—Rust, Go, Kotlin, TypeScript, Swift, Dart, and Julia—detailing their key features, typical use cases, popularity trends, and why developers should consider learning them to stay competitive in today's software landscape.
This article explains agile testing principles, contrasts them with traditional waterfall testing, and details how the P1 project applied Scrum testing practices—short delivery cycles, daily stand‑ups, bug triage, continuous collaboration, technical excellence, and streamlined processes—to achieve rapid, high‑quality software releases.
This reflective guide explores how developers can grow amid countless technologies by focusing on product requirements, architecture design, clean coding practices, and personal self‑improvement, offering actionable insights such as using a ubiquitous language, higher‑dimensional thinking, KISS principles, test‑friendly code, confidence building, and targeted reading.
In this translated talk, Niclas Hedhman examines why poor code proliferates in the software industry, debunks common myths about development, highlights the hidden challenges programmers face, and proposes practical principles such as the KISS rule to gradually raise code quality and developer satisfaction.
In this interview, Git’s long‑time maintainer Junio Hamano reflects on the project’s 15‑year history, its community, design philosophy, favorite features, and the changes he would still make to improve version control for developers worldwide.
This article provides a comprehensive overview of DevOps concepts, including definitions of CI, CD, continuous deployment, version control, tooling, implementation steps, benefits, and distinctions from Agile and Lean IT, offering guidance for effective adoption and interview preparation.
This article chronicles the launch and backlash of the domestically developed Mulan programming language, examines the contentious reception of the UOS and Red Flag Linux operating systems, and reflects on China's broader push for independent software ecosystems amid ongoing trade tensions.
This article explains how using Git's cherry‑pick to copy commits between branches can lead to merge conflicts or silently incorrect code states, illustrates three possible outcomes with a concrete example, and advises when cherry‑pick is appropriate versus using a full merge.
The article analyzes why business and development teams often clash over requirements, explains the inherent upper and lower limits of IT production capacity, and proposes practical ways—such as staffing, process optimization, architectural improvements, and demand prioritization—to continuously raise the IT output ceiling while lowering maintenance burdens.
The article explains how agile testing reshapes software development by promoting simultaneous dev‑test activities, cross‑functional collaboration, continuous integration tools, clear communication, and rapid feedback loops that together accelerate delivery and improve product quality.
This article explores the essence of programming through philosophical definitions, the historical impact of Linus Torvalds and Linux, practical advice on setting small goals, and personal experiences that illustrate how continuous thinking, execution, and solid fundamentals lead to professional growth and mastery.
This article outlines ten practical habits for programmers—including cautious agreement, assertive refusal, building a personal knowledge system, cultivating a big‑picture view, adhering to coding standards, conducting code reviews, focusing on one language at a time, writing logic‑first comments, managing time well, and deeply understanding client needs—to accelerate professional growth and avoid common pitfalls.
The article explains why clear, complete and consistent error logs are essential for troubleshooting, enumerates typical sources of bugs—from invalid parameters and integration failures to logic coupling and hardware issues—and provides concrete guidelines and code examples for writing diagnostic logs that are easy to understand and act upon.
This article reviews the ten most popular continuous integration tools of 2020—including Jenkins, Buddy, TeamCity, Bamboo, GitLab CI, CircleCI, Codeship, CruiseControl, Buildbot, and GoCD—detailing their main features, language support, integration options, and suitability for various DevOps workflows.
The article explains, using a 1982 Lisa team story and agile practice observations, why lines of code, iteration velocity, and full staff utilization are unreliable productivity metrics and advocates using global outcome metrics and leading indicators for effective software development management.
This article introduces Git as a distributed version control system, explains its core workflow and branch model, and provides step‑by‑step instructions for configuring, cloning, checking out, committing, pushing, and using Git commands within IntelliJ IDEA, including useful screenshots.
The article shares practical advice for aspiring programmers, emphasizing the importance of genuine interest, perseverance, structured learning resources, real‑world projects, mentorship, and a balanced foundation in programming basics, Python, documentation, and related technologies to build a sustainable career in software development.
This article explains how the MaFengWo PMO team built a self‑developed PMO system that centralizes requirement data, automates group creation, synchronizes messages and emails, provides risk alerts and weekly reports, ultimately improving execution speed, reducing manual effort, and supporting multi‑business‑line project management.
This article shares Ant Financial's experience and structured approach to managing remote software development teams, covering planning, communication, toolchains, daily routines, and the benefits and challenges of distributed work to help technical leaders optimize remote collaboration.
This page provides a detailed table of contents linking to over 200 original articles covering API testing, unit and integration testing, performance testing, Java, Groovy, Python, web crawling, automation tools, and various technical and non‑technical topics for software engineers and testers.
This guide explains why version control matters, introduces Git as the leading distributed system, and provides a concise cheat‑sheet of the most important commands—from initializing a repository to branching, merging, and undoing changes—so you can work efficiently and collaborate without losing any history.
The TIOBE Programming Community Index, updated monthly, measures programming language popularity using data from global engineers, courses, and major search engines, helping developers assess skill relevance and choose appropriate languages, while emphasizing that the ranking reflects popularity rather than language quality.
This tutorial explains how to efficiently locate relevant open‑source repositories on GitHub by using advanced search filters such as name, README, description, star count, fork count, language, and last update date, with practical code examples and screenshots.
This guide explains five common Git workflows—from the simple master‑only model to feature, developer, combined, and release branching strategies—detailing their purposes, advantages, and when to adopt each to keep codebases organized and avoid conflicts in projects of any size.
The article explains various integration testing approaches—including Big Bang, Incremental, Bottom‑up, Top‑down, and Hybrid—and outlines practical best‑practice guidelines such as test ordering, separating test suites, thorough logging, and creating shared test plans for developers.
This article chronicles the development, challenges, and ultimate decline of IBM’s OS/2 operating system, examining technical decisions, market dynamics, and strategic missteps that led to its failure despite early promise in the.
JetBrains unveiled its 2020 roadmap for IntelliJ‑based IDEs, detailing new localization efforts, a lightweight editor mode, enhanced Git staging support, AI‑driven code completion, and other advanced features aimed at improving developer productivity and experience.
This article explains Git's evolution from a distributed version control system to the industry standard, outlines its key advantages and drawbacks, and provides a comprehensive list of essential commands for branching, stashing, resetting, tagging, and repository management.
This article reviews several popular code comparison utilities—including WinMerge, Diffuse, Beyond Compare, Altova DiffDog, AptDiff, and Code Compare—highlighting their key features, platform support, and how they help programmers efficiently spot and merge differences in source files.
Amid trade tensions and tech bans, Chinese developers have united to create the open‑source Unity Operating System (UOS), supporting domestic processors, offering a Windows‑like interface, and aiming to build a sustainable software ecosystem despite early ecosystem gaps.
This article offers practical guidance for aspiring programmers, covering mindset, learning strategies, career paths, and daily habits to help beginners build a successful and fulfilling software development career.
Python Software Foundation announced $407,000 in funding from Mozilla’s Open Source Support program and the Chan Zuckerberg Initiative to support pip’s 2020 development, outlining a three‑phase plan covering core work, resolver redesign, and long‑term maintenance, while detailing allocation of resources and future funding goals.
The article analyzes the sharp decline of the antivirus software market, citing reduced search interest, Microsoft’s free built‑in Defender, high development costs, shifting user habits toward mobile devices, and offers guidance on when third‑party protection may still be needed.
An overview of five emerging programming languages—Elm, Kotlin, Rust, Elixir, and Crystal—highlighting their key features, advantages, and potential impact on software development, illustrating how they address modern development needs and may shape the future of the industry.
This article introduces six widely used code comparison tools—WinMerge, Diffuse, Beyond Compare, Altova DiffDog, AptDiff, and Code Compare—detailing their features, supported languages, and how they help developers efficiently identify and merge differences in source files.
JD Retail’s technology and data platform adopted agile methods, launched training and coaching, created an Agile Project Management Guide, and achieved a 25% reduction in delivery cycles while 80% of projects now follow agile practices, showcasing measurable efficiency gains.
In a QCon 2019 interview, Huawei Cloud’s DevCloud chief product evangelist Liu Heng explains the platform’s end‑to‑end, one‑stop DevOps services, its emphasis on security and trust, the role of AI and AIOps, and how cloud‑native practices are empowering enterprises across industries.
The author, a former technical director, recounts a three‑month period managing a 20‑person R&D team across four legacy projects, analyzes four critical management mistakes—including over‑estimating team skill, under‑estimating project difficulty, spreading resources too thin, and neglecting dedicated management—and shares concrete reflections and actionable lessons for future leaders.
Microsoft has officially signed the Oracle Contributor Agreement and announced its integration into the OpenJDK community, highlighting a renewed commitment to Java development, collaboration with key partners, and future contributions that could reshape the Java ecosystem.
This article explains what Test‑Driven Development (TDD) is, outlines its step‑by‑step workflow, reviews its historical origins, compares it with traditional testing, and discusses the key benefits and drawbacks to help teams decide whether to adopt TDD.
The article explains what code review is, its goals, why it’s essential alongside testing, how QA professionals can effectively participate, various review methods, a Selenium‑specific checklist, and a set of best‑practice guidelines to improve software quality and delivery speed.
This article outlines ten essential habits for Java developers, covering solid OOP fundamentals, mastery of core APIs, continuous coding practice, active participation in tech forums and blogs, studying open‑source projects, tracking industry trends, maintaining reusable code snippets, understanding development methodologies, and documenting personal technical insights.
At the European Open‑Source Summit, Linus Torvalds explained that he now spends his days reviewing and replying to email patches, acting as a code maintainer rather than a developer, while reflecting on Git’s impact, his evolving role, and lingering imposter syndrome.
This article shares 25 actionable programming practices—from avoiding over‑planning and embracing simple solutions to leveraging version control, writing meaningful tests, and prioritizing user experience—aimed at making daily coding work more enjoyable and productive.
This article shares practical advice for junior developers, emphasizing the importance of a learning mindset, reading existing code, seeking constructive criticism, considering the big picture, and developing skills beyond programming to accelerate career growth and become a valuable team member.
This comprehensive guide explains how technical professionals can excel as project managers in internet companies by defining clear goals, aligning people and processes, and navigating each phase—from project initiation and requirement review to scheduling, testing, release, and post‑mortem—ensuring timely, high‑quality delivery.
The article argues that no company can be genuinely technology‑driven, explaining that market demand, product focus, and solid management practices—not flashy tech—determine success, while also offering practical advice on documentation, soft skills, and realistic career expectations for developers.
This guide walks developers through effective requirement management, scheduling, tracking, change handling, repository best‑practices, and risk mitigation, offering concrete checklists, prioritization methods, Git workflow rules, and actionable tips to keep projects productive and on‑time.
This article surveys hacker culture, tracing its roots from 1950s MIT clubs to modern tech giants like Facebook, outlines core hacker values, shares insights from seminal works such as 'The Cathedral and the Bazaar,' and offers practical advice for cultivating a hacker mindset in today’s DevOps era.
A technical director recounts a month‑long, troubled e‑commerce project—detailing its background, the cascade of quality and management mistakes, the intensive code‑review rescue, and the hard‑earned lessons on design, delegation, and balancing speed with quality.
In this interview, former Facebook Tech Lead Ge Jun shares how rapid yet sustainable development, trust‑based culture, and practical DevOps practices boost R&D efficiency, offering concrete process, engineering, personal, and management strategies along with measurable metrics for tech teams.
This article explores six practical ways to accelerate Java development—from hand‑writing and copy‑pasting to Excel formulas, code‑generation tools, and custom generators—detailing their workflows, sample code, advantages, drawbacks, and how to choose the right method for any project.
Interviews with 14 IT experts reveal that slow adoption, skill shortages, costly manual processes, and insufficient organizational support hinder automated testing, while opportunities exist through better tooling, containerization, and focused training to improve ROI and software quality.
An overview comparing Python and PHP highlights Python’s readability, rapid development, and broad applicability versus PHP’s server‑side strengths, detailing each language’s limitations, advantages, typical use cases, and why developers increasingly favor Python for diverse projects.
This article explains why clean code matters—reducing reading time, easing project continuation, speeding up new‑developer onboarding, and supporting consistent coding patterns—and provides six practical tips, from readable formatting to regular code reviews, to help developers produce cleaner, more maintainable software.
This article details JD.com’s agile transformation of its Shopping App, describing the challenges faced, the comprehensive agile maturity diagnosis model, measurement methods, improvement planning, and practical success tips for scaling agile across large, distributed development teams.
This article explains a comprehensive Git branching strategy for large projects, detailing the roles and workflows of master, develop, hotfix, and release branches, and how they support product development, testing, and release management.
Engineer.ai, an Indian AI startup that touted AI‑assisted app development and raised millions in funding, is now sued for allegedly exaggerating its AI capabilities, with evidence that human engineers performed the work, highlighting a broader issue of deceptive AI companies.
The article reflects on the challenges of shaping a sustainable team culture, shares personal experiences of transitioning from a traditional telecom background to mobile product development, and proposes concrete habits and a "product engineer" mindset to align engineering with product and data‑driven decision making.
The Ctrip Technology Salon held on August 3 in Shanghai gathered agile experts from Qunar, Vipshop, Hellobike, China UnionPay, Xinben Agile, and the Electronic Industry Press to share measurement systems, full‑process agile project management, agile‑driven publishing, rapid startup practices, business agility, and product innovation driven by community needs.
This article provides an overview of Python, covering its origin, historical releases, key features, major application domains such as web development, AI and data analysis, various interpreters, and development guidelines like PEP 8.
The article argues that Scrum falls short of true agility, critiques its rigid framework, labels it as fragile when mis‑implemented, and shares personal insights on why simple priority queues often outperform Scrum in software development.
This guide outlines how engineers can succeed as technical project managers by setting clear goals, aligning people and processes, and mastering each phase of the project lifecycle—from initiation and requirement review to scheduling, design, testing, release, and retrospective analysis—while mitigating common risks.
The article shares practical strategies for programmers to boost efficiency, emphasizing solid fundamentals, thorough documentation reading, thoughtful planning with sketches, disciplined task lists, regular reflection, focused work sessions, healthy sleep and exercise, and dedicated learning time to overcome common productivity anxieties.
The article describes Tubi's three‑month experiment to replace traditional waterfall and rigid sprint models with a flexible Release Train system, outlining the motivations, principles, team roles, tooling choices, successes, and areas needing improvement for a fast‑growing startup.
The article explains how company software projects differ from school practice projects in terms of pre‑built scaffolding, version‑control collaboration, multiple deployment environments, remote debugging, structured logging, and the need for permission approvals, offering practical guidance for newcomers to professional development.
This article adapts William J. Donovan’s sabotage manual to reveal how easy it is to undermine an agile team’s efficiency and how practical tactics—like over‑reliance on supervisors, ignoring feedback, and over‑building features—can silently destroy true agility.
This article provides a detailed overview of Git as a distributed version control system, covering installation on Windows, global user configuration, core concepts such as working directory, repository, staging area and HEAD, typical branching workflows, remote repository setup, and a collection of frequently used Git commands.
TIOBE's June ranking shows Python soaring to a record 8.53% share, surpassing C++, and predicts that if this growth continues, Python could replace Java and C within a few years to become the most popular programming language.
In this interview, Microsoft Asia Research chief Zou Xin shares his extensive software engineering experience, discusses the evolution of software development, offers practical advice on learning AI, and reflects on his books and upcoming GIAC conference activities, providing valuable insights for engineers and students alike.
This article traces GitHub’s evolution from a weekend project in 2008 to a $75 billion Microsoft acquisition, examining its innovative free‑plus‑paid model, community‑driven growth, strategic product decisions, and the lessons it offers for product and R&D management.
This case study details how a user product center team applied the APD agile methodology and stream development practices—such as visual value streams, explicit process rules, WIP limits, bug‑board visualization, workflow management, and an evolved TDD approach—to double throughput, cut delivery cycles by 60%, and reduce monthly bugs from 50 to 2, demonstrating measurable R&D efficiency gains.
Linus Torvalds, the creator of Linux, began programming at age 11, built the OS inspired by Minix and Unix, leveraged community support, and exemplifies traits such as intense focus, modesty, and dedication, offering valuable lessons for developers and highlighting the historical evolution of open‑source operating systems.
This article reviews the top ten programming languages, explains why learning multiple languages matters, and offers practical advice on choosing the most beneficial language for your career, covering Java, JavaScript, Python, Kotlin, Go, C#, Swift, Rust, PHP, and C/C++.
This article examines the debate over writing documentation in agile projects, explains how to create effective agile documentation using user stories, compares it with traditional project documentation, and offers concrete guidance and examples to help teams adopt a more efficient, value‑driven documentation approach.
This article explains why agile projects treat documentation differently from traditional projects, outlines the logical and structural differences, shows how to write user stories that pair Why and What, and provides practical guidance for creating concise, value‑driven agile documentation.
The article explores what a bug really is, why bugs inevitably appear in software development, and offers practical strategies—such as effective logging, leveraging debugging tools, and keeping iteration sizes small—to locate and resolve bugs more quickly.
The article examines why many consider Java outdated and inflexible, discusses its ecosystem, JVM strengths, comparisons with newer languages, and ultimately argues that despite its age Java remains a viable backbone for large‑scale software development.
This article explores the most famous software development laws—from Murphy's Law to Moore's Law—explaining their meanings, origins, and practical implications for coding, project management, and system design.
The article examines why seemingly outdated technologies such as SQL remain valuable, critiques the overhyped promises of TypeScript and Docker, and urges developers to balance new trends with proven fundamentals for sustainable software engineering.
This article chronicles a Chinese computer science graduate’s step‑by‑step evolution from learning basic C and Java in university to building campus apps, winning software contests, mastering Spring, Hadoop, Elasticsearch, and Neo4j, and ultimately landing offers from top tech firms, illustrating the challenges and perseverance required for a successful software engineering career.
The article argues that programmers should devote the majority of their limited time to mastering transferable fundamentals and design principles rather than constantly chasing the latest frameworks, using the Lindy effect and personal experience to illustrate this sustainable learning strategy.
The article analyzes the difficulties of quantifying software R&D efficiency, critiques common measurement methods, proposes two guiding principles—global over local metrics and result over output—and presents a comprehensive set of delivery efficiency, quality, and capability indicators with calculation logic.
To keep product development sustainable, prioritize user‑reported bugs first, then self‑discovered bugs, followed by user‑requested features and finally internal ideas, using continuous ranking based on impact, difficulty, and supporter count while actively listening to users and fixing problems before adding new functionality.
