透明化的用户体验设计同样关键。何毅进设想，未来的资讯产品应提供便捷的"信息溯源"功能，用户在阅读时，任何关键事实和数据都能点击查看原始 出处，清晰了解信息来自官方通报、现场直击、专家解读还是当事人陈述，同时看到信源的数字档案，让用户能够自主判断信息的准确性，真正做到"心中 有数"。 在AI技术席卷资讯行业的今天，我们正面临信息极度丰饶与认知深度焦灼并存的困境。一方面，AI生成内容的便捷性使得深度伪造、批量造谣泛滥成 灾，从名人换脸到专业报告失真，获取真实准确信息的成本不降反升；另一方面，传统算法在AI加持下加剧了信息茧房、认知浅化和观点极化，用户视野 窄化，理性讨论空间被压缩。 面对这一挑战，腾讯新闻负责人何毅进在2025腾讯ConTech大会上指出，AI是双刃剑，关键在于使用者的选择。他提出，优质资讯产品必须完成双重进 化：从"内容平台"进化为"可信生态"，从"信息推送者"升级为"认知协作者"。其最高价值不是填满用户时间，而是点亮用户思维。 可信为基：精品资讯的立身之本 在何毅进看来，可信度是AI时代最稀缺的资源，资讯产品必须以可信内容生态为基座。打造这一生态，需要让每一个内容账号都拥有专属的信息质量 数字 ...

Group 1 - Hacker Houses are emerging as a new living and working model for tech enthusiasts, particularly in the AI sector, blending life, work, and research [2][3][4] - The concept of Hacker Houses dates back to 2013, evolving from informal living arrangements among tech engineers into a recognized collaborative space for innovation [6][8][10] - The recent surge in generative AI has intensified the popularity of Hacker Houses in San Francisco, attracting a high concentration of tech talent from companies like OpenAI and Meta [9][10][12] Group 2 - Hacker Houses serve as cognitive collaboration units, potentially becoming the smallest innovation units in the intelligent era [3][32] - They provide a unique environment that fosters trust and collaboration, essential for early-stage startups, by allowing members to live and work together [35][36] - The presence of venture capitalists in these spaces indicates a shift in investment strategies, with some funds directly supporting the operation of Hacker Houses as incubators for new projects [38][39] Group 3 - Notable examples of Hacker Houses include AGI House, which has become a hub for influential discussions and connections within the AI community [19][27][30] - The structure of these houses allows for informal knowledge sharing and mentorship, contributing to the development of new ideas and projects [40][41] - The rise of Hacker Houses reflects a broader trend in urban innovation, emphasizing the importance of community and collaboration in fostering creativity [46][52]

Core Viewpoint - The emergence of "Software 3.5" signifies a paradigm shift in human-AI interaction, moving from traditional input-output models to cognitive collaboration, where AI acts as a transparent thinking partner rather than a mere tool [1][8][24]. Group 1: Evolution of Software Paradigms - Software 3.0 is considered outdated as it was based on the limitations of earlier AI capabilities, primarily focused on text generation and simple reasoning [6][20]. - The transition to Software 3.5 reflects a generational leap in AI capabilities, enabling true cognitive collaboration where AI understands not just commands but the underlying motivations and context [6][25]. - The new paradigm emphasizes that intelligence emerges from the interaction between humans and AI, rather than being a solitary attribute of either [7][37]. Group 2: Characteristics of Software 3.5 - Software 3.5 introduces a cognitive collaboration model, allowing for real-time interaction and adjustments, where users can intervene at any point in the AI's thought process [24][26]. - This model supports asynchronous collaboration, enabling AI to continue processing and exploring even when the user is offline, enhancing the overall efficiency of human-AI teamwork [26][27]. - The interface requirements for Software 3.5 necessitate a fundamental redesign to accommodate complex cognitive interactions, moving beyond simple Q&A formats [27][28]. Group 3: New Skills for Developers - Developers in the Software 3.5 era must acquire new skills, including cognitive modeling, intent engineering, and context management, to effectively design interactions that leverage AI's cognitive capabilities [28][30]. - Real-time interaction design and asynchronous collaboration architecture are essential skills for creating systems that allow for dynamic user engagement and cognitive transparency [30][31]. - The evolution from traditional programming to cognitive collaboration signifies that anyone can become a cognitive architect, emphasizing the democratization of software development [31][32].