This article shares practical insights on interviewing software engineers, exposing hiring biases, recommending interview structures, small‑talk techniques, broad and specific technical questions, project‑based assessments, and how to create a fair, inclusive process that reveals true talent.
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.
In this talk, a former Google global R&D director shares how demand‑driven reform, strong infrastructure foundations, and hiring the best talent shaped Google’s architecture evolution, offering practical insights for startups on balancing design, evolution, and business versus technology drivers.
The article explains Google’s rigorous talent‑acquisition strategy—hiring only candidates who outperform you, using a slow, data‑driven process, talent decision committees, structured interviews, and continuous feedback—to illustrate how startups can build a high‑quality team.
The article shares practical lessons from a year of backend R&D experiments at Weibo, describing how a bottom‑up hybrid‑cloud solution, cross‑team collaboration, and systematic team‑building transformed the Feed service’s scalability, cost efficiency, and alignment with business goals.
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.
The article chronicles Zhang Yiming’s journey from early failures to founding ByteDance, detailing the company’s rapid growth, product‑centric culture, funding milestones, recommendation engine technology, and the strategic decisions that turned a small engineering team into a multi‑billion‑dollar media powerhouse.
The article argues that a CEO’s strategic thinking—forecasting trends, identifying breakthrough points, and committing all resources—outweighs sheer execution, illustrating the concept with examples from Chinese tech firms and offering a three‑step framework for sustainable growth.
The article explains Alibaba's continuous delivery theory, tools, and best‑practice pipeline—including integration, testing, deployment, and release—illustrated with diagrams and a detailed description of how the platform improves software quality, collaboration, and operational resilience in large‑scale cloud environments.
An experienced Facebook engineer explains that promotions rely on sustained technical excellence, measurable impact, peer feedback, and a transparent calibration process rather than office politics, outlining the review steps, criteria, and the importance of helping others.
This article summarizes the core concepts of "The Geek and the Team", highlighting humility, respect, and trust as pillars for effective software team collaboration, and provides practical guidance on culture, leadership, handling disruptive members, organizational influence, and user relationships.
In this article, the COO of Shimo shares real‑world observations and interviews with senior engineers to reveal that high salaries and free meals satisfy only basic needs, while meaningful work, growth opportunities, and a strong company culture are the true drivers that motivate top technical talent in startups.
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 reflects on the evolving role of a software architect through personal experiences at Tieto, Sony, and a bank, highlighting responsibilities, team organization, project leadership, and the broader mindset that makes anyone a de‑facto architect in both technology and life.
The article chronicles Wang Tao’s journey from a modest Hangzhou upbringing and early fascination with flight to founding DJI, detailing his education, early prototypes, strategic product decisions, funding challenges, and how the Phantom drone propelled the company to dominate the global UAV market.
This article outlines ten practical management principles—including clear structure, defined goals, appropriate delegation, visual tracking, and continuous improvement—to help leaders build high‑performing, accountable teams and avoid common pitfalls.
The article recounts a themed team‑building competition where various “sect” groups presented management insights on talent development, employee motivation, KPI‑driven evaluation, and execution, culminating in a vote that crowned the winning strategies and highlighted the value of practical, collaborative learning for R&D teams.
Google’s research on meeting efficiency reveals nine practical rules—assign a decision‑maker, prepare thoroughly, define a clear owner, keep meetings easy to cancel, limit size, attend only when needed, be punctual, stay focused, and shut down devices—to transform wasted time into productive outcomes.
The article examines why software engineers are often seen as hard to communicate with, shares Nicholas C. Zakas' experiences and analogies, and offers practical advice such as involving engineers early, minimizing interruptions, granting creative space, and providing timely appreciation to foster better collaboration.
The article examines why technically brilliant founders often fail to grow their companies, highlighting mindset shifts, market‑oriented product thinking, team‑building, capability bridging, and the creation of open industry ecosystems as keys to turning technical talent into successful CEOs.
The article shares Kevin Scott’s insights on building high‑performing engineering teams during rapid company growth, emphasizing the difference between technology and company building, the importance of asking "how" before "what", and how a cultural manifesto can guide and sustain a thriving R&D culture.
This article debates whether compact, full‑stack engineering teams are inherently unstable compared to larger, low‑tech “valley” teams, arguing that stability depends on a team's ability to nurture talent and continuously attract experts rather than relying on crude, static practices.
The article outlines Douban's R&D management philosophy, describing three core constraints—product contribution, proper methods, and technical goals—how they translate into rules, the democratic rule‑making process, cross‑team collaboration incentives, and a balanced performance and reward system.
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.
From 2011 to 2014 Ctrip shifted from a 25% online, 75% offline model to a mobile‑centric approach, reorganizing its 16 business units, decoupling systems, and adopting new engineering practices to improve performance, scalability, and team autonomy.
Huawei’s shift from a pure telecom operator to a full‑stack IT company reveals the challenges of ecosystem complexity, open‑source adoption, talent restructuring, and strategic focus, offering valuable insights for R&D managers navigating large‑scale digital transformation.
The article shares a founder’s hard‑earned lessons on preventing code‑base entropy, hiring the right first engineer, and gradually improving code quality so that a growing startup can transition from a solo coder to a well‑structured engineering team.
