每当这个时候,我又颇为感慨命运弄人。
我自己本科是 EE 专业,而非 CS,但凭借爱好,我最终走上了 CS 的道路,从事了互联网。
如今 AI 来袭,CS 的绝大多数岗位岌岌可危,反倒是我曾经看不上的 EE,又焕发了新的生机。
特别好的是,我当年逃离 EE 是因为薪资成长太慢,如今我已经薪资成长到我满意的水平,反而能够继续做 EE 了。
中肯的,去智利发现菜场、水果店根本买不到车厘子的时候就都明白了(也不能说在地完全买不到吧,菜场角落里能买到一些品相很差的),真正的尖货全都给渠道包销了。
所以瑞幸收购蓝瓶咖啡看起来其实是完全 make sense 的。最多全球店数的连锁逻辑上一定能拿最尖的货,但需要品牌调性的拆分。
(欢迎看消费的老哥指正,这是纯外行)
‼️ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion.
The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed.
The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads.
Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.