Tech and case studies on organizational management, team management, and engineering efficiency
This article explains how Software Bill of Materials (SBOM) mirrors hardware BOMs, outlines their core differences, presents best practices, tools, and implementation strategies to improve supply‑chain transparency, compliance, and security for modern software development.
This article explains how Software Bill of Materials (SBOM) serves as a digital map for component dependency and change management, detailing its functions in visualizing dependencies, detecting version conflicts, ensuring license compliance, and providing supply‑chain risk alerts, ultimately improving development efficiency, security, and regulatory compliance.
Meta’s engineering teams built a data‑driven efficiency metric system centered on Diff Authoring Time (DAT), using OS telemetry, IDE integration, and threshold rules to quantify active coding, guide toolchain optimization, and align individual and collaborative workflows, ultimately fostering a culture where data guides development decisions.
Mary Meeker’s 340‑page AI trend report highlights five core predictions—including unprecedented AI adoption speed, AI becoming a public utility, the rise of Chinese models, AI’s integration into the physical world, and the emergence of AI‑native users—while warning investors of the high risk of AI projects.
This article explains various Selenium waiting techniques—including implicit wait, fixed (hard) wait, page load strategies, and JavaScript detection—detailing their principles, advantages, disadvantages, and providing Python code examples to help choose the most suitable approach for stable and efficient automated web testing.
The article explains why high‑quality, diverse data—rather than just advanced models—has become the decisive factor for enterprise AI success, outlining key dimensions of data quality, strategies for building diverse datasets, and practical steps for establishing a data‑first AI strategy.
This article analyzes Google’s large‑scale code review practices, showing how lightweight processes, tool‑driven automation, and a culture of knowledge transfer turned code review from a time‑consuming task into a productivity engine that scales across tens of thousands of engineers.
A brief analysis of Google’s code review data shows an average of five comments per 100 lines of code and two comments per change, with comment density decreasing from eight per 100 lines for new hires to 4.5 after three years of experience.
The article defines good code as functional and easy to modify, explains why focusing on maintainability and simplicity beats fast but fragile development, lists common signs of bad code, and offers concrete practices like small modules, clear naming, and test‑driven development to boost productivity.
This article reviews and compares three AI code editors—Trae, Cursor, and Augment—detailing personal usage experiences, performance, feature differences, cost, integration with MCP tools, suitable scenarios for solo entrepreneurs versus professional developers, and practical tips for improving workflow with AI assistance.
