This article explains what Go channels are, how they are implemented in the runtime, their data structures, creation, sending, receiving, closing semantics, common pitfalls, and includes detailed code examples to illustrate channel behavior in concurrent programs.
This article outlines three essential principles for responsibly deflecting responsibility in software teams, highlights three scenarios where blame shifting is inappropriate, and provides role‑specific tactics for developers, testers, product managers, and ops to navigate workplace conflicts effectively.
This guide outlines common tester‑developer interaction scenarios, highlights typical mistakes, and provides step‑by‑step best‑practice responses to improve bug reporting, collaboration, and overall software quality assurance processes.
Effective listening is presented as the most essential leadership skill, a foundation for other abilities, whose scarcity in the digital age creates communication gaps that can cost organizations millions, and practical tips are offered to reduce the "communication funnel" and improve decision‑making.
This article explains structured thinking—combining logical sequencing and proven frameworks like 5W2H—to help professionals clarify problems, organize ideas, and communicate solutions effectively, offering practical steps for new teams, building geek culture, and delivering impactful presentations.
Becoming a software architect requires more than high‑concurrency knowledge; it demands comprehensive abilities such as requirement analysis, system decomposition, technology selection, design, communication, and leadership across all development phases, balancing business understanding with technical expertise to deliver effective architectural solutions.
This guide shares practical strategies for formulating clear, answerable technical questions—explaining your current understanding, asking fact‑based queries, identifying unknown terms, doing research, choosing the right person, and even using questions to uncover hidden assumptions and contribute to the community.
This article explores the core responsibilities of a technical team lead, covering team building, management styles, culture cultivation, communication, hiring, and dismissal strategies, and offers practical advice and real‑world examples to help leaders create high‑performing engineering teams.
The article examines why testers and developers often clash, illustrates the conflict with the classic Prisoner's Dilemma, lists common friction points such as unclear processes, standards, resources, and attitudes, and offers practical recommendations to establish shared workflows, improve communication, and foster a cooperative team environment.
The article examines the common friction between testers and developers, likening it to the Prisoner's Dilemma, identifies typical sources of conflict such as unclear processes, standards, resource contention, and attitudes, and offers five practical strategies to improve communication, workflow, and teamwork for better software quality.
This article explains why strong communication is essential for developers and offers four actionable techniques—reflective listening, thorough preparation, audience awareness, and navigating virtual tools—to help programmers become more effective collaborators.
In the VUCA era, project managers operating in matrix environments must adopt clear responsibilities, emotional intelligence, and strategic questioning to turn awkward interactions with technical experts into productive collaboration, using influence, empathy, and professional insight across all project phases.
This article provides a comprehensive overview of optical fiber technology, covering fiber composition, transmission parameters, attenuation causes, dispersion, OTDR principles, cable structures, connectors, and the impact of non‑linear effects on fiber‑optic communication systems.
The article shares practical methods for reducing bugs throughout the software development lifecycle, emphasizing early communication with product managers and testers, thorough design and code reviews, mandatory unit testing, continuous integration, and proactive log monitoring to ensure smooth testing and delivery.
A software architect must combine strong technical expertise, deep business understanding, forward‑looking design, broad knowledge, effective communication, and systematic thinking to translate business needs into reliable, scalable systems that drive a company's success.
A seasoned CTO shares concrete advice for junior developers, covering tool selection, goal setting, continuous learning, communication skills, networking, and choosing the right company, all aimed at maximizing growth and long‑term career value during the critical early years.
This article shares practical insights on project management, covering how to understand project goals, assess resources, communicate with stakeholders, handle risks and changes, create effective plans, and ensure successful delivery through disciplined documentation and verification.
This article explains what a software architect does, outlines their main responsibilities such as requirement analysis, system decomposition, technology selection, and specification writing, and highlights the essential design, technical, and communication skills needed to progress from junior developer to architect.
This article adapts Stephen Covey’s “Begin with the end in mind” habit to the workplace, explaining how to distinguish effectiveness (what to do) from efficiency (how to do it), design meaningful KPIs, and communicate results‑oriented actions to boost productivity and team performance.
This article shares a former Google engineer’s journey to CTO at a game studio, highlighting the challenges of leaving the programming comfort zone, mastering communication, choosing the right technologies, abandoning side projects, and navigating complex team‑management decisions.
A vivid story of a product manager and an app developer at China Ping An who physically fought over a request to change the app's theme color based on phone case color, followed by practical advice on handling unreasonable product demands and improving cross‑team communication.
This article explores the core competencies that distinguish a truly professional project manager, emphasizing the importance of goal‑oriented thinking, effective communication, risk identification, and strong negotiation skills while highlighting common pitfalls and the need for clear appointment and exit criteria.
Drawing on eight years of experience at companies like NVIDIA, Google, Slide, and Glow, this article offers concrete, system‑level advice for junior developers on building a personal toolbox, setting strategic goals, mastering communication, networking, and choosing the right company to accelerate long‑term growth.
The article examines the technical, economic, and security challenges of deploying instant‑messaging services as decentralized applications on public blockchains, argues that a dedicated communication‑focused blockchain is more suitable, categorizes existing blockchain IM projects, and outlines why platform‑level communication requires a specialized chain.
This guide outlines common tester‑developer interaction scenarios, highlights typical mistakes, and provides best‑practice responses to improve bug reporting, collaboration, code reviews, and issue resolution, helping QA professionals foster constructive communication and maintain project quality.
This article shares practical interview techniques—listening carefully, answering from a high‑level overview to details, staying humble, crafting honest resumes, balancing breadth and depth, showing initiative, and providing concrete proof—to help candidates communicate their skills effectively and succeed in technical job interviews.
This article reviews Android mobile architecture patterns—including MVC, MVP, MVVM, Flutter-derived framework, and Android Architecture Components—explaining their evolution, layer separation, and communication mechanisms such as object holding, interface contracts, and router-based dispatch, while providing illustrative code examples.
The article shares practical reflections on project management in e‑commerce development, emphasizing the importance of clear requirements, effective communication, realistic scheduling, resource allocation, and proactive risk management to help practitioners improve their project outcomes.
This article explores the seven core competencies—technical expertise, abstraction, design foresight, systematic thinking, problem‑solving depth, cross‑domain knowledge, and communication—that distinguish a successful software architect and guide how to develop them.
The article shares practical guidance for JD.com’s R&D middle‑platform project managers, emphasizing internal and external cultivation, responsibility, humility, passion, empathy, professional project‑management skills, and effective communication to influence cross‑functional teams and drive successful delivery of business requirements.
The article outlines five actionable strategies—ensuring tests exist, communicating with the original author, eliminating warnings, refactoring, and making the code better than when found—to responsibly modify and enhance legacy code while minimizing risk and technical debt.
The article explains why soft skills such as skeptical thinking, curiosity, analytical ability, and communication are crucial for software testers, complementing hard technical knowledge and enhancing defect detection, collaboration, and overall testing effectiveness.
This article offers product managers practical negotiation techniques—including securing a home base, identifying true stakeholders, using vision as a tool, maintaining consistency, proving rationale, committing to agile practices, asking open‑ended questions, focusing, listening, and standing firm on decisions—to effectively influence and align stakeholder expectations.
The article explores common conflicts between development, testing, and operations staff, explains why operations are often undervalued, and offers practical steps—such as clear documentation, defined processes, and proactive communication—to improve teamwork and reduce blame‑shifting in software projects.
This guide categorizes common programming questions, explains why some have standard answers, and offers practical techniques—like providing context, searching first, and structuring inquiries—to help developers ask clearer, more effective questions and get useful responses.
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.
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 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 explains how traditional user research methods struggle to keep pace with fast‑moving internet product cycles and proposes an agile, business‑oriented research framework that shortens study time, improves cross‑functional communication, and ensures research outcomes are actionable and aligned with product goals.
This article breaks down the realistic role of product managers, highlighting core competencies such as communication, independent thinking, and project management, and offers practical guidance on handling diverse requirements and ensuring product plans smoothly transition into development.
The article recounts Joel Spolsky’s Yale talk, highlighting his key takeaways about focusing on real problems, avoiding in‑house programmer roles, the importance of aligning business with technical expertise, and how strong communication separates ordinary staff from leaders.
The article shares a real‑world workplace story about a disruptive employee, then outlines seven practical principles—respecting superiors, keeping them informed, giving proper feedback, avoiding incitement, not creating trouble, responding to ad‑hoc tasks promptly, and helping leaders succeed—to guide professionals in building effective, harmonious teams.
This guide outlines why sharing matters, how to overcome fear, focus your topic, control timing, engage audiences without reading slides, and continuously improve your presentation skills through structured preparation, logical storytelling, and audience‑responsive techniques.
This article explains what infographics are, why they are essential for simplifying complex information, outlines the six main types of visual representations, and presents five key principles—eye‑catching design, accurate messaging, simplicity, eye‑movement guidance, and minimal text—to create effective infographic designs.
This article explains the differences between MQTT and CoAP, two lightweight IoT communication protocols, and provides guidance on when to use each based on network conditions, architecture compatibility, and deployment scenarios.
This article presents a curated list of frequently mispronounced English words among Chinese programmers, showing the proper IPA pronunciation alongside common incorrect variants, helping developers communicate more clearly with international colleagues and avoid embarrassing misunderstandings.
The article outlines five crucial steps for visual designers to collaborate effectively with front‑end engineers, covering environment familiarity, design system creation, proper asset slicing, clear annotation, and pixel‑perfect testing to ensure seamless implementation and reduce miscommunication.
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.
A corporate dragon‑boat race on the Duanwu Festival turned into a vivid lesson on project management, highlighting how unclear roles, poor communication, lack of team harmony, and member inactivity can derail a project and offering practical tips to strengthen leadership and teamwork.
The article explains how to successfully launch and drive large‑scale architecture refactoring by translating technical jargon into plain language, using data‑driven arguments, empathizing with stakeholders, and employing structured escalation and win‑win negotiation tactics to align cross‑functional teams.
The article shares a senior engineer’s reflections on systematic learning, the role of architects in coding, the pitfalls of endless meetings, how to keep systems alive, and practical questioning techniques that boost problem‑solving efficiency for software professionals.
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.
This article traces the evolution of web technologies from CGI to MVC and service‑oriented architectures, examines how communication challenges drive the shift from waterfall to agile development, compares expert versus full‑stack learning models, and envisions a "no‑stack" future for versatile engineers.
The article shares a senior engineer’s reflections on how systematic, knowledge‑network‑based learning, practical code involvement, effective communication, and disciplined architectural habits can dramatically improve a developer’s efficiency, problem‑solving ability, and overall career growth.
This article examines why many operations engineers feel unhappy, identifies four personal‑management problems—over‑pursuing tech, mis‑prioritizing tasks, poor communication, and chronic complaining—and offers concrete, actionable suggestions to improve productivity, satisfaction, and team collaboration.
This article explores why efficient operations are hard to achieve, identifies common pitfalls such as unclear responsibilities, communication gaps, and resource mismatches, and presents a practical framework—including clear roles, professional processes, and a good service interface—to help operations teams become more effective and satisfied.
This guide explains why product managers often face friction when issuing requirements, outlines three key points for effective requests—including understanding human factors, choosing the right communication channels, and applying the SMART principle—and offers practical comparisons of common mistakes versus best practices for technical, design, and cross‑functional collaboration.
This article outlines the vital communication techniques for software architects, emphasizing when to say “yes,” how to handle “no” situations, active listening, understanding stakeholder needs, and quick thinking to make effective decisions and foster collaboration.
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.
This article shares actionable advice from a former product manager and engineer on how product managers and developers can prevent conflicts, improve communication, and collaborate effectively through better requirement handling, realistic planning, and clear, data‑driven explanations.
The author compares Chinese and US software engineers, highlighting stark differences in communication style, problem‑solving ability, technical depth, passion for coding, and broader expectations such as leadership and vision, while noting that only a small elite in each country truly excel.
This article outlines the critical non‑coding abilities—communication, problem‑solving, version control, and continuous learning—that aspiring developers need to succeed in modern software teams and advance their careers.
The article uses three vivid workplace anecdotes to illustrate why clear goals, feasible methods, solid communication, rational processes, proper incentives, and effective assessment are essential for turning strategy into successful execution.
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.
This article explains how to formulate technical questions so that experienced hackers and community members are more likely to provide helpful answers, emphasizing prior research, clear presentation, humility, and demonstrating effort to avoid being perceived as a 'loser' who merely demands solutions.
Technical writing forces programmers to clarify and deepen their understanding, boosts communication skills, invites valuable feedback, expands professional networks, and ultimately builds influence, making it a powerful learning strategy beyond ordinary study methods.
The article shares practical support and communication principles, data handling guidelines, and internal best‑practice examples from Qunar to help newcomers avoid common pitfalls and improve operational efficiency by emphasizing sincere assistance, careful treatment of sensitive information, post‑mortem reviews, and appropriate use of tools such as mailing lists, QTALK, and encoding conversion.
The article outlines six critical qualities—hands‑on programming, abstract thinking, technical foresight, problem‑driven analysis, cross‑domain knowledge, and strong communication—that distinguish an effective software architect and guide them through every phase of a project.
The article introduces a Coursera course on workplace professionalism, outlines its syllabus covering communication, self‑leadership and professional image, shares learner discussions questioning whether the content is merely self‑help, and provides course details such as instructor, duration, and enrollment link.
This article explains how front‑end engineers can overcome common design‑communication hurdles by establishing clear style guidelines, standardizing reusable components, and aligning visual expectations, ultimately creating a unified product look and smoother teamwork between designers and developers.
This article outlines the product manager’s role as a communication hub across leaders, design, engineering, and operations, detailing each project phase, common challenges, and practical techniques—such as focusing on product goals and respecting professional expertise—to enhance collaboration and reduce rework.
This article outlines the key traits, abilities, and mindsets—such as empathy, problem‑solving, design simplification, and continuous learning—that are essential for becoming an effective user experience practitioner and advancing in the field.
This article explains why integrating storytelling into UX design improves user empathy, fuels creativity, guides research, and helps teams communicate ideas effectively, illustrated with real‑world examples from educational platforms and product scenarios.
