BestHub
Sign in
Tagged articles

refactoring

426 articles · Page 5 of 5
Qunar Tech Salon
Qunar Tech Salon
May 24, 2016 · Backend Development

Lessons from Three System Architecture Refactorings: Balancing Business Continuity and Technical Improvement

The article shares practical experiences from refactoring three backend systems—M, S, and X—highlighting the challenges of keeping business running while redesigning architecture, the concrete solutions applied, measurable outcomes such as increased release frequency and higher availability, and key lessons on prioritizing problems and avoiding over‑refactoring.

System Designarchitecturerefactoring
0 likes · 7 min read
Lessons from Three System Architecture Refactorings: Balancing Business Continuity and Technical Improvement
Architect
Architect
May 15, 2016 · R&D Management

Strategic Phased Approach to System Architecture Refactoring

The article outlines how to effectively tackle extensive architecture refactoring by prioritizing issues, classifying them, and implementing a phased strategy that focuses limited resources on specific problem categories to achieve clear, incremental results and maintain team morale.

PrioritizationSystem Designphased implementation
0 likes · 9 min read
Strategic Phased Approach to System Architecture Refactoring
21CTO
21CTO
May 13, 2016 · Backend Development

How to Refactor a Live Backend System Without Stopping the Business

The article shares practical experiences and lessons learned from three large‑scale backend architecture refactorings, explaining why doing business‑critical changes while keeping services online is the toughest challenge and how to identify and solve the most critical problems first.

Backendhigh availabilityrefactoring
0 likes · 8 min read
How to Refactor a Live Backend System Without Stopping the Business
Architecture Digest
Architecture Digest
Apr 21, 2016 · Backend Development

Evolution and Refactoring of Autohome Mobile Backend Architecture

The article chronicles Autohome's mobile backend transformation from a monolithic ALL‑IN‑ONE design to a modular, high‑availability microservice architecture, detailing the challenges of traffic surge, resource coupling, and rapid releases, and describing the adopted solutions such as service decomposition, stateless design, Java migration, RPC framework, asynchronous components, and comprehensive monitoring and tracing.

microservicesmobilemonitoring
0 likes · 11 min read
Evolution and Refactoring of Autohome Mobile Backend Architecture
Qunar Tech Salon
Qunar Tech Salon
Mar 27, 2016 · Backend Development

Understanding Architecture Corruption and How to Mitigate It

The article examines why software architectures inevitably degrade over time in long‑running projects, analyzes the stages of decay, and presents practical strategies—including environment upgrades, phased and distributed builds, component isolation, and platform‑plus‑app designs—to keep systems maintainable and performant.

Build Optimizationarchitecturecontinuous integration
0 likes · 23 min read
Understanding Architecture Corruption and How to Mitigate It
21CTO
21CTO
Mar 10, 2016 · Fundamentals

How to Write Clear, Maintainable Functions: Naming, Parameters, and Structure

This article explains practical techniques for writing high‑quality functions, covering consistent naming conventions, descriptive function names, optimal parameter handling, clean function bodies, reduced nesting, and other best‑practice tips to improve readability and testability.

Best PracticesCode Readabilityfunction design
0 likes · 13 min read
How to Write Clear, Maintainable Functions: Naming, Parameters, and Structure
21CTO
21CTO
Mar 1, 2016 · Fundamentals

Why Bad Code Survives and How Refactoring Can Save Your Projects

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.

Software Engineeringbad code patternscode quality
0 likes · 12 min read
Why Bad Code Survives and How Refactoring Can Save Your Projects
21CTO
21CTO
Feb 23, 2016 · Fundamentals

Why Writing Less Code Makes You a Better Developer

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.

Software Engineeringcode minimizationcode quality
0 likes · 4 min read
Why Writing Less Code Makes You a Better Developer
21CTO
21CTO
Feb 4, 2016 · Fundamentals

12 Essential Rules for Successful Architecture Refactoring by Uber’s Raffi Krikorian

This article presents Uber engineering leader Raffi Krikorian’s twelve practical rules for planning, executing, and validating architecture refactoring, covering purpose definition, incremental delivery, data handling, technical debt, technology choices, pressure management, business alignment, non‑technical factors, code quality, and team readiness.

Best Practicesengineering managementincremental development
0 likes · 13 min read
12 Essential Rules for Successful Architecture Refactoring by Uber’s Raffi Krikorian
21CTO
21CTO
Jan 14, 2016 · R&D Management

Why Software Architectures Decay Over Time and How to Fight It

The article examines why long‑running software projects inevitably see their architectures degrade, explores the stages of decay, and presents practical strategies—such as environment upgrades, phased and distributed builds, tooling, modular refactoring, and process isolation—to mitigate the problem.

Build Optimizationproject scalingrefactoring
0 likes · 24 min read
Why Software Architectures Decay Over Time and How to Fight It
High Availability Architecture
High Availability Architecture
Jan 13, 2016 · Fundamentals

Bad Code: Causes, Symptoms, and Refactoring Challenges (Part 1)

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.

Best PracticesSoftware Engineeringbad code
0 likes · 15 min read
Bad Code: Causes, Symptoms, and Refactoring Challenges (Part 1)
Java High-Performance Architecture
Java High-Performance Architecture
Jan 12, 2016 · Backend Development

Refactoring a Legacy Transaction System to Java: Strategies and Process

Facing high maintenance costs, complex business demands, and costly Microsoft tech, a company migrated its five‑year‑old transaction platform to Java, employing phased refactoring, comparative testing, and traffic‑splitting to ensure correctness, minimal impact, and a smooth, zero‑downtime rollout with centralized configuration and logging.

BackendSystem Designrefactoring
0 likes · 5 min read
Refactoring a Legacy Transaction System to Java: Strategies and Process
21CTO
21CTO
Dec 22, 2015 · Fundamentals

12 Proven Practices to Dramatically Boost Code Quality

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.

Code Reviewautomationcode quality
0 likes · 8 min read
12 Proven Practices to Dramatically Boost Code Quality
Qunar Tech Salon
Qunar Tech Salon
Dec 22, 2015 · Fundamentals

Programming Philosophy: Writing Elegant, Modular, and Readable Code

The article presents a comprehensive philosophy on software development, emphasizing the importance of repeatedly refining code, structuring it elegantly, modularizing with clear functions, avoiding unnecessary comments, and adopting simple, intuitive practices to improve readability and maintainability across any programming language.

Best PracticesCode ReadabilityProgramming Philosophy
0 likes · 27 min read
Programming Philosophy: Writing Elegant, Modular, and Readable Code
21CTO
21CTO
Nov 21, 2015 · Backend Development

How to Become a Successful Web Architect: Essential Skills & Roadmap

This article outlines the common pitfalls programmers face on the path to web architecture, emphasizes mastering object‑oriented fundamentals, design patterns, and refactoring, and provides a detailed roadmap of the technical, operational, and managerial knowledge required to become a competent web architect.

Design PatternsSoftware Engineeringbackend development
0 likes · 19 min read
How to Become a Successful Web Architect: Essential Skills & Roadmap
ITPUB
ITPUB
Nov 13, 2015 · Backend Development

Eliminate Code Segregation: Writing Cleaner, More Elegant PHP

This article shows how to transform fragmented PHP snippets—such as disjointed loops, scattered timing code, and split error‑code definitions—into cohesive, readable structures using for‑loops, functional helpers, shutdown callbacks, and modern constant arrays, improving both aesthetics and maintainability.

BackendBest PracticesCode style
0 likes · 5 min read
Eliminate Code Segregation: Writing Cleaner, More Elegant PHP
21CTO
21CTO
Oct 16, 2015 · Fundamentals

Master Extract Method Refactoring: Simplify Your PHP Code with Real Examples

This article explains the Extract Method refactoring technique, its definition, benefits, and step‑by‑step PHP examples that show how to split a long method into smaller, well‑named methods, improving readability, reusability, and adherence to the Single Responsibility Principle.

Code Readabilityextract-methodrefactoring
0 likes · 10 min read
Master Extract Method Refactoring: Simplify Your PHP Code with Real Examples
21CTO
21CTO
Oct 6, 2015 · Fundamentals

How to Tame Legacy Code: Proven Strategies for Effective Cleanup

This guide walks you through practical steps for assessing, testing, version‑controlling, incrementally refactoring, and simplifying messy legacy code so you can safely improve maintainability without introducing new bugs.

code cleanuplegacy coderefactoring
0 likes · 14 min read
How to Tame Legacy Code: Proven Strategies for Effective Cleanup
MaGe Linux Operations
MaGe Linux Operations
Aug 21, 2015 · Fundamentals

Why Good Architecture Should Be Business‑Independent: Real‑World Refactoring Insights

In this talk, senior architect Neeke shares practical experiences and lessons on software architecture and refactoring, using bridge and building analogies to illustrate how business‑agnostic design, careful analysis of existing support points, and incremental restructuring can transform fragile systems into robust, maintainable solutions.

System Designbusiness independencerefactoring
0 likes · 9 min read
Why Good Architecture Should Be Business‑Independent: Real‑World Refactoring Insights
21CTO
21CTO
Aug 17, 2015 · R&D Management

Why Do Software Architectures Decay Over Time and How to Stop It?

The article examines why software architectures inevitably degrade in long‑running projects, explains the stages of decay, and presents practical strategies—such as upgrading environments, phased and distributed builds, component isolation, and platform‑plus‑app designs—to keep systems maintainable and performant.

codebase decaymodularizationrefactoring
0 likes · 24 min read
Why Do Software Architectures Decay Over Time and How to Stop It?
MaGe Linux Operations
MaGe Linux Operations
Jun 26, 2015 · Fundamentals

Master Git Undo: Revert, Reset, Rebase, and More

This guide explains common Git undo scenarios—reverting public commits, amending messages, discarding local changes, resetting history, using reflog, branching tricks, interactive rebasing, and stopping file tracking—providing clear commands, underlying principles, and practical tips for safely managing version control mistakes.

Gitrebaserefactoring
0 likes · 15 min read
Master Git Undo: Revert, Reset, Rebase, and More
Architect
Architect
May 12, 2015 · Fundamentals

12 Rules for Successful Architecture Refactoring – Insights from Uber’s Raffi Krikorian

The article presents Uber engineering leader Raffi Krikorian’s twelve practical rules for planning, executing, and managing software architecture refactoring, emphasizing clear purpose, measurable goals, incremental delivery, data‑driven decisions, technical debt control, realistic technology choices, and stakeholder communication.

data-drivenincremental deliverymanagement
0 likes · 13 min read
12 Rules for Successful Architecture Refactoring – Insights from Uber’s Raffi Krikorian
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
May 12, 2015 · Industry Insights

How to Avoid the Hype: Practical Rules for Successful Architecture Refactoring

This article offers goal‑oriented, data‑driven advice and checklists for architecture refactoring, emphasizing realistic technology selection, pressure management, business understanding, handling non‑technical influences, code‑quality practices, and team readiness to ensure effective, sustainable redesigns.

Best PracticesChecklistarchitecture
0 likes · 7 min read
How to Avoid the Hype: Practical Rules for Successful Architecture Refactoring
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
May 7, 2015 · Fundamentals

12 Rules for Successful Architecture Refactoring – Insights from Uber’s Engineering Leader

The article presents Uber engineering manager Raffi Krikorian’s twelve practical rules for planning, executing, and evaluating software architecture refactoring, emphasizing clear purpose, measurable goals, incremental delivery, current state assessment, data‑driven decisions, and diligent management of technical debt.

incremental deliveryrefactoringsoftware design
0 likes · 8 min read
12 Rules for Successful Architecture Refactoring – Insights from Uber’s Engineering Leader