注册并分享邀请链接,可获得视频播放与邀请奖励。

与「REVIEW」相关的搜索结果

REVIEW 贴吧
一个关键词就是一个贴吧,路径全站唯一。
创建贴吧
用户
未找到
包含 REVIEW 的内容
I had Opus 4.8 in Claude Code write a sophisticated, if minor, academic paper from a archive of hundreds of de-identified research files from years ago I had to use GPT-5.5 Pro as a reviewer, it spotted one major error & some minor points. Opus corrected
显示更多
0
17
276
22
转发到社区
Activity on Sui mainnet has resumed after a halt due to a crash bug in the gas charging logic introduced by the 1.72 release. A full incident review will be shared in the coming days.
0
169
1K
152
转发到社区
During yesterday’s PRAGATI session, projects worth over Rs. 30,000 crore were reviewed. The works covered sectors like railways, power and road connectivity. Aspects relating to ports, Swachh Bharat Mission 2.0 and other social sector schemes were also discussed.
显示更多
0
537
7K
1K
转发到社区
Yesterday, our industry witnessed something unprecedented. In the past, when a CEX faced negative news, users could still freely move their assets to another platform. But this time, many users discovered something alarming: They were not unable to leave HTX — they suddenly had nowhere to go. Following the UK sanctions-related concerns around HTX, some third-party risk-control systems broadly labeled wallets interacting with HTX as “high risk.” As a result, many normal users experienced: restricted transfers, blocked transactions, and in some extreme cases, frozen accounts on other platforms simply for depositing funds from HTX. This level of large-scale, indiscriminate risk control against ordinary users is unprecedented in crypto history. What makes this even more troubling is: HTX itself is operating normally. Trading, deposits, withdrawals, and OTC services are all functioning as usual. But somehow, the users became the problem. And that is something the entire industry should reflect on. Because the people being affected are not “HTX users” alone. They also trade on Binance, OKX, Bybit, Coinbase, and many others. They belong to the crypto industry as a whole. If concerns exist around a platform, then measures should target the platform itself — not ordinary users through broad collateral damage. At the moment, HTX withdrawals remain fully operational. Users can still move assets on-chain. But if users eventually feel safer keeping funds only on-chain, or exiting entirely through OTC markets, then this is no longer an HTX issue. It becomes a crisis of trust for all centralized exchanges. And in a market already struggling with weak confidence, this could cause lasting damage to the entire industry. To put it simply: Crypto can survive without HTX. But crypto cannot survive without user trust. We want to clearly state: HTX fully supports compliance efforts and is actively cooperating with all relevant parties to resolve misunderstandings as quickly as possible. We respect the need for exchanges to follow compliance requirements. But we also believe ordinary users should not become victims of flawed or overly broad risk-control systems. Therefore, we sincerely call on all exchanges and industry partners to: 1️⃣ Work together with third-party security and compliance providers to address the current situation affecting users, and improve industry-wide risk-control standards. 2️⃣ Implement more precise review mechanisms for normal users interacting with HTX, so legitimate funds and users are not unfairly impacted. HTX is fully willing to cooperate throughout this process. Finally, to everyone who still trusts HTX and continues to keep assets on our platform: Thank you. HTX will not run away. We will stay here, face the situation directly, and continue working until these issues are fully resolved.
显示更多
0
19
59
11
转发到社区
Why is the creator of OpenCode pretty skeptical about AI productivity gains, and the hype around AI? A very conversation @thdxr (and lots of truth bombs:) Timestamps: 00:00 Intro 07:03 Dax’s path into tech 09:04 Early startup experience 13:16 Getting involved with open source 16:13 OpenCode 23:17 Anthropic banning OpenCode 30:34 From terminal to GUI 32:34 OpenCode’s business model 36:33 Why inference is profitable 39:11 GPU bottlenecks 40:54 AI hype 45:50 AI spending 48:47 Dax’s memo 55:41 Dax’s skepticism of predictions 58:58 Engineering culture at OpenCode 1:02:38 How building works at OpenCode 1:05:36 Taste and quality 1:11:32 Dax’s work setup 1:12:35 The role of engineers and EMs 1:15:50 Advice for engineers 1:18:12 Book recommendation Brought to you by: • @AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • @WorkOS – everything you need to make your app enterprise ready • @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable Three interesting thoughts from Dax: 1. No AI-native coding agent company is “winning” by being better with AI. Dax says that none of OpenCode’s competitors are crushing them, and that nobody is using AI so well that others cannot compete. 2. Most software engineers profit from AI as time gained, not increased output — unless you change incentives! Dax says the natural way for software engineers to “cash out” their AI tooling gains is with time savings, by doing the same work as before, but faster. Until compensation and motivation structures change, most teams should expect output to stay flat while engineers go home earlier. There’s nothing wrong with this, but AI vendors sell a different outcome to CFOs: increased output. 3. AI code generation mutes the “guilt” of doing the wrong thing, but this builds up tech debt. Pre-AI, writing a hack felt bad, the second time it felt really bad, and by the third time you’d often just refactor in order to fix up the code. Now, the agent hides the hack, which skews devs’ judgment and results in less tech debt being cleaned up.
显示更多
0
29
1.2K
84
转发到社区
让不同的 agent 交叉 review 的后果就是代码越改越多。。。
0
20
31
1
转发到社区
US FDA extends review of AstraZeneca’s experimental breast cancer pill
Houston fuel trader Ikon Midstream is under investigation in Mexico in connection with cartel-linked fuel smuggling, according to three Mexican security sources and four government security documents reviewed by Reuters @specialreports
显示更多
AI 编程赛道内卷加剧!Anthropic 再出企业安全重磅功能 2026年5月伦敦「Code w/ Claude」活动上,Anthropic 一口气放出两大核心安全更新,精准直击企业 AI 编码最大痛点:代码数据外泄、开发漏洞频发,正式正面对标 GitHub Copilot 企业版! 更新一:Claude 自托管沙箱(Claude Sandbox) 彻底打破公有云数据顾虑!采用「云端编排+本地执行」架构: 仅智能体逻辑留在 Anthropic 云端,所有代码、工具执行操作全部迁移至企业自有基础设施,完美实现「代码与仓库数据不出企业安全边界」。 兼容主流部署:Cloudflare / Daytona / Modal / Vercel 企业完全自主掌控运行环境、权限与审计日志 更新二:Security Guidance 安全插件 适配 Claude Code 的轻量化实时风控工具,嵌入开发全流程: 代码编辑、AI 生成变更、代码提交阶段自动扫描漏洞,智能识别风险代码、复盘代码差异,提前拦截安全隐患,无需人工逐一复核。 落地硬核效果 内部实测数据:研发团队的 PR 安全类评论直接减少 30%-40%,大幅降低安全 review 压力,提效又控险。 完整企业安全矩阵成型 本次更新叠加此前公布的 28 项企业合规安全集成能力,补齐了 AI 编程的最后一块安全短板。 不难看出,Anthropic 此番密集布局,核心目标就是强攻企业级 AI 编程市场,用私有化安全+实时漏洞防护,打响与 GitHub Copilot 的差异化竞争!
显示更多
China Memory-Chip Maker CXMT Clears Shanghai Listing Review