This article enumerates 35 common bad programming habits—ranging from code organization and team collaboration to testing and maintenance—and explains why they harm productivity, offering concrete advice on how to recognize and replace each habit with healthier practices.
The article presents five practical concepts—avoiding unnecessary uniqueness, modularizing code, separating concerns, enhancing readability, and choosing clear naming—to help developers write bug‑free, efficient, and easily maintainable code that reduces cognitive load and boosts productivity.
The article introduces Cable, Qunar's internal continuous integration platform that combines automated static code checks, environment validation, rapid feedback, and flexible configuration to improve development efficiency, reduce release failures, and enhance overall product quality within a fast‑paced online travel business.
Learn how to ensure high‑quality Java code throughout agile development by standardizing coding conventions, applying static analysis, writing unit tests, implementing continuous integration, and conducting thorough code reviews and refactoring, with practical tool recommendations and best‑practice guidelines for each step.
The article explains how to analyze a purchase‑order creation requirement, identify core domain objects, design a layered Java backend using the SSH framework, and implement clean, maintainable code with proper business‑rule validation and service‑DAO separation.
This article identifies why most code remains low‑quality despite many guidelines and presents four practical principles—single abstraction level, minimized indentation, clear expressions, and effective use of helper classes—that dramatically improve a team's coding standards.
This article curates a must‑read list of programming books covering coding best practices, design patterns, refactoring, project management, and personal development, offering concise insights so developers can deepen their knowledge, improve code quality, and grow their careers.
Godeyes is a cross‑platform static analysis tool that scans Android applications for crash‑related issues such as API incompatibilities, OOM risks, and uncaught exceptions, offering Eclipse, Android Studio, and Jenkins integrations along with customizable rules and detailed HTML reports.
This tutorial walks through preparing the PMD environment, exploring its directory structure, and step‑by‑step instructions for implementing a custom rule—such as enforcing braces on while loops—using both Java code and XPath expressions, including packaging and execution details.
Discover 26 practical agile development principles—from building test cases before code to avoiding premature optimization—that guide teams to deliver high-quality software efficiently, emphasizing incremental work, continuous testing, thoughtful design, and disciplined code management.
This article shares practical Java naming guidelines—avoiding meaningless letters, using proper English, handling singular/plural forms, boolean properties, method names, CRUD operations, and abbreviations—to help developers write clearer, higher‑quality code through disciplined naming practices.
The article humorously explores nine commonly discouraged programming habits—such as using goto, avoiding documentation, cramming code onto one line, omitting type declarations, and redefining operators—explaining why developers sometimes break rules and how these practices can affect code readability, maintainability, and performance.
Android Lint, Google’s static analysis tool, scans Android code for potential bugs and style violations, enabling developers to fix problems early, and Meituan enforces its use in the development pipeline so that any Lint-detected issues block merges into the main branch, ensuring higher code quality.
This article presents a comprehensive list of 17 essential PHP best‑practice tips—ranging from using absolute paths and custom loaders to proper output buffering, character encoding, session handling, and file permission management—to help developers write cleaner, more maintainable, and secure backend code.
This article examines the two main types of poor developers—‘cowboy’ programmers who rush code without maintainability and mediocre coders lacking competence—explores their harmful habits such as spaghetti code, endless bugs, and arrogance, and outlines how good developers differ through humility, responsibility, and continuous learning.
Android Lint is a static code analysis tool for Android that detects potential defects and optimization opportunities across correctness, security, performance, usability, accessibility, and internationalization, offering command‑line and IDE integration, customizable rules, and detailed HTML reports to improve code quality.
The article examines why developers often produce low‑quality, hard‑to‑maintain code, outlines common bad‑code patterns, discusses the limited benefits and high costs of refactoring, and offers practical advice for writing better, more maintainable software.
The article provides comprehensive guidelines for writing high‑quality functions, covering naming conventions, parameter design, and body implementation techniques such as reducing nesting, avoiding mutable inputs, and using clear verbs to improve readability, maintainability, and testability across programming languages.
The article argues that while writing code is essential, the true goal of developers is to minimize code through thoughtful design, using tools that reduce errors, and continuously refactoring to keep code clear, maintainable, and a harmless by‑product of solving problems.
This article explains how to objectively assess code quality by defining good code, discussing readability, documentation, exception handling, concurrency, performance, logging, maintainability, modularization and providing recommended reading, helping developers and reviewers establish consistent evaluation standards.
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 examines why developers produce low‑quality, hard‑to‑maintain code, describing common anti‑patterns such as unclear intent, unreadable logic, poor organization, and missing abstractions, and discusses the difficulties of refactoring such code, while offering insights into recognizing and improving code quality.
This guide walks you through installing Flake8 on CentOS 6.4 with Python 2.6, adding optional plugins, running the linter on your files, and integrating it into Git hooks to automatically enforce coding standards.
The article explains how to write robust, error‑free code by always using two‑branch if statements, handling return values and exceptions correctly, avoiding null‑pointer pitfalls, and steering clear of over‑engineering through practical examples and clear best‑practice guidelines.
This article outlines twelve practical techniques—including TDD, ATDD, CI, pair programming, code reviews, static analysis, coding standards, automation, refactoring, early demos, user testing, and team cohesion—that collectively raise software quality while reducing bugs and development costs.
This article outlines ten practical habits—from mastering fundamentals and labeling code to continuous learning and avoiding shortcuts—that can help any software developer grow into an exceptional programmer who writes clean, maintainable, and impactful code.
This article explores practical programming philosophies for writing robust, maintainable code by using exhaustive two‑branch if statements, proper error handling, disciplined null‑pointer management, and avoiding over‑engineering, offering concrete examples and guidelines for Java and other languages.
These ten detrimental coding habits—ranging from misspelled identifiers and poor formatting to hard‑coded passwords and premature optimization—illustrate how bad practices can reduce efficiency, increase bugs, and jeopardize security, emphasizing the need for disciplined, modular, and well‑structured development.
While many developers know they should avoid certain coding shortcuts, this article reveals nine surprisingly common bad programming habits—like using goto, skipping documentation, over‑compressing code, and redefining operators—that programmers often cling to, explaining their origins, risks, and occasional hidden benefits.
The article argues that visible over‑time and frantic activity often mask poor software design, while quieter teams that focus on solid architecture, SOLID principles, and unit testing deliver higher quality code, challenging traditional notions of effort in tech management.
This article outlines six practical habits for developers—self‑checking code before blaming tools, continuous learning, embracing refactoring, acting professionally, using static analysis, and genuinely caring about code quality—to improve productivity and reduce bugs in any software project.
A graduate student recounts the shocking code quality issues he found in his team's data‑mining project, highlighting bad naming, massive classes, duplicated logic, overuse of singletons, excessive comments, and other anti‑patterns that jeopardize maintainability and graduation.
The article argues that while programmers obsess over performance gains, maintainability is often more critical, illustrating this with C# LINQ vs Single/First debates, database design pitfalls, and the hidden costs of premature optimization, ultimately urging developers to prioritize readable, maintainable code and measure performance before refactoring.
Quora shares how it sustains high‑quality code while accelerating development by applying four quality principles and implementing specialized tools and processes across writing, review, testing, and legacy cleanup stages, offering a practical model for other engineering teams.
The article examines Quora's engineering practices—including static analysis, post‑commit code review, automated testing, and systematic legacy code cleanup—that enable the company to maintain high code quality while sustaining fast development cycles.
This article explains how to improve code quality by focusing on three essential attributes—readability, maintainability, and changeability—offering practical advice, design‑pattern examples, and coding conventions that help developers write clearer, more adaptable, and easier‑to‑maintain software.
Learning the core programming language rather than relying on heavy frameworks, building small independent modules, and keeping code minimal and readable improves flexibility, performance, maintainability, and reduces bugs, ultimately leading to higher productivity and better collaboration among developers.
The article explains how cyclomatic complexity, method and class length, and internal class coupling affect code maintainability, and demonstrates how tools like PMD and JavaNCSS can be configured to detect and refactor overly long or tightly coupled code structures.
This article introduces five key aspects of Java code quality—coding standards, duplicate code, test coverage, dependency analysis, and complexity analysis—and demonstrates how Eclipse plugins such as CheckStyle, PMD, EclEmma, JDepend, and Metrics can be configured and used to assess and improve each aspect.
The article argues that the perceived trade‑off between development speed and code quality is a misleading premise, explaining how short‑term shortcuts harm long‑term productivity while disciplined, high‑quality practices actually accelerate delivery and improve product outcomes.
The article argues that striving for flawless code is futile because most software constantly evolves, and it advocates focusing on correctness, readability, and pragmatic refactoring rather than chasing unattainable perfection.
While elegant, well‑crafted code can be admired, the article argues that treating software as art often distracts from practicality, emphasizing that true programming excellence is measured by efficiency, reliability, and rapid problem‑solving rather than aesthetic bragging.
