This article presents a detailed skill‑tree and practical learning roadmap for software engineers, covering computer fundamentals, data structures, Java core concepts, multithreading, JVM internals, databases, distributed systems, personal branding, and effective study methods such as videos, books, and paid resources.
This guide explains why reading framework source code is essential for developers, outlines step‑by‑step methods such as researching online, scanning packages, locating entry points, systematic reading, organizing insights, and applying critical thinking to deepen understanding and improve coding practice.
The project report details how the Virtual General Service Voucher Center Phase II was delivered using agile methods, achieving higher delivery speed, improved quality, and greater business satisfaction through iterative planning, visual kanban boards, daily stand‑ups, self‑organizing teams, engineering best practices, continuous improvement, and active stakeholder involvement.
The article explains how lacking a real‑time functional requirements design document leads to high communication costs, misaligned expectations, costly rework, and testing nightmares, and it offers practical guidance on where to store, what to include, and how to maintain document quality for successful software development.
Learn how to use Git's cherry-pick command to selectively copy individual or ranges of commits from one branch to another, with step‑by‑step examples, command syntax, and tips for handling multiple commits and postponing automatic commits.
The article examines why many large, well‑known tech companies suffer from messy code, chaotic development processes, and reliance on outdated technologies, exploring the underlying personnel dynamics, reconstruction costs, and the tension between business and technical value.
This article explains the importance of version control systems for collaborative software development, outlines the differences between distributed and centralized VCS, offers best‑practice guidelines, and compares popular open‑source tools like Git, Mercurial, and SVN.
This article shares practical, experience‑based advice on introducing agile methods in software projects, emphasizing tailoring practices to specific contexts, problem‑driven adoption, and essential rules such as physical Kanban boards, daily stand‑ups, and clear Scrum roles, illustrated with multiple real‑world case studies.
This article explains the concept and advantages of continuous integration, outlines a typical CI workflow including submission, testing, building, deployment and rollback, discusses challenges in test case management, reviews popular CI tools such as Jenkins and Qone, and details code‑coverage measurement using Jacoco with Maven configuration.
The article recounts how a monolithic 66,000‑line home‑page system with high latency and tangled logic was re‑engineered through clear direction, module‑based design, and incremental changes, resulting in dramatically faster feature rollout, lower learning cost, and improved performance metrics.
Through a series of candid developer anecdotes—ranging from accidental production database truncations and hidden mistakes to the dangers of coding while exhausted and the importance of version control—this article highlights practical lessons for safer coding practices, rigorous reviews, and disciplined operational procedures.
This article explains Git’s four areas (working, staging, local repository, remote repository) and five file states (origin, modified/untracked, staged, committed, pushed), detailing step‑by‑step commands such as git add, commit, push, and how to revert changes using git reset, checkout, and clean.
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.
The Elasticsearch Team Development Constitution outlines a comprehensive set of principles and guidelines—covering design philosophy, code quality, interaction etiquette, and organizational responsibilities—to help the rapidly growing project evolve into a reliable, secure, scalable, and user‑friendly distributed search engine.
Understanding and applying solid methodologies—such as design patterns, coding standards, and domain‑driven design—constitutes the core of software development best practices, helping programmers evolve from “wild” coders to professionals who write clean, maintainable code and continuously improve through disciplined practice.
This article compiles a series of Chinese-language resources on user story mapping, explaining how the technique helps agile teams create clearer backlog, prioritize features, and plan releases, offering both theoretical background and practical steps for effective implementation.
The article argues that, in most cases, developers who work on Linux gain skills faster than those who stay on Windows because of richer open‑source resources, fewer APIs to master, and easier access to high‑quality reference implementations.
This article recounts how a small, multi‑disciplinary channel development team applied a customized Kanban‑based agile process to overcome tight schedules, heavy workloads, and a critical three‑day emergency feature request, demonstrating both the strengths and limits of agile in fast‑changing environments.
LightMerge, Ctrip’s integration accelerator, addresses the challenges of merging multiple feature branches by automatically detecting conflicts, merging selected branches, and integrating with CI pipelines, thereby streamlining the multi‑feature branch release process and improving development efficiency and code quality.
This article describes how the Agricultural Bank's software development center introduced daily builds, automated testing, Kanban boards, and Scrum stand‑ups across three phases to boost development efficiency, product quality, and team collaboration, sharing lessons learned and outcomes from the pilot projects.
This article explains why open‑source software is vital, defines what open source means, and provides a detailed, illustrated workflow—from forking a repository on GitHub to creating pull requests and merging code—so developers can start contributing effectively.
This article presents typical developer‑product manager interactions, highlights common wrong replies, and provides concise, professional answers that improve collaboration, reduce friction, and keep projects on track.
This article outlines nine recurring problems—from mismatched teams and unrealistic requirements to relentless overtime and ignored personal lives—that drain developers' energy and sabotage software projects, offering insight into how these issues arise and why they persist.
The 2018 Stack Overflow Developer Survey, with over 100,000 respondents, reveals that most developers are relatively new, many lack formal CS degrees, enjoy high job security, favor JavaScript and SQL tools, and display distinct demographic and ethical trends across the global software industry.
The article explains how DevOps combines culture, practices, and tooling to enable organizations to deliver applications and services more rapidly by breaking down silos between development and operations, fostering cross‑functional collaboration, automation, and continuous improvement throughout the software lifecycle.
This article explains why agile development is needed, outlines its advantages over traditional waterfall methods, defines agile and scrum, and provides practical guidance on preparing teams, tools, and processes before launching an agile project.
This article shares ten practical pieces of advice for programmers—from thinking before coding and communicating clearly with product managers, to writing documentation and comments, handling changing requirements, prioritizing business value, testing thoroughly, solving problems independently, and using new technologies wisely.
The article explains that there is no universal silver‑bullet methodology for software projects; instead, teams must analyze each project's unique variables, blend existing frameworks, and continuously refine a simple, tailored process to achieve effective results.
This article explains why developers should incorporate diagramming into their workflow, outlines three key uses—understanding problems, facilitating team communication, and merging ideas—reviews various media from pen‑and‑paper to code‑generated charts, and offers practical tips for creating clear, effective diagrams.
The article outlines a three‑stage learning path for Python—from mastering basic syntax and common libraries, through intermediate mastery of domain‑specific tools and Pythonic coding practices, to advanced project‑level considerations like documentation, distribution, and performance optimization—while recommending key books for each stage.
Creating an internal developer community fosters open feedback, trust, and collaboration, enabling managers to gather valuable insights, improve documentation and tooling, and ultimately deliver products that meet user expectations and drive higher retention across emerging fields like IoT.
This reflective essay examines how agile development, flat management, and engineering culture intersect, contrasting traditional control‑heavy standards like ISO9000 and CMM with the open, collaborative approaches exemplified by Linux, Scrum, and modern tech giants, and explores how organizations can nurture both rigor and innovation.
This article provides a comprehensive guide to software project management, covering risk assessment, cost budgeting, client communication, requirement analysis, development planning, quality assurance, and product delivery to help teams deliver successful software solutions.
This article compiles the free ebook portals of leading English‑language publishers such as O'Reilly, Packt, Manning, Apress, and Microsoft Press, summarizing their offerings across topics like big data, AI, web development, and more for developers seeking quality learning resources.
This article shares a practical five‑step workflow—rehearsal, design, foundation, implementation, and cleanup—plus two simple techniques, tagging and daily review, that help developers make their work processes more conscious, focused, and productive.
Alibaba’s entertainment advertising CRM team replaced a slow waterfall process with a cross‑functional One Team and bi‑weekly iterations, cutting development time from 12 to under 6 days, delivery to under 20 days, improving collaboration, feedback loops, and overall product quality.
This article explores how the evolving titles for software creators—from programmer to developer to engineer—reflect shifting expectations, responsibilities, and cultural perceptions within teams and management, offering guidance on choosing the right model for modern development groups.
Lei Jun shares his unexpected path to programming, the joy he finds in coding, and practical advice on staying curious, focusing on users, and treating software development as both disciplined craftsmanship and creative art to build a lasting career.
This article explores the essential tools, methods, and developer habits needed to produce high‑quality, maintainable code, emphasizing why automation alone isn’t enough and outlining concrete code‑review steps that ensure reliability and alignment with product requirements.
This article presents eight hands‑on project ideas—from cloning Trello and building a user‑management dashboard to creating a native cryptocurrency tracker and a Messenger clone—designed to strengthen your coding skills across frontend, backend, and mobile development while teaching essential tools like React, Redux, Webpack, and APIs.
This article shares a detailed, experience‑based framework for project managers to successfully lead cross‑company, multi‑team software collaborations by dividing work into planning, implementation, and delivery phases, emphasizing risk identification, schedule coordination, change handling, and continuous external communication.
This article provides a concise historical overview of various software development methods and practices, emphasizing the importance of understanding their origins to better comprehend current development approaches.
The article compares the classic waterfall software development model with iterative development, outlines the drawbacks of the former, highlights the six advantages of iteration, and details a multi‑iteration parallel approach with QA and release‑cycle practices for improved project control and product quality.
This reflective essay explores how programming knowledge decays over time, outlines three career stages, and offers practical strategies for senior developers to invest in durable skills and sustain long‑term growth.
The author reflects on years of programming experience, urging beginners to master core computer science subjects such as discrete math, algorithms, operating systems, and architecture, arguing that solid fundamentals prevent costly missteps when later learning frameworks like .NET, Java, or web technologies.
The article emphasizes that mastering core computer science subjects such as discrete mathematics, algorithms, operating systems, computer architecture, and compilers is essential for building solid programming skills and avoiding future difficulties when learning higher‑level frameworks and languages.
The article reflects on the deep divide between core and business development teams, emphasizing the need for thick‑skinned communication, structured feedback channels, realistic expectations, and proactive platform management to turn criticism into constructive collaboration.
This article shares practical, step‑by‑step methods for programmers to improve code quality, reduce endless bug fixing and overtime, and cultivate disciplined habits such as focused planning, thorough requirement analysis, ignoring unnecessary quality checkpoints, writing readable code, and deliberate practice.
The article recounts how a brilliant but isolated developer named Rick became a bottleneck, leading the team to miss deadlines, and how firing him forced a shift to collaborative development that dramatically improved productivity and reduced technical debt.
The article examines why software projects often suffer from the paradox of many team members, few deliverables, and heavy workloads, identifying issues such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architecture that collectively drain efficiency.
The article outlines seven essential qualities—positive attitude, communication, time management, rapid learning, deep technical experience, teamwork, and user‑centric thinking—that distinguish top developers and offers practical ways to assess each trait during hiring and development.
This article surveys twenty indispensable DevOps tools—from project tracking with Jira and version control with Git to containerization with Docker and monitoring with New Relic—explaining their core functions, typical use cases, and how they fit into a modern software development lifecycle.
The iQIYI Literature vertical uses a streamlined four‑stage agile workflow—review, scheduling, development, release—combined with dynamic process tweaks, tight baseline coupling, branch‑isolated CI/CD, and layered quarterly, monthly, and weekly planning, enabling rapid product iterations and sustained growth into a recognized brand.
This article outlines eight key responsibilities for CTOs—from strategic thinking and rapid decision‑making to effective communication, team management, and staying ahead of technology trends—to help leaders guide their teams and deliver valuable products.
This article presents a comprehensive, visual overview of core Python concepts—including basic syntax, data types, control flow, file handling, exceptions, functions, modules, and object‑oriented programming—organized as a series of mind‑map diagrams to aid beginners in structured learning and deeper understanding.
The article explains how developers can achieve ten‑times productivity by focusing on three core questions—what to do, why it matters, and when to act—while emphasizing experience, problem‑solving, clear communication, prioritization, and the right balance between architecture and code.
The article uses the hammer metaphor to critique treating agile methods as a one‑size‑fits‑all tool, illustrating common misunderstandings through dialogues about user stories, estimation, TDD, pair programming, Kanban, Scrum, SAFe, and continuous delivery, and urging thoughtful adoption.
GitHub’s recent announcements reveal massive repository growth, a new dependency‑graph tool that adds security alerts, AI‑driven code recommendations, and an updated Explore feed, all pointing toward a future where developers write less code and rely more on automation and data‑driven insights.
This article introduces the Chinese translation of "Functional Light JavaScript," explaining the book’s focus on lightweight functional programming concepts in JavaScript, the author’s journey, the core philosophy, a detailed table of contents, and where to find the open‑source translation.
A seasoned developer explains his personal approach to quickly learning new programming languages, critiques beginner tutorials, and presents three concise exercises that help experienced programmers efficiently grasp syntax, handle input, and practice control structures in any language.
This article compiles fifteen core Python interview questions—covering language basics, code snippets, multi‑threading, decorators, garbage collection, and version control—each with detailed answers, explanations of why they matter, and visual examples to help candidates ace Python developer interviews.
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.
Oracle announced that Java will adopt a strict six‑month release cadence, with the next version slated for March 2018, shifting from the previous two‑year cycle and ensuring future releases in March and September without delays for unfinished features.
This guide showcases practical Pythonic techniques—including variable swapping, efficient range iteration, string joining, context-managed file handling, optimal list operations, destructuring assignments, and comprehensions—to help developers write clearer, more memory‑efficient Python code while avoiding common pitfalls.
The article examines the recurring bugs and reliability issues in Linux file systems—especially ext4—highlighting Linus Torvalds' criticism, POSIX shortcomings, fuzz‑testing results, historical bug statistics, and practical advice for developers to avoid data‑loss pitfalls.
A Google AdMob engineer measured his own and his teammates' daily code changes, finding an average of about 150 lines per day, which leads to an estimate of roughly four million lines of code written across Google every day.
To distinguish yourself among Java developers, focus on mastering core OOP principles, essential APIs, continuous coding, community engagement, blog interaction, studying open‑source frameworks, tracking tech trends, maintaining reusable code snippets, understanding various development methodologies, and documenting your insights for sharing.
This article examines the shortcomings of traditional software development, explains the concepts of continuous integration and CI servers, outlines the benefits of adopting CI, and provides practical best‑practice recommendations while also addressing common challenges teams may face.
This article examines the PYPL Top IDE Index, revealing that Visual Studio, Eclipse, and Android Studio were the three most searched IDEs in August, while explaining the methodology, limitations of search‑based popularity metrics, and offering follow‑up questions for developers.
This article reviews eight up‑and‑coming programming languages—Swift, Go, TypeScript, Rust, Kotlin, Clojure, Haskell, and R—detailing their origins, key features, community adoption, and GitHub star counts to highlight their potential impact on software development in the coming years.
This article shares a programmer’s personal insights on industry traits, the three main types of Chinese software companies, and practical guidance for choosing career routes such as continued development, architecture, technical management, or project management.
This article chronicles Yukihiro Matsumoto’s journey from his early fascination with computers in school, through his self‑taught language experiments and the creation of Ruby during Japan’s economic downturn, to his reflections on programming as a lifelong, creative, and human‑centered pursuit.
This article explains why package managers are essential, showcases Yarn's step‑by‑step tutorial for creating a simple package manager, and highlights how the resulting tool handles classic challenges like circular dependencies and file‑structure optimization.
This article recounts how the Taobao Live team applied agile practices over three months, tracking capacity, lead time, quality, and predictability, and demonstrates measurable improvements in delivery speed, defect reduction, and business metric alignment through focused goals, rapid hypothesis testing, and continuous delivery.
The article argues that making "architect" a permanent job title is misguided, advocating instead that architecture be treated as a flexible role shared by senior developers who stay involved in coding and collaborate on design decisions to avoid over‑design and team friction.
Lu Qi, former Baidu CTO, shares five essential principles—believing in technology, building on others' work, pursuing engineering excellence, learning daily, and taking ownership—to help software engineers elevate their mindset and impact in the AI‑driven era.
The article explains how Huawei transformed from the world’s largest device maker into a top ICT software solutions supplier by embracing open‑source technologies, collaborating with the Linux Foundation, and driving innovations in cloud‑native, big‑data, and networking ecosystems.
This article presents a detailed, game‑like learning roadmap for programmers, recommending foundational scripting languages, Unix/Linux mastery, web development, databases, C/C++ and Java, system programming, design patterns, and advanced topics such as distributed systems and big‑data technologies to guide career growth.
The article illustrates five typical ways requirements are expressed in software projects—from leader‑driven oral requests and vague “half‑cooked” specifications to detailed document‑heavy, prototype‑driven, and client‑participation models—highlighting the challenges and impacts each pattern has on development and delivery.
The article explains why many hiring posts that claim they only need one programmer are misguided, highlighting disrespect, underestimation of effort, misunderstanding of project scope, and premature recruitment, and offers practical advice for both employers and developers.
The article shares thirteen practical lessons learned from years of software development, covering starting small, incremental changes, early logging and error handling, thorough testing, creating a safe learning environment, embracing leadership without titles, coding regularly, abstract thinking, and the importance of personal financial safeguards for long‑term career growth.
This article explores why time is a precious resource for programmers, outlines effective project time tracking methods, and offers practical strategies—such as structured schedules, accurate estimations, work‑life balance, and innovative tracking tools—to improve productivity and reduce overtime.
This article shares several agile process‑improvement case studies—from enhancing team responsiveness and communication to building strong engineering culture—offering practical guidance on establishing visibility, efficient decision‑making, minimizing re‑planning costs, and fostering high‑quality, cross‑functional delivery teams within software development.
This article explains the true practice of Continuous Integration, introduces Martin Fowler’s definition, details a six‑step commit workflow (the “check‑in‑dance”), addresses common team questions, and offers practical tips such as token control and visual CI status monitoring.
The article discusses how a software team selects an appropriate iteration cycle, establishes clear work agreements for each sprint, adopts single‑piece development with immediate testing, and introduces continuous integration to improve quality and efficiency in an agile environment.
This article presents a series of agile process‑improvement case studies—including flexible response to change, effective communication, goal‑aligned teams, and robust engineering culture—offering practical guidance for software teams seeking to adopt and sustain agile transformations.
This article presents a curated list of essential Java books ranging from beginner fundamentals and agile testing to advanced architecture, software development processes, and project management, offering download links and concise commentary to help Java developers systematically improve their skills.
The weekly roundup covers AlphaGo’s retirement and release of self‑play games, Tencent’s surge as Asia’s top startup investor, Microsoft’s migration of Windows code to Git, WeChat mini‑program enhancements, Alibaba’s retail partnership, AI insights from Siri’s co‑founder and Facebook’s new NMT model, Xamarin Live Player’s impact, and Git 2.13 security improvements.
The Meitu‑Meituan‑Dianping technical salon brings senior engineers together to share hands‑on insights into recommendation‑algorithm optimization, JUnit‑based distributed automated testing, and the evolution of client architecture from ad‑hoc to modular development, offering senior R&D professionals cutting‑edge knowledge through case studies and expert presentations.
The article examines recent trends showing Python’s rapid rise against Java’s declining popularity, compares their core differences in typing, syntax, performance, and ecosystem, and discusses why programmers should understand these shifts across web, cloud, mobile, and data science domains.
The article argues that software development is a continuous design activity rather than a repeatable manufacturing process, using car production and cooking analogies to illustrate why traditional waterfall management fails and why developers should be seen as designers, not assembly line workers.
The article examines the ongoing debate about Java's relevance versus Python's rising popularity, presenting recent job market statistics, usage trends, and a detailed comparison of the two languages' characteristics, performance, cross‑platform capabilities, and roles in modern IT domains.
In this reflective guide, former Mozilla engineer James Long shares personal insights and actionable advice—ranging from finding mentors without idolizing them to tackling big projects and exploring new languages—to help programmers continuously improve their skills and mindset.
This article lists ten practical abilities—ranging from version control and writing to debugging and teamwork—that every fresh programmer should acquire to thrive in real‑world software development without formal guidance.
After a decade in software development, the author reflects on common career pitfalls—frequent platform switching, chasing management roles, neglecting breaks, stopping coding, avoiding community, and over‑relying on job boards—offering practical advice to build a sustainable, rewarding developer path.
The article explores why many programmers prefer working late at night, examining factors such as sudden urgent tasks, daytime distractions, the creator's unique schedule, fatigue‑induced focus, and the impact of bright screens on sleep cycles, ultimately highlighting the quiet, uninterrupted environment that night provides for deep coding work.
This article introduces seven high-quality open‑source bug tracking tools—Bugzilla, Redmine, Trac, Mantis, Fossil, Phabricator, and WebIssues—detailing their origins, main features, and why they can boost project development and issue management for software teams.
The article explains why rapid response is essential in modern software projects, critiques the drawbacks of waterfall development, and introduces agile practices such as short iterations, user stories, continuous integration, automated testing, and close collaboration to deliver value more efficiently.
This article offers a comprehensive, hands‑on learning roadmap for new programmers, covering scripting languages, editors, Unix/Linux shell, web fundamentals, Java, databases, system programming, and architecture, while emphasizing practical projects, critical thinking, and long‑term skill development.
After a decade of switching platforms, the author reflects on career‑building mistakes, shares why focusing on a single technology stack, continuous learning, and community involvement matter, and offers practical advice for developers seeking sustainable growth and better job prospects.
