This guide explains OpenAI's open‑source maintainer program, detailing eligibility, the three support components, key application fields, and how to craft persuasive answers to secure six months of ChatGPT Pro with Codex, Codex Security access, and API credits.
In a candid interview at the Linux Foundation Open Source Summit, Linus Torvalds reflects on his shift from programmer to maintainer, the impact of AI and Rust on kernel development, hardware trends, and how open‑source communities adapt to change.
This guide compiles 50 practical Docker commands covering daily status checks, weekly resource cleanup, monthly security hardening, logging and monitoring, image management, high‑availability, and disaster‑recovery, helping operators maintain healthy containers across Rocky, CentOS, and Kylin environments.
The Linux kernel’s floppy‑disk driver received its first maintenance update in three years, submitted by Intel engineer Andy Shevchenko, who removed an unused CROSS_64KB macro, replaced a custom SZ_64K constant, and alphabetically reordered headers, thereby cutting redundant code and improving readability for legacy systems still relying on floppy storage.
This article explains how creating a custom frontend component library in small companies often leads to resource waste, maintenance nightmares, technical debt, and production failures, and recommends using mature open‑source libraries with selective customization instead.
This article explains why equipment failures often lead to blame‑shifting between production and maintenance teams, defines clear responsibilities, and outlines a four‑step system—including daily inspections, maintenance scheduling, fault handling, and performance metrics—to achieve coordinated, data‑driven equipment management.
The article examines Vibe Coding, an AI‑driven programming approach that lets developers generate software from natural‑language prompts, outlining its efficiency gains, lower entry barriers, cross‑domain collaboration benefits, as well as code‑quality, debugging, over‑reliance risks, and practical guidelines for responsible use.
This article explains why systematic equipment management is crucial for manufacturers and introduces ten key performance indicators—breakdown rate, MTBF, MTTR, utilization, OEE, maintenance cost ratio, availability, and more—detailing how to calculate, interpret, and improve each metric using a dedicated management system.
When a client claims there is no workload because a system is stable, this article offers practical strategies—such as proactive monitoring, artificial fault injection, transparent SLA reporting, and value‑added services—to demonstrate the necessity of ongoing maintenance fees while balancing client expectations.
When a client believes a perfectly stable system requires no work, this guide offers practical strategies—like creating visible tasks, leveraging SLA metrics, simulating issues, and adding value‑added services—to justify and sustain maintenance fees.
Alibaba's EasyExcel Java library will cease new feature development and shift to maintenance‑only mode, yet it remains notable for its low‑memory, high‑speed Excel processing, and the author is launching EasyExcel‑Plus to further boost performance and add features.
The article outlines twelve harmful coding habits—such as excessive microservice splitting, incomplete refactoring, overly long methods, deep nesting, random variable names, inaccurate or outdated comments, duplicated code, ignoring specifications, missing logging, over‑engineered frameworks, and reinventing wheels—that degrade readability, complicate maintenance, increase bugs, and hurt team productivity.
The article describes how JD Aviation’s maintenance department uses a vector‑based knowledge base and large‑language‑model services to automatically generate, evaluate, and maintain training exam questions, addressing the rapid growth of manuals, frequent updates, and the heavy manual workload of traditional test creation.
This article provides a comprehensive guide for developers on why documentation matters, what types of technical documents to create, practical templates and formatting rules, and how to maintain and update documentation over time to ensure lasting value.
This article explains why traditional qualitative questionnaires are insufficient for maintaining a design system, introduces a four‑step framework (clarify, select, explore, solve) with specific quantitative metrics for component scale, maintenance efficiency, adoption breadth, and usability, and demonstrates how to apply these metrics to identify and resolve real‑world component library issues.
This article shares practical tips for maintaining a MacBook, covering regular OS updates, disk space cleaning, startup item management, keyboard and screen cleaning, temperature control, battery replacement, and data backup to extend the laptop’s lifespan.
The article, presented by a senior architect, outlines the standardized six-stage process of database design—system requirements analysis, conceptual design, logical design, physical design, implementation, and operation & maintenance—accompanied by illustrative diagrams for each phase.
The article outlines practical criteria for creating qualified and excellent API documentation, covering project overview, modular organization, request/response details, maintenance practices, and common pitfalls, illustrated with a Jira issue‑creation example, to help testers and developers improve efficiency and communication.
Drawing on more than 50,000 repair cases, this article explains why continuously powered‑on computers often outlast those that are frequently switched off, citing reduced moisture‑induced oxidation, temperature effects, and the hidden risks of Windows sleep/hibernate especially in humid environments.
This article outlines the evolution of software architecture—from monolithic to distributed, microservice, and serverless models—detailing each pattern’s structure, advantages, and drawbacks, helping developers understand how architectural choices impact scalability, maintenance, and innovation in modern software projects.
A Huawei maintenance engineer shares a decade‑long journey of turning 24/7 on‑call pain into systematic knowledge management, building comprehensive fault‑handling documentation, automating tools, and guiding the team’s evolution toward SRE practices that dramatically reduce manual effort and improve reliability.
The article examines how front‑end frameworks can address business scenarios, user experience, development speed, and maintenance cost, offering practical strategies and future trends to quickly launch and sustainably maintain high‑quality products.
Linus Torvalds highlighted the generational challenge of Linux kernel maintenance, the difficulty of finding new maintainers, the importance of trust, the continued dominance of C with emerging Rust support, and previewed the massive upcoming 5.8 release with its new hardware and feature updates.
This article outlines practical strategies for maintaining Selenium test automation, including keeping test cases simple, encouraging developer involvement, defining execution strategies, improving test stability, focusing on high‑return‑on‑investment scenarios, and using cloud services for efficient cross‑browser compatibility testing.
This article explains why Selenium test automation requires ongoing maintenance, outlines the two main maintenance scenarios—test failures and dependency changes—and provides practical guidance for developers and testers to efficiently support and sustain automated testing in agile environments.
This article discusses why microservices have become popular, outlines their advantages such as continuous delivery, easier maintenance, independent scaling, fault tolerance, and technology flexibility, and also examines the challenges like service decomposition, distributed system complexities, and multi‑team coordination, helping readers decide when to adopt them.
This article debunks common myths about test automation, explains why scripts require ongoing maintenance, discusses why full automation is impossible, and offers practical guidance on balancing automated and manual testing using risk‑based, conversation‑driven, and exploratory approaches to maximize value.
After the holiday break, this guide walks operations engineers through a comprehensive checklist—including hardware inspection, server preparation, network device checks, monitoring platform readiness, remote access security, and post‑holiday work review—to ensure systems run smoothly and securely.
This article explains Oracle 12c's In‑Memory Column Store feature, its compression levels, step‑by‑step testing results for full scans and joins, a real‑world production case from Zhejiang Mobile, and practical maintenance commands to keep the in‑memory area healthy.
This article outlines ten practical guidelines for operations engineers—ranging from mandatory rollback testing and cautious handling of destructive commands to robust backup verification, vigilant monitoring, and disciplined handover procedures—to dramatically reduce system outages and improve overall reliability.
The article explains the evolution from single‑block to three‑tier software architecture, outlines the benefits and drawbacks of monolithic applications, and discusses why modern internet‑scale systems increasingly need to move beyond monoliths to meet scalability, maintainability, and rapid delivery demands.
This article outlines four key practices—comprehensive engineering documentation, robust business backup, continuous online monitoring, and regular periodic inspections—that together ensure optimal performance, reliability, and long‑term benefits for data center operations.
