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.
Metrics‑Driven Development (MDD) extends test‑driven principles by embedding real‑time monitoring into design, enabling rapid, precise, and granular software iterations, improving early problem detection, decision support, and aligning development with DevOps culture.
In this interview, Linus Torvalds shares hard‑earned lessons on software project management, emphasizing personal responsibility, the primacy of users over code quality, the limited role of tools, and how the Linux kernel mailing list keeps contributors aligned, offering timeless advice for developers and teams.
This case study describes how Qunar's R&D support team built an integrated project management platform that unified workflow, data, and toolchains across development, testing, and release stages, dramatically lowering communication overhead, eliminating information inconsistencies, and improving overall engineering productivity.
This article introduces Git as a distributed version‑control system and GitHub as a hosting platform, explains why they are useful, and walks through core commands such as init, add, commit, branch, tag, and push to help developers manage code efficiently and collaborate effectively.
The article explores how code submission and version‑control practices evolve from simple solo workflows to complex, team‑wide processes, highlighting the need for tools, branching, automation, and continuous integration to manage growing codebases and maintain software quality.
This article explains how applying Lean Engineering principles—such as small batches, rapid failure, continuous improvement, and continuous delivery—can reduce risk, accelerate software delivery, and improve quality in enterprise IT environments, while also integrating cloud‑based automation and feedback loops.
The article explains why flat user‑story backlogs are ineffective, illustrates the problems with prioritizing and planning using such lists, and shows how constructing a user‑story map provides context, improves backlog management, and enables better release planning for product development.
This article shares a senior technical director’s hard‑won lessons on balancing hands‑on development, non‑functional requirements, architecture design, training, and management to boost team productivity and product quality in software projects.
The article examines the paradox of having many developers but little output, identifying causes such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architectures, and offers practical suggestions to improve efficiency in software projects.
This article explains the core concepts of distributed version control, compares it with centralized systems, describes repository structures, outlines the advantages of Git, and provides step‑by‑step command examples for initializing, committing, branching, merging, cloning, pulling, and pushing changes in a collaborative development workflow.
The article warns programmers that three common misconceptions—isolating themselves to code, ignoring responsibilities beyond coding, and chasing money before growth—hinder career development, urging them to embrace communication, treat their skills as a business, and focus on continuous personal and professional improvement.
The article presents the latest TIOBE programming language rankings, highlighting Haskell's position at 23, notable moves for MQL4, Hack, and Elixir, and provides visual trend charts for the top 10 languages along with a disclaimer about the data's scope and limitations.
The article reflects on how developers often become zealots for particular languages or tools, compares this to religious wars, and argues that abandoning blind loyalty in favor of an open, pragmatic approach leads to broader skill sets, better career decisions, and more innovative solutions.
This article explores how software development has transformed over the past decade, highlighting the shift from monolithic architectures to service‑oriented, containerized, and microservice models, and explains why improving developer efficiency and experience is the core driver of this evolution.
This article examines how increasing software productivity drives the evolution of development models—from traditional waterfall through agile to microservices—and how full‑feature teams adapt production relations to maximize efficiency and creativity.
This article offers practical strategies for junior programmers to improve their coding skills, build a professional portfolio, communicate effectively, and maintain a healthy mindset, helping them stand out in a competitive software development landscape.
This article outlines the essential qualities of a good Pull Request—including meaningful improvements, readability, and maintainability—while also highlighting advanced practices such as priority setting, code review, and automated testing to make PRs more disciplined and artistic.
The article explains how to use the User Story Mapping technique on the TFS platform, describing both a direct one‑to‑one mapping approach and a conversion method that transforms business‑level story maps into technical TFS work items for efficient DevOps team collaboration.
Under CEO Satya Nadella, Microsoft has dramatically embraced open source, climbing to the top of GitHub’s contribution leaderboard with 16,419 contributions—surpassing Facebook, Docker, Angular, and Google—while opening key technologies such as .NET, Chakra, MSBuild, Xamarin, and PowerShell to the community.
An insider critique reveals how Huawei's complex hierarchy, rigid processes, outdated tools, and management culture hinder software development efficiency and quality, urging a shift toward flatter, more agile R&D practices.
Linus Torvalds discusses the origins of Linux, the role of open‑source collaboration, the evolution of Git, his personal work habits, and the broader impact of open‑source software on technology, business, and future innovation in a candid TED‑style interview.
This article clarifies common misunderstandings about agile development, explains why it can be faster than traditional methods by reducing pre‑development waste, early releases, and continuous testing, and offers practical illustrations through games, diagrams, and user‑story techniques.
The article examines how concise, efficient, and simple development practices—ranging from agile iteration and tool selection to testing automation and team management—can boost developer productivity, reduce waste, and enhance software quality across the entire software development lifecycle.
This article explains the principles of version control systems, illustrating the evolution from manual file‑locking methods to modern distributed workflows with checkout, check‑in, merging, branching, and collaborative features exemplified by the custom Hit and HitHub platforms.
This article explores how engineers can leverage their unique technical language, focus on mastering a single technology, navigate management or expert career tracks, and overcome societal stereotypes to build fulfilling, impactful careers in today's rapidly evolving tech landscape.
This article chronicles Zhang Xiaolong’s journey from a modest engineering student and free‑email developer to the mastermind behind WeChat, highlighting his technical experiments, product pivots, and leadership decisions that reshaped China’s social‑media landscape.
This article traces the evolution of programming languages from the early 1950s regional assembly language to modern languages like Go and Dart, highlighting key milestones, influential predecessors, and the continual innovation that has produced over 250 distinct languages.
A senior architect compares two real projects—one a traditional co‑located auction site and the other an open‑source distributed Java product—showing that the distributed team produced code at roughly $0.13 per line versus $3.98 per line, a thirty‑fold cost reduction.
Drawing on interviews with over 500 engineers from top tech firms, this article outlines ten actionable practices—such as speeding iteration, embracing automation, fostering code ownership, and allocating 20% time—that together create a respectful, high‑performance engineering culture.
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.
The article introduces User Story Driving Agile Development (UDAD), a comprehensive methodology that integrates impact mapping, user story mapping, visual guidance, Scrum, Kanban, continuous integration, exploratory testing, and automated deployment to provide a cohesive, end‑to‑end agile process supported by Microsoft Team Foundation Server.
The article explains how software architects combine technical architecture responsibilities with people‑focused management duties, emphasizing the importance of nurturing talent, sharing a clear product vision, encouraging collaboration, and balancing technical excellence with team motivation to achieve successful, high‑impact projects.
This article shares a seasoned programmer’s practical roadmap for mastering a new programming language, covering motivation, goal setting, language selection, book recommendations, code reading, hands‑on practice, and building real modules to accelerate skill development.
