0 views collected around this technical thread.
This article explains what a product feature list is, how it fits into product planning and architecture, outlines its benefits for development and MVP definition, describes common presentation formats, and emphasizes its dynamic nature while also mentioning a related DevOps hackathon event.
This article outlines Ctrip's hotel R&D team's systematic approach to boosting development efficiency through OKR alignment, MVP-driven value delivery, agile practice upgrades, and DevOps automation, detailing challenges, solutions, measurement metrics, and continuous improvement strategies.
This article explains how managing complexity by layering responsibilities and introducing an MVP architecture separates UI rendering from business logic in Android search features, illustrating the problems of high coupling and low cohesion with concrete Kotlin code examples and discussing AB testing and decorator patterns.
This article explains the Minimum Viable Product (MVP) concept, contrasts it with traditional waterfall development, and demonstrates how MVP can be used in game recommendation business to reduce risk, accelerate feedback loops, and enable agile iterative improvements.
This article presents thirty concise architectural principles—ranging from KISS and YAGNI to distributed system design, user experience, and configuration management—explaining each rule, offering practical commentary, and showing how they guide architects to build simple, maintainable, and scalable software systems.
By applying the DRY principle, the team abstracted audit requirements into a micro‑core plugin architecture, built a two‑week MVP for Xianyu’s community moderation, and demonstrated how systematic research, reusable patterns, and incremental evolution prevent duplicated effort and create a scalable, maintainable audit system.
The author chronicles his experience learning coaching, treats coaching as a product, and demonstrates how applying MVP principles and a DevOps mindset—through iterative releases, feedback loops, and metrics like lead time and NPS—can transform personal development into a systematic, customer‑focused process.
This article details how Ctrip's ticket‑search list page was refactored with clean‑architecture principles, introducing a unidirectional data flow, business Service layer, and plugin‑based aspect‑oriented modules to improve maintainability, testability, and cross‑platform reuse of front‑end code.
The article describes how a lightweight big‑data analysis platform called MVP was built from scratch—using a User‑Event‑Config model, HDFS + ClickHouse + Spark, and four modules for metric monitoring, root‑cause alerts, deep growth analysis, and A/B testing—enabling real‑time insights in seconds instead of days and dramatically accelerating product‑growth operations.
The article shares ten practical lessons from a senior full‑stack engineer covering CSS specificity, component state design, backend code organization, PostgreSQL performance, the pitfalls of rushing releases, automation investment, mastering tools, MVP thinking, research‑driven development, and systematic scientific debugging.
This article details the design and implementation of Ctrip's hotel Android map features, covering business background, module architecture, coordinate system handling, multithreading challenges, and practical solutions such as MVP, AsyncTask, and atomic flags to ensure smooth user experience.
This article examines why CEOs frequently change strategic directions, analyzes the information asymmetry between leadership and R&D, and presents four practical viewpoints—including decisive responsibility, enriching decision data, rapid MVP iteration, and aligning CEOs with user insights—to help teams navigate shifting priorities effectively.
This article walks through Android TV’s Leanback library—its purpose, how to add the dependency, and core components such as BaseGridView, Presenter, and ObjectAdapter—using the QQ Music TV app as a case study, while weighing its design advantages against maturity and update‑frequency drawbacks.
This tutorial walks through Android implementations of MVC, MVP (using Mosby), and MVVM (with DataBinding), providing concise explanations, annotated code snippets, and a unified demo that lets beginners quickly grasp the differences and start building each architectural pattern in just ten minutes.
The article uses the behind‑the‑scenes process of Friends Season 6 to illustrate agile concepts such as backlog, user stories, MVP, Scrum meetings and continuous delivery, showing how a sitcom’s production can serve as a model for effective R&D management.
This article shares how JD.com’s technology R&D center applied user story mapping to address common requirement‑grooming challenges, clarifying ambiguous PRDs, defining MVPs, estimating story points, planning versions and iterations, and ultimately delivering a store display system within 4.5 sprints, improving efficiency and stakeholder trust.
This article describes how a large, tightly‑coupled Android detail page was refactored into a clean, modular MVP architecture that splits business logic into reusable Parts, reducing the file size from over 2000 lines to fewer than 200 while improving readability, maintainability, and rendering performance.
The author recounts how discovering Agile and Extreme Programming in 2008 transformed his software development mindset, improved project delivery, and reshaped organizational and product design practices, illustrating both the benefits and challenges of adopting Agile in a traditionally waterfall‑focused environment.
This article explains why proper architectural design is essential for Android apps, compares the MVC, MVP, and MVVM patterns, analyzes their advantages and disadvantages, and demonstrates the practical benefits of MVVM through a real‑world delivery‑mode switching project.
This article reviews Android mobile architecture patterns—including MVC, MVP, MVVM, Flutter-derived framework, and Android Architecture Components—explaining their evolution, layer separation, and communication mechanisms such as object holding, interface contracts, and router-based dispatch, while providing illustrative code examples.