This article introduces seven widely used code comparison tools—WinMerge, Diffuse, Beyond Compare, Altova DiffDog, AptDiff, Code Compare, and jq22—detailing their features, supported platforms, and how they help programmers efficiently identify and merge differences in source code and other files.
The author, a former programmer turned tech manager, humorously lists thirteen counter‑productive practices—ranging from fake agile enthusiasm and lack of coaching to cultural neglect and tool misuse—that can sabotage a development team when agile is applied without genuine understanding or respect.
The article examines the heated discussion about whether C++ is obsolete, presenting TIOBE ranking data, contrasting opinions on its relevance in various domains such as operating systems, game engines, and web development, and offering practical advice for newcomers deciding if C++ should be their first programming language.
SPD Bank’s four major systems—an enterprise micro‑service platform, cash‑flow analysis, fund‑supervision, and financial IC‑card services—successfully passed the Level‑3 Continuous Delivery assessment of the national DevOps standard, showcasing a leading‑edge, organization‑wide DevOps capability that boosts delivery speed, quality, and agility.
Tencent’s 2020 R&D Big Data Report shows the company added 2 billion lines of code, with R&D staff comprising 68% of its workforce, highlights C++ as the top language, details significant efficiency gains, and reveals high‑quality code output from technical leaders and senior engineers.
The article announces the official release of Java 16, outlines its new language and JVM enhancements, incubator and preview APIs, tooling updates, platform ports, and highlights the extensive community contributions that helped deliver the update.
Celebrating Python’s 30th birthday, this interview with core contributor Pablo Galindo explores the language’s rise, current massive adoption, diverse use cases—from machine‑learning models to internal tooling—and his perspective on upcoming challenges, performance improvements, and the balance between evolution and backward compatibility.
The article outlines how agile development improves software quality, enhances team collaboration, increases project transparency, reduces risk, accelerates growth, and enables more accurate project assessment, making it a comprehensive methodology for modern, user‑centric software projects.
Stack Overflow’s engineering team reveals how they deliberately forgo certain coding best practices—such as strict adherence to design patterns, extensive unit testing, and conventional language choices—to boost performance and scalability, offering insights into the trade‑offs between idealism and real‑world software demands.
This guide explains when taking side projects makes sense for developers, warns against low‑pay, high‑effort gigs, and provides concise reviews of 19 popular freelance platforms—including their focus, key features, and official websites—to help programmers choose the right opportunities.
Effective error logging provides crucial clues for troubleshooting, yet many logs lack context, consistency, or detail, making debugging time‑consuming; this article explains common error sources, fourteen typical causes, improvement measures, and practical guidelines—including formatting rules and code examples—to help developers write clear, actionable logs.
RedMonk’s February 2021 programming language ranking places JavaScript at the top, followed by Python, Java, and PHP, using GitHub pull‑request data and Stack Overflow activity to gauge popularity, and notes that half of the top‑20 languages have shifted unusually compared to the previous year.
This article introduces four major software development models—Waterfall, Iterative (RUP), Spiral, and Agile—detailing their origins, core concepts, advantages, and disadvantages, helping readers understand how each approach structures project phases, manages risk, and adapts to changing requirements.
This guide walks through installing Git, configuring it in IntelliJ IDEA, creating a local repository, adding and committing files, and pushing the project to a remote GitLab repository, including screenshots and code snippets for each step.
This article explains how character encoding works, using ASCII, Unicode, UTF‑8 and GBK examples to reveal why the garbled string “锟斤拷” appears when mismatched encodings are processed, and shows the underlying byte‑level transformations.
This article traces the historical shift in software development practices, comparing the linear Waterfall model with Agile, Kanban, Scrum, and Lean approaches, highlighting how each methodology improves flexibility, transparency, and efficiency by borrowing principles from automotive production systems.
This article compiles the most influential 2021 software development trends—from cloud, edge, containers, AI, blockchain, and more—alongside curated deep-dive resources covering frontend innovations such as smart code generation, TypeScript declarations, authentication mechanisms, node_modules challenges, React best practices, security protocols, and operational resilience.
This article shares practical guidance for non‑CS individuals who want to self‑study programming and switch careers, emphasizing clear self‑positioning, project‑centric learning, solid fundamentals, community involvement, and realistic long‑term expectations to improve employability.
This article outlines five practical version‑control best practices—choosing a suitable branching strategy, committing small frequent changes, writing descriptive commit messages, developing on branches, and performing regular code reviews—to improve team collaboration and delivery speed in modern software projects.
The article presents data‑driven predictions for 2021, covering cloud dominance, edge computing growth, multi‑cloud strategies, Kubernetes supremacy, the rise of quantum computing, blockchain evolution, AI democratization, deep‑learning frameworks, modern databases, big‑data processing, low‑code platforms, software architecture diversity, programming language shifts, and the future of web and mobile development.
A seasoned programmer shares six practical lessons—from avoiding knowledge blindness and valuing soft skills to embracing code simplicity, listening before speaking, staying flexible with technology, and aligning roles with personal strengths—to help developers grow both technically and professionally.
The article examines the causes and consequences of workplace involution and the 996 work model, shares personal experiences, and offers practical advice for engineers to build solid fundamentals and for managers to foster sustainable, non‑involuted teams while emphasizing cloud, open‑source, and thoughtful career choices.
This article outlines the typical roles in an internet company, explains how cross‑department collaboration, timeline definition, resource allocation, development‑testing‑deployment phases, and comprehensive project retrospectives work together to ensure successful project delivery.
The 2020 GOLF+ IT New Governance Leadership Forum in Beijing highlighted industry best practices, honored ICBC senior manager Qian Xianglong as the financial sector leader, and featured an in‑depth interview where he discussed his career, 2020 DevOps achievements, and ambitious 2021 plans for standardization, tooling, and security.
This article compiles a wide-ranging discussion on how development teams can guarantee that developers allocate sufficient time for writing test cases despite tight schedules, covering division of testing duties, organizational processes, requirement handling, performance metrics, and skill development.
The article outlines Java 16’s release schedule, highlights its six‑month support window, and details a comprehensive list of new language and runtime features—including sealed classes, strong encapsulation, foreign‑linker API, ZGC improvements, record classes, and the upcoming jpackage tool—while noting Java 17’s upcoming LTS release.
This article explains the multiple benefits of code review—from knowledge sharing and improving code quality to enforcing team standards—and provides practical steps, cultural tips, tool recommendations, and workflow guidelines to help development teams adopt effective code review practices.
In a recent global C++ conference, Bjarne Stroustrup outlined the major features of C++20, explained his design philosophy of simplicity, balance, freedom and friendliness, and highlighted how C++ continues to serve a wide range of domains while offering guidance for learning and future evolution.
This article explains why QA should join technical design reviews, outlines the four main benefits, and provides a step‑by‑step guide for pre‑review preparation, in‑review focus areas, and post‑review follow‑up, illustrated with a real project case study.
This article explains the concept of mock testing, its role in unit and interface testing, and reviews popular mocking tools such as EasyMock, JMockit, Mockito, RAP, YApi, Moco, and DOClever, highlighting their applications in software development.
Anxin Securities’ user‑center project passed the third‑level DevOps continuous‑delivery assessment, showcasing how standardized processes, tool empowerment, and agile transformation boosted software delivery efficiency and positioned the firm at the forefront of domestic DevOps maturity.
Discover a curated list of twelve essential IntelliJ IDEA plugins—including IDE Features Trainer, Codota, and Code With Me—that help developers master the IDE, enhance code quality, and streamline collaboration, all illustrated with clear screenshots and concise descriptions.
This guide offers practical advice for agile developers, covering stand‑up meetings, sprint planning, tracking progress, story points, and teamwork to help teams thrive in fast‑paced, remote‑first environments by emphasizing efficient communication, realistic planning, and continuous improvement.
This article traces Python’s history—from Guido van Rossum’s Dutch roots and the influence of ABC, through its 1991 birth, community‑driven growth, and design philosophy—to illustrate how open‑source collaboration shaped one of today’s most popular programming languages.
The eight‑dimension low‑code capability measurement model evaluates platforms across business scenario breadth, user‑group reach, technical completeness, material inclusiveness, product richness, production‑chain coverage, collaboration efficiency, and intelligence, providing a traceable framework to assess maturity and guide future evolution.
This article examines the often‑tense relationship between product managers and developers, identifies the main sources of friction from both sides, and offers a structured three‑step approach—including clear direction, rigorous use‑case work, and five communication techniques—to achieve sustainable, win‑win collaboration.
After two decades of Java and C dominating the TIOBE rankings, Python has surged to the second spot, prompting a discussion on why programming skills are becoming a universal necessity and how the latest index can guide developers in choosing the right language for future projects.
This guide presents a comprehensive, organized list of the most commonly used Git commands—including repository initialization, configuration, file staging, committing, branching, tagging, inspection, remote synchronization, and undo operations—complete with concise examples to help developers work efficiently with version control.
This article presents forty concise, actionable tips ranging from breaking code into functions and applying YAGNI and KISS principles to using version control, testing, and continuous learning, all aimed at helping developers enhance their coding efficiency and professional growth.
The article explains open source’s core principles of openness, sharing, equality and collaboration, advises selecting projects with strong community and multi‑company backing, highlights China’s rapid growth in Apache projects, and encourages developers to contribute through code, documentation, translation and other community activities.
The article outlines eight major software development trends expected to dominate the next ten years, including the continued rise of artificial intelligence, Python’s growth with AI/ML, 5G’s impact, edge and cloud computing expansion, emerging languages like Rust, Kubernetes dominance, React’s persistence, and the lowering barrier for self‑taught programmers.
A project manager recounts how poor quality focus, insufficient team oversight, lack of design, uncontrolled requirement changes, and missing code reviews led to a disastrous rollout, and shares the corrective actions and key lessons to avoid similar failures in future software projects.
This article compares the traditional Waterfall model with Agile approaches like Scrum, outlining their origins, advantages, disadvantages, key roles, processes, and how teams can balance both methods to improve project delivery and avoid common pitfalls.
The article argues that many agile implementations are misapplied, creating pressure and defects for developers, and proposes that developers focus on proven software development practices such as extreme programming, continuous delivery, and test‑driven development rather than blindly following flawed agile frameworks.
Code reviews are essential for maintaining product quality, reducing technical debt, and fostering team knowledge sharing, yet they face challenges like time constraints and subjective biases; this guide outlines why reviews matter, their benefits, common pitfalls, formats, participants, focus areas, processes, key operations, principles, and typical issues with practical examples.
This article shares a step‑by‑step framework for software developers to rapidly grasp new technologies by first scanning the big picture, identifying recurring patterns, building case‑based projects, reinforcing knowledge through micro‑service integration, and applying focused study techniques for both theoretical and practical challenges.
The article reflects on a year of software development experience, emphasizing the importance of concise daily stand‑ups, rigorous code review, product‑oriented thinking, regular incident retrospectives, and thoughtful process adaptation to improve team efficiency, quality, and ownership in software projects.
The article explains why software developers who come from short‑term training bootcamps are frequently dismissed by hiring teams, analyzes the underlying reasons, and offers practical advice for self‑learning, building real experience, and demonstrating genuine coding ability.
This article examines seven typical misconceptions in software development—from focusing on tasks instead of demand to favoring batch releases over continuous delivery—and offers practical guidance on improving flow efficiency, cross‑functional collaboration, code quality, and automated testing.
GitHub CLI 1.0, now officially released, lets developers manage repositories, pull requests, and issues directly from the terminal with simple commands, offers cross‑platform installation options, and supports custom aliases and enterprise connections for faster, scriptable workflows.
Continuous Integration is a software development practice where team members frequently integrate their work, typically multiple times per day, with each integration automatically built and tested to quickly detect errors, improve collaboration, reduce risk, and enable faster, more reliable delivery of high‑quality software.
The article explains a range of source‑code branching patterns—including source branches, mainlines, feature branches, release branches, maturity branches, hot‑fix branches, release trains and team integration branches—detailing their purposes, trade‑offs, integration frequencies, and how teams can choose the most suitable strategy for effective software development.
This article outlines practical Java coding conventions, explains the importance of automated style checking with Checkstyle, and provides a comprehensive list of development best‑practice tips ranging from naming rules and documentation to tooling, hardware setup, and continuous learning habits.
The article shares a personal journey of using the Deepin Linux distribution for everyday development, communication, and entertainment, demonstrating its graphical interface, extensive software support, Android app compatibility, and various efficiency and freedom advantages that make it a viable Windows alternative.
In this candid post, a former technical director shares a three‑month case study of team mismanagement, detailing four critical mistakes—over‑estimating talent, under‑estimating project difficulty, spreading resources too thin, and neglecting proper management—along with reflective insights and actionable lessons for future leaders.
This article surveys a wide range of REST API tools—covering API definition, testing, monitoring, publishing, and centralized management—highlighting their key features, supported languages, integration capabilities, and suitability for teams of different sizes and project requirements.
A seemingly simple two‑line code change can stretch into days because of unclear bug reports, unfamiliar features, thorough root‑cause analysis, multiple reproduction paths, impact checks, careful solution design, and comprehensive testing, all of which aim to prevent future regressions.
The discussion analyzes why creating a domestic MATLAB‑like scientific computing platform in China faces steep technical, talent, market, and funding obstacles, and proposes ecosystem and policy measures to foster homegrown alternatives.
This article explains the importance of security testing, outlines where to start, and details a step‑by‑step security testing workflow covering requirement analysis, static code scanning, third‑party component checks, data masking, permission checks, XSS, SQL injection, privilege escalation, file upload/download, server port scanning, and business‑specific test cases.
The article examines Python's rapid rise since its 1991 debut, highlighting its free, cross‑platform nature, strong community support, growing popularity on StackOverflow, and expanding job market, while questioning whether it will dominate future software testing, AI, and machine‑learning development.
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.
