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.
The article uses a vivid restaurant scenario to illustrate how repeated requirement changes cause developers to face rework, increased cost, schedule delays, and communication friction, explaining why programmers and designers dread constantly shifting product specifications.
The article explores three archetypes of engineers—Coder, Hacker, and Architect—examining their motivations, work habits, and impact on product development, while challenging common misconceptions about engineering roles and encouraging readers to choose the path that fits their passion and skills.
This article explains what defines an expert developer, estimates the time required to achieve expertise, and outlines a four‑step learning process—study, practice, discuss, and teach—while emphasizing focused platform mastery and continuous skill expansion.
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.
This article shares eleven practical rules for software developers, ranging from treating technology as a tool rather than a solution, writing clear code, avoiding unnecessary code, limiting comments, planning before coding, testing thoroughly, continuous learning, enjoying coding, acknowledging unknowns, adapting best practices, and striving for simplicity.
This article explains Baidu's continuous integration (CI) journey, detailing the CI capability model, its three core factors—test coverage, build system, and team habits—along with metrics, scoring, and how the CI team supports product lines to improve development efficiency.
Through a collection of humorous and often pointless code comment examples, the article examines how developers use annotations—ranging from cryptic references to overly detailed narratives—to convey (or obscure) intent, highlighting best practices and pitfalls in writing effective code comments.
The article lists fifteen common workplace obstacles—such as endless meetings, email overload, misguided productivity metrics, technical debt, non‑technical managers, poor documentation, distracting environments, and a relentless chase for the newest tools—that hinder developers from writing high‑quality code efficiently.
The article explores how deliberate practice, shared values, and a craft‑oriented mindset empower programmers to continuously improve their skills, adopt solid engineering practices, and evolve from apprentices to true software artisans.
The article argues that a successful development team always includes a less‑skilled member, and how treating that person with respect and support reflects the team’s culture, improves morale, and ultimately enhances overall project quality.
This article chronicles the author's seven‑year evolution from a disinterested student to a seasoned developer, detailing study plans, key algorithm and data‑structure books, internship experiences, custom parsers, performance‑critical mobile features, and the indispensable role of algorithms for serious programmers.
This article highlights five common programming mistakes—copying code without understanding, reinventing the wheel, over‑relying on Google, ignoring warnings, and applying quick fixes instead of permanent solutions—explaining why they harm code quality and offering practical advice to help developers write cleaner, more maintainable software.
A compilation of interviews with renowned programmers—Linus Torvalds, Dave Thomas, Guido van Rossum, and others—covers how they learned to code, essential programmer skills, the role of math and physics, upcoming hot topics, preferred tools, favorite books, and music, offering deep insight into the craft of software development.
Reflecting on five years of software development, the author shares hard‑earned lessons about unclear goals, inconsistent learning, the importance of solid fundamentals, good architecture, business awareness, and realistic career paths for developers seeking lasting growth.
The article argues that claims of mastering programming in a few days are misleading, presents research showing a decade is typically needed to achieve expertise, and offers practical advice on how to become a competent programmer through sustained practice, collaboration, and thoughtful language selection.
In a series of interviews, the creators of Node.js, Python, Ruby, Kotlin, Scala, C++, Dart, Julia, and Clojure discuss each language's core strengths, design goals, and the contexts in which developers should choose them, offering a panoramic view of modern programming language evolution.
The article examines how concise, efficient, and simple development practices, agile iteration, automated testing, and thoughtful tool selection can boost individual and team productivity while maintaining software quality, offering practical examples and strategic guidance for optimizing software development processes.
This article outlines ten key characteristics—ranging from holistic development and problem‑solving passion to strong communication and business curiosity—that distinguish great programmers and help them excel beyond technical expertise in real‑world software projects.
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 provides a comprehensive list of the most commonly used Git commands, organized by tasks such as repository creation, configuration, file handling, committing, branching, tagging, inspection, remote synchronization, and undoing changes, helping developers work efficiently with version control.
In this expert Q&A, Baidu’s senior big-data specialists reveal common project pitfalls, argue for Java in Hadoop-style systems, discuss MongoDB deployment, outline criteria for choosing open-source versus self-built solutions, and evaluate the viability of NewSQL/Spanner-type startups.
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.
This article shares practical advice from a former development director on how technical managers can excel by connecting with their teams, managing tasks effectively, mastering time and resources, respecting individuals, and representing their team’s interests to drive success.
This article shares seasoned product‑manager insights on preventing and resolving friction with developers by preparing for requirement changes, improving code reusability, allocating buffer time, understanding requirements, communicating with data, and providing clear, detailed specifications.
In this speech, Ma Huateng shares practical insights on product design, emphasizing extreme focus on core capabilities, building reputation through high‑end user experience, and adopting a sensitive, operation‑driven management style to continuously refine and differentiate products.
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 presents 22 fundamental Scrum questions covering roles, artifacts, events, benefits, limitations, and practical guidance, offering a comprehensive overview for anyone preparing to become an effective Scrum Master and deepen their understanding of agile project management.
The article shares a quirky yet effective debugging habit where developers explain code line‑by‑line to a small rubber duck, forcing coherent thinking that often leads to breakthroughs, and encourages readers to adopt a similar personal tool for clearer problem solving.
The article shares a comprehensive overview of Google’s engineering environment, covering Silicon Valley work culture, internal communication mechanisms, the company’s development toolchain, quality‑versus‑speed trade‑offs in workflows, hiring practices, and the broader engineer mindset, supplemented by a detailed Q&A session.
The October TIOBE Programming Language Index shows Java climbing past 20% market share, highlights rapid shifts for languages like OpenEdge ABL, VBScript and Go, and explains how the ranking—based on search engine data—can guide developers in skill assessment and language selection for new projects.
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.
This article offers practical advice for newly‑graduated programmers on gaining experience, building tools, contributing to open source, improving English, blogging, joining forums, studying reference manuals, analyzing problems deeply, and embracing fundamentals to overcome career stagnation.
The article traces the history of the legendary "Hello World" program—from Brian Kernighan's 1978 C book and its early B-language roots, through its cultural symbolism, to the hardware breakthroughs that helped it become a universal first program for generations of developers.
This reflective guide shares personal lessons on starting a programming journey, emphasizing honest self‑assessment, practical learning habits, common pitfalls, and actionable advice for beginners to turn curiosity into real coding skills.
Drawing on two decades of experience, this article shares practical advice on overcoming programming challenges, maintaining motivation, leveraging online resources, building a versatile toolset, and continuously learning to stay ahead in the ever‑evolving software development landscape.
This article outlines the most frequent programming errors beginners make—such as mindlessly copying code, reinventing the wheel, over‑relying on Google, ignoring warnings, and opting for quick fixes—explaining why they harm code quality and how to avoid them.
Copy‑pasting code from Stack Overflow may save time, but retyping each snippet forces deeper understanding, encourages critical evaluation of solutions, and leads to cleaner, more maintainable code, making you a better developer rather than a mere “Stack Overflow‑style” coder.
