吵翻了！CTO 不搞管理反而沉迷写代码改 Bug，还靠这保住百万订单。网友：小公司才敢这么干，大公司早乱了

Core Viewpoint - The article emphasizes the importance of CTOs continuing to write code, as it allows them to maintain technical sharpness, understand the real state of systems, and create unique value paths for their companies [1][2]. Group 1: Reasons for Writing Code - Many CTOs stop coding as they rise in their careers, often spending their time in meetings instead [3]. - The author, however, has produced significant code output over the past year, independently delivering several important features [5]. - The coding work is categorized into three types: long-term exploratory projects, urgent customer needs, and bug fixes [7]. Group 2: Types of Coding Work - Long-term Exploratory Projects: Few individuals in a company can independently develop and deliver new features. The author believes that pushing new ideas requires long-term investment, which is often limited by organizational structures [8][9]. - Urgent Customer Needs: When important clients have urgent requests that could impact significant orders, the author prefers to address these needs directly, leveraging their understanding of the business context [12][13]. - Bug Fixes: The author finds that fixing bugs helps maintain a deep understanding of the codebase, which is crucial for making informed decisions about technical debt and team priorities [15]. Group 3: Benefits of Coding - Writing code allows the CTO to discern what tools are genuinely useful based on firsthand experience, which aids in strategic decisions like tool selection and hiring [18][19]. - The author enjoys coding and prefers it over managing teams, allowing them to focus on product development and technical problem-solving [20][21]. - The use of AI tools has significantly increased the author's work efficiency, allowing them to provide context and make decisions rather than writing code line by line [22][23]. Group 4: Finding the Right Work Style - The article discusses the flexibility of the CTO role, highlighting that there is no one-size-fits-all approach. The author has found that writing code aligns with their skills and interests, enabling them to create maximum value [24]. - The author encourages engineers to find their unique advantages rather than conforming to a standard path in management [25].