The author reflects on personal experiences with agile adoption, emphasizing the importance of documentation, distinguishing true teams from loosely organized groups, clarifying Scrum role requirements, and discussing the unique challenges and advantages small teams face when practicing agile methodologies.
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 explains the value of technical diagramming, defines architecture and architecture diagrams, describes their purposes, outlines common diagram categories such as the 4+1 view, offers criteria for good diagrams, addresses typical pitfalls, and introduces the C4 model with concrete examples and a case study.
Bootstrap 5 Alpha introduces a jQuery‑free core, drops Internet Explorer support, revamps the documentation UI, adds CSS custom properties, expands the grid system and utilities, and brings numerous enhancements to forms, colors, and overall developer experience.
This article explains how to use Swagger and Springfox to automate API documentation and testing in Java SpringBoot projects, covering the benefits of Swagger, integration steps, Maven dependencies, configuration examples, and how to access the generated interactive UI for faster, more reliable interface validation.
This article provides a concise reference of Laravel's String helper functions, describing each method's purpose and showing example code snippets for common string operations such as conversion, case manipulation, searching, and generating random strings.
This article outlines frequent programming errors—such as trusting user input, skipping tests, neglecting documentation and logs, hard‑coding values, ignoring rest, and failing to keep learning—and offers practical advice to prevent them and improve software reliability.
This guide explains why proper software documentation is crucial and reviews four popular online tools—GitHub Pages, Read the Docs, Tettra, and Apiary—detailing their features, how they integrate with version control, and where to access them.
This article explores the challenges of component maintenance in micro‑frontend architectures, compares different component types, and presents a practical CLI tool that automates scaffolding, testing, documentation, and publishing to streamline the creation of a reusable, well‑documented component library.
The article introduces magpie_fly, an open‑source Flutter component library created by 58.com to unify component management, provide detailed documentation with live previews and source code, outline its implementation approach, list existing widgets, and describe future plans for community contributions.
This article describes how a front‑end team can create a markdown‑based documentation site that updates automatically via GitLab webhooks, using EggJS with marked and highlight.js for server‑side rendering or NestJS with docsify for client‑side rendering, and provides complete code examples and deployment steps.
This article shares Ant Design’s multi‑year open‑source project operation experience, covering project documentation, website setup, code style, unit testing, CI services, release workflow, issue/PR templates, Git tips and community‑driven growth strategies for a frontend UI library.
This tutorial explains how to install Node.js and docsify-cli, initialize a docsify project, customize the navigation bar, cover page, search and code highlighting, and finally deploy the documentation site to GitHub Pages or a cloud server using Nginx, while providing troubleshooting tips.
This guide walks you through downloading, extracting, and configuring C++ library man pages on a Linux system so that the standard "man" command can provide offline documentation for C++ functions and classes.
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 you through using Docsify to create a lightweight, dynamic documentation website for the SpringBoot-based mall project, covering installation, project initialization, sidebar and navigation customization, search, code highlighting, copy‑code features, and deployment via GitHub Pages.
Learn how to boost your workflow on GitHub by editing files directly, pasting images, formatting code blocks, linking issues and code, creating permanent permalinks, using project boards, setting up GitHub Wiki, deploying sites with Jekyll, and even turning the platform into a lightweight CMS.
Vant 2.0 launches with four new components, revamped documentation, enhanced theming and a slimmer bundle, while boasting 220 releases, a 98% issue‑resolution rate and plans for VantWeapp 1.0 and a Vue 3‑based Vant 3.0, reflecting the project’s marathon‑like, fast‑iteration development.
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.
This guide walks developers through selecting VuePress for a centralized documentation portal, installing it globally or locally, configuring navigation and build scripts, generating static files, deploying them on an Ubuntu server with Nginx, and automating updates via Jenkins, cron jobs, and Docker.
This tutorial provides a comprehensive overview of Markdown syntax, covering heading levels, text styling, unordered and ordered lists, blockquotes, inline and fenced code blocks, tables, horizontal rules, as well as link and image formatting, with clear examples for each feature.
This article outlines comprehensive IT operations practices, covering methods, documentation, process flows, essential technical skills, monitoring strategies, backup solutions, and the overall value of operations in supporting business objectives.
This article explores why API design is crucial for large‑scale software systems, outlines fundamental design principles, presents detailed best‑practice recommendations, and discusses compatibility, idempotency, error handling, and versioning with concrete examples such as the POSIX File API.
This article chronicles the author’s journey from fragmented knowledge‑base tools to adopting MDWiki—a pure front‑end, Markdown‑driven wiki that can be deployed on any web server, integrated with GitHub Pages, and extended with comments, analytics, and custom build pipelines.
This article explores the multifaceted role of IT operations, emphasizing how automation, documentation, processes, monitoring, and backup strategies create business value, and shares practical insights from over ten years of experience to help professionals elevate their operational impact.
Taro UI is a multi‑end UI component library built by the Aotu Lab, offering easy installation, rich components, and seamless adaptation across WeChat mini‑programs, H5, and ReactNative, with detailed quick‑start instructions and code examples for developers.
This guide walks you through the essential parts of a Laravel codebase—documentation, composer files, routes, service providers, tests, and debugging tools—so you can confidently understand and contribute to a new project even without prior PHP experience.
This article explains how to use Python’s built‑in help() function to view documentation for modules, objects, and keywords, shows the command syntax, provides interactive examples, demonstrates how to browse modules, keywords and topics, and describes the simple “q” key method to exit the help session.
Understanding and documenting the system context—its external users, roles, channels, and interacting systems—provides a foundational view that links business context to architecture, guides information flow modeling, and ensures traceability throughout the software development lifecycle.
This article explains the discipline of software architecture, its historical roots, key definitions, the importance of comprehensive documentation, various architectural views, and essential documentation components that help teams communicate designs, educate new members, and maintain system quality over time.
VuePress is a lightweight static site generator for technical documentation and blogs that offers responsive design, theme customization, Markdown with Vue components, PWA support, and easy navigation configuration, and can be quickly set up, built, and deployed via simple npm or Yarn scripts while handling common pitfalls such as asset placement and base‑path adjustments.
The article shares practical QA techniques and project‑progress strategies for a mobile DSP advertising team, emphasizing paper‑based documentation, rapid test case execution, clear test design using XMind, and the potential of AI‑driven bug analysis, while also highlighting the importance of versatile testing roles.
This guide shares practical GitHub usage habits, from crafting consistent READMEs and issue/PR templates to leveraging labels, CI integration, release workflows, and post‑release support, helping open‑source maintainers improve project visibility, collaboration, and quality.
This article compares traditional waterfall and agile software architecture, examining the roles, timelines, and deliverables of architects, sharing real‑world challenges, and offering practical guidelines for building sustainable, adaptable architectures in modern development teams.
This article chronicles the development of a DevOps documentation hub from its early v0.5 prototype through v1.0 and v2.0 releases, detailing the shift from reStructuredText to Markdown, the use of Git submodules, Azure App Service deployment, and plans for automated navigation and community interaction.
This article explains how Electron lets web developers create cross‑platform desktop applications with familiar JavaScript and Node.js, compares it to NW.js, outlines learning stages, offers documentation tips, and provides guidance on selecting and extending useful demo projects.
This article highlights the most common Linux frustrations in 2017, from inadequate documentation and software version incompatibilities to UEFI/Secure Boot challenges, the decline of 32‑bit support, and deteriorating X‑forwarding support, while noting overall progress and inviting readers to share their own issues.
This article explains the concept of custom schema URLs in mobile development, describes the problems of a growing ad‑hoc implementation, and presents a refactored, configuration‑driven architecture that provides automatic matching, self‑documenting schemas, and integrated testing for Android apps.
This article outlines a comprehensive R&D management framework covering product lifecycle‑based task planning, documentation practices, code collaboration, quality assurance, automated deployment, fault handling, instant communication, and techniques for boosting team technical competence.
This article presents a detailed, experience‑driven guide to building an efficient R&D management system covering the product lifecycle, task management, documentation, code collaboration, quality assurance, automated deployment, fault management, instant communication, and techniques for continuous technical improvement.
The article explains how integrating chatbots into communication platforms like Slack transforms routine operations into transparent, collaborative, and mobile-friendly workflows, enabling continuous pair‑programming, on‑the‑fly documentation, focused incident response, and seamless cross‑team coordination.
This guide compiles sixteen highly useful websites—including search engines, official documentation, Chinese tutorials, community Q&A, and framework references—to help anyone learning Python find reliable resources and solve programming problems efficiently.
This article shares ten practical guidelines—from clear naming and solid modeling to robust exception handling, elegant design, strong fundamentals, effective documentation, and a positive mindset—aimed at helping developers create software that is both functional and visually appealing while advancing their careers.
The article shares practical operations lessons—from periodic permission audits and thorough documentation to capacity monitoring, log rotation, and automation—illustrating how systematic practices and tooling can standardize and streamline IT infrastructure management.
This article explains why comprehensive interaction design documents are essential for aligning product vision, improving hand‑off accuracy, and boosting team efficiency, and it provides a detailed framework covering structure, layout, color, typography, and content guidelines to help design teams create clear, reusable documentation.
This article introduces three key macOS tools—Dash for documentation, MindNode for mind mapping, and OmniGraffle for diagramming—explaining their core features, usage tips, and how they can boost a developer's productivity, followed by a curated list of additional handy utilities.
This article describes how to build an automated documentation publishing pipeline using VSTS CI, Azure FTP deployment, Sphinx conversion, Docker containers, and GitHub synchronization, enabling one‑click HTML generation and backup for Markdown/reStructuredText sources.
Transpedia, launched with TDH 4.6, consolidates all StarRing product manuals into a single online portal that offers real‑time synchronization, keyword search, and intuitive navigation, eliminating the need for PDF downloads and dramatically improving documentation accessibility and user experience.
Effective API design requires shifting from a developer‑centric mindset to the user’s perspective, emphasizing clear documentation, stability, versioning, flexibility, security, and ease of use, while avoiding unnecessary complexity and ensuring consistent, well‑structured interfaces for diverse clients across web, mobile, and IoT platforms.
This article compares waterfall and agile approaches to software architecture, examining the architect's role, time span, deliverables, and documentation practices, and offers practical guidance for building sustainable, adaptable system designs in modern development environments.
This guide walks you through installing Sphinx, configuring the Read the Docs theme, generating reStructuredText from Python code, and building HTML documentation for your API, complete with project setup, conf.py tweaks, and custom module directives.
This article explains why APIs are valuable assets, outlines the essential traits of a good API, and provides a step‑by‑step design process—including requirements gathering, naming, documentation, performance considerations, exception handling, and refactoring examples—illustrated with Java code snippets.
This article explores the challenges of software documentation, proposes automated solutions using DevOps principles, and reviews tools that generate docs from code comments, manage versioned design documents, and integrate testing, offering practical guidance for teams to streamline documentation and improve development efficiency.
This article explains the definition of operational standardization and outlines four core principles—best practice, modularity, templating, and simplicity—showing how they improve team efficiency, documentation consistency, and enable scalable, automated operations.
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.
After two years as an intern and eight months as a full‑time engineer at Microsoft Azure, I reflect on nine often‑overlooked corporate practices—from missing documentation and low enthusiasm to limited code review and reliance on outdated tools—that shape daily life for developers in large tech firms.
