A casual chat with an overseas AI student reveals that while China excels in large‑scale models and engineering speed, it still trails the West in AI‑focused terminology, standards, and protocol innovation, prompting a reflection on cultural habits, competitive pressure, and the need for original contributions.
The article analyzes Palantir’s shift from a profit‑centric, standardized software model to a responsibility‑driven, ontology‑based architecture that embeds engineers on‑site, leverages LLM orchestration, and prioritizes specificity and security, offering a new paradigm for enterprise software value creation.
The article argues that cultivating a strong engineering culture—through shared values, clear processes, automation, altruistic collaboration, and continuous self‑improvement—empowers programmers to remain reliable and productive despite uncertainty, boosting the odds of sustained success while acknowledging that culture is only one of several critical factors.
The article examines BYD's engineering culture, highlighting how its leaders emphasize innovation, competition, and efficiency, and how this mindset drives technological breakthroughs, rigorous R&D processes, and a distinctive management style that empowers engineers to shape the company's long‑term success.
The article examines how two decades of lavish perks and guaranteed jobs have left software engineers over‑valued, how AI‑driven layoffs and shifting business priorities are forcing CTOs to abandon the old talent‑retention mindset, adopt a genuine engineering culture, and reclaim narrative control to ensure organizational resilience.
This article explores the qualities that distinguish a senior or mature software engineer, drawing on the author’s experience and insights from Etsy’s CTO to outline attitudes, habits, and mindsets that enable engineers to have lasting impact across teams and projects.
The article examines why software architectures become tangled—citing resource constraints, poor organization, unmanaged technical debt, outdated tech, and missing documentation—and offers practical strategies such as background analysis, continuous refactoring, training, communication, design‑pattern adoption, engineering culture, and comprehensive testing to restore health.
The article examines Amazon's Correction of Errors (COE) process, presenting both supportive and critical SDE perspectives, and discusses whether detailed post‑incident documentation truly improves engineering practices or merely adds bureaucratic overhead.
Greg Foster investigates why Facebook abandoned Git for Mercurial, revealing that massive repository size caused severe performance bottlenecks, Git’s inability to scale, and the collaborative culture of Mercurial’s maintainers, ultimately shaping Facebook’s tooling decisions and influencing broader industry practices.
The article reflects on a bug‑fixing team's experience, arguing that bugs are an inevitable by‑product of software development, discussing the limits of zero‑tolerance policies, the trade‑offs between quality and resources, and suggesting cultural and engineering practices such as testing left‑shift, code reviews, and refactoring to improve quality without sacrificing delivery speed.
The article chronicles Google’s Test Certified initiative from its early challenges in 2005 through the establishment of a multi‑level certification system in 2006, detailing its structure, certification process, scaling efforts, cultural impact, and the lessons learned for improving automated testing practices.
This article argues that systematic documentation dramatically improves productivity, reduces unnecessary meetings, and builds a sustainable knowledge culture in startups, offering practical advice on tools, templates, and team habits to make documentation a core engineering practice.
Feng Di, Xiaohongshu’s community technology leader, explained that an outstanding engineering team thrives on passion, freedom, and efficiency, must manage endless product demand, scale without excessive process, cultivate T‑shaped skills, balance algorithm work with solid system engineering, adopt data‑driven ownership, automated testing, and meaningful overtime to continuously solve real problems together.
After a decade at Google as a Staff Software Engineer and Manager, the author reflects on three career phases and shares four key lessons about embracing differentiation, shifting from a tech‑user to a tech‑owner mindset, the true meaning of management, and adopting a healthy career‑life attitude.
The article critiques traditional software architects as bottlenecks, shares personal experiences at eBay and Alibaba, argues that dedicated architecture departments often cause more harm than good, and advocates that every engineer develop architectural thinking, offering guidance for engineers, team leads, and CTOs.
The author reflects on a decade‑plus at Google, describing three career phases, the impact of diversity, a shift from being a technology user to a technology owner, and practical lessons on managing elite engineers in a fast‑moving, innovative environment.
After ten and a half years at Google as a Staff Software Engineer and Manager, the author reflects on three career phases, the power of diversity, the shift from a technology user to a technology owner, and the unique management culture that shaped his professional outlook.
This article shares ten practical principles—ranging from ownership and time management to continuous learning and balanced output—that help engineers avoid common pitfalls, improve team efficiency, and foster personal and professional growth.
The article outlines ten actionable strategies—optimizing iteration speed, relentless automation, building proper abstractions, rigorous code reviews, fostering respectful environments, shared code ownership, investing in automated testing, allocating 20% time, cultivating continuous learning, and hiring top talent—to create a thriving engineering culture.
This article explains why a strong engineering culture is essential for software delivery, quality, and employee satisfaction, and outlines three practical steps—defining core values, implementing supporting mechanisms, and living the values—to create and sustain such a culture within a company.
The article outlines Google’s best‑practice guidelines for code coverage, emphasizing its workflow benefits, the cultural impact of increasing coverage, the limits of high percentages, the importance of uncovering uncovered code, and practical steps for progressively improving coverage across projects.
The talk explains why measurement is essential for engineering effectiveness, describes the shift from a handcrafted "farming" R&D model to an industrialized, data‑driven process, outlines when and how to measure, and emphasizes the importance of aligning metrics with true business outcomes.
The author reflects on a decade at Google, sharing how exposure to a diverse, innovative environment reshaped his views on differentiation, transformed his technical mindset from user to owner, and revealed unconventional management practices that emphasize empowerment, tool‑driven processes, and the pursuit of joyful, purpose‑driven work.
Drawing from four years of experience as a technical team leader at Alibaba, the article shares practical insights on recruitment, goal definition, effective communication, fostering a strong engineering culture, and personal reflections, offering guidance for managers seeking to build high‑performing, innovative development teams.
Drawing on four years of experience as a technical team leader, this article shares practical advice on hiring, defining clear objectives, fostering effective communication, and cultivating a strong engineering culture to sustain long‑term team performance and innovation.
The article reflects on Youzan’s testing team evolution, from its late start in 2014 to hiring code‑savvy testers, role consolidation, long‑term value thinking, and how these practices shaped a high‑quality engineering culture, while also announcing their newly published ebook.
This case study examines Facebook's origins, mission, core leadership, explosive growth, business model, and especially its distinctive engineering culture—known as The Hacker Way—highlighting practices such as bootcamps, hackathons, hackamonths, information transparency, and empowerment that drive innovation and align employee performance with company goals.
This article presents a comprehensive case study of Etsy’s evolution in quality assurance, engineering culture, continuous integration, continuous delivery, and cloud migration, detailing the team structure, testing strategies, four core engineering principles, tool development, and the benefits of rapid, automated deployment pipelines.
This article examines Etsy's engineering culture and operational practices, covering diversity and inclusion, the "Code as Craft" philosophy, blameless postmortems, the engineering rotation program, and the measurement of code coverage as a quality‑driving metric, illustrating how these initiatives foster continuous improvement and resilience.
The article argues that simple, term‑free design processes—focused on business problems, whiteboard brainstorming, concise documentation, and iterative feedback—outperform formal architecture tools, patterns, and dedicated architects in large‑scale systems like Uber, emphasizing engineering culture over rigid methodologies.
The article explains how leading tech companies like Uber and Skype design massive systems using simple, informal diagrams and collaborative documentation instead of formal architecture tools or dedicated architects, emphasizing simplicity, team autonomy, and practical trade‑offs over rigid patterns.
The article chronicles three generations of Hangzhou‑origin engineers—from gritty early Alibaba pioneers to modern cloud and blockchain specialists—showing how their relentless problem‑solving, cultural resilience, and tech‑first mindset transformed China’s internet ecosystem and positioned the city as a global engineering hub.
The article explains Google’s “Code Health” initiative, describing its purpose, organizational structure, and how it promotes better readability, maintainability, stability, and simplicity in software development through best‑practice documentation, tooling, and cultural advocacy.
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.
This article explores the true mission of a CTO, how to evaluate their performance, the optimal split between internal and external duties, and the five core responsibilities that drive technology strategy, engineering culture, sales, business development, and marketing within an organization.
In an interview at Huawei's 2015 Developer Conference, GitHub CIO Scott Chacon explains how open‑source culture, simple APIs, and global collaboration drive GitHub’s growth, security resilience, and its partnership with Huawei to reach Chinese developers.
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 article examines Google’s unique engineering‑focused culture, flexible work policies, flat organization, rigorous hiring, and performance management system, showing how these practices attract top talent, encourage innovation, and sustain the company’s rapid growth and low turnover.
The talk explains Facebook's early engineering culture—emphasizing rapid "Hack" iterations, a decentralized organization that avoids dependencies, open code‑base ownership, data‑driven debate, and the strategic hiring of strong engineers—to illustrate how these practices drive high‑speed product development.
