This comprehensive guide explains Python coding style best practices, covering PEP 8 extensions, flexible line length, naming conventions, docstring standards, functional versus object‑oriented design, testing, standard library usage, third‑party tools, and project structure to produce readable, maintainable code.
This article presents a detailed guide to modern Java development, covering coding style, immutable data structures, builder patterns, dependency injection, null handling, formatting, Javadoc, streams, publishing strategies, Maven configuration, CI tools, repository management, configuration automation, essential development tools, and a curated list of widely used Java libraries.
The article outlines the design principles, modular architecture, front‑back separation, lifecycle management, testing, and deployment strategies of Alibaba’s Detail platform, aiming to improve collaboration efficiency, stability, extensibility, and reuse across various business scenarios.
The article examines how Google maintains high code quality through rigorous code reviews, strict style guides, active code‑health initiatives, fix‑it events, and a strong testing culture, while also discussing the perception that older code inevitably degrades.
This article explains how to configure Android Studio for Robotium testing, create and run test cases, and integrate automated tests into a Gradle‑based continuous integration pipeline using Jenkins.
The article examines how concise, efficient, and simple development practices, agile iteration, automated testing, and thoughtful tool selection can boost individual and team productivity while maintaining software quality, offering practical examples and strategic guidance for optimizing software development processes.
Learn how to achieve comprehensive code coverage for multi‑process Node.js applications by using Istanbul, instrumenting child processes, writing Mocha tests, and merging coverage reports, with detailed examples of master‑worker RPC, custom fork hacks, and package.json scripts for automated testing.
The article outlines Baidu Cloud's comprehensive quality assurance framework—including testing technologies, specialized safeguards, and a multi‑stage QA evolution—demonstrating how data integrity, performance, and user experience are continuously measured, monitored, and improved for a cloud storage service serving hundreds of millions of users.
An in‑depth overview of KISSY, Alibaba’s home‑grown front‑end framework, covering its origins, architectural layers, modular system, component library, tooling, mobile support, testing, CI, and real‑world deployment examples such as shop and product detail pages, highlighting strengths and current challenges.
This article introduces six versatile Python libraries—Pyglet, Peewee, Bottle, Invoke, Splinter, and Arrow—that help developers quickly solve common tasks, from multimedia handling and database access to web APIs, automation, and date‑time processing, while remaining robust for larger projects.
This guide explains how to apply clean architecture principles to Android development by separating concerns into presentation, domain, and data layers, ensuring framework, UI, and database independence, and providing testing strategies and error‑handling techniques for a maintainable app.
This article details the evolution of Mobile Taobao's engineering architecture, development workflow, and quality assurance measures across three phases, illustrating how modularization, automated platforms, and rigorous testing practices enabled high‑quality continuous delivery for a large‑scale mobile application.
The article emphasizes that programmers achieve the software engineering iron triangle of cost, speed, and correctness by thoroughly understanding problems, crafting clear designs, listing test conditions, considering impacts on other components, and anticipating future issues, urging a slower, long‑term perspective before diving into code.
This article explains why H5 performance matters, defines the one‑second rule for different network conditions, and provides comprehensive front‑end optimization techniques—including resource loading, image handling, server deployment, code standards, testing tools, and classic case studies—to improve user experience on mobile web applications.
Over the past two months I helped develop a distributed hybrid‑cloud platform, tackling challenges from OS differences and network ports to message queues, logging, multi‑language integration, and testing, and I share the architectural decisions, tooling choices, and practical lessons learned for building robust backend systems.
This guide explains how to use Redis's built‑in redis-benchmark tool to measure the throughput of local or remote Redis instances, covering basic testing, selective command benchmarking, and remote server testing with practical command examples.
This article provides an extensive overview of modern JavaScript development, covering the transition to ES2015, module systems, build tools like Webpack, testing frameworks, process automation, code quality tools, Git workflows, client‑side templating, and essential Node.js knowledge for frontend engineers.
The article outlines thirteen critical production‑related mistakes—from not externalizing configuration and using inadequate test data to neglecting security, documentation, disaster‑recovery planning, and proper capacity planning—providing actionable guidance for developers and architects to improve system stability and performance.
The article explains how over‑complex mental models, poor translation of semantic ideas into code, inadequate naming, missing design chunks, unclear usage patterns, and lack of smooth model transitions cause code to decay, and offers practical principles such as DDD, SRP, good naming, testing, and reusing existing algorithms to maintain readability.
A recent study of five major open‑source distributed systems reveals that most failures can be triggered and reproduced with simple, multi‑event tests, highlighting the importance of systematic testing, deterministic error handling, and concise logging for reliable system operation.
The article provides a detailed, data‑driven look at Google’s internal software development practices, covering unified trunk code management, pervasive code visibility, rigorous reviews, feature‑flag experimentation, strict testing, and the blend of Java, C++, and JavaScript in front‑end and back‑end work.
When inheriting tangled legacy code, first decide if you’re responsible and willing to invest, then establish comprehensive tests, use version control, make incremental changes, separate cleaning from bug fixing, remove dead code and comments, avoid mutable shared state, and eliminate unnecessary complexity to improve maintainability.
