RayW

如果，我是说如果。 假如我的 followers 里有相对年轻的求职者，正好在找工程方向的工作。 我相信你的简历里一定有一些自己做过或者正在做的项目，不管是不是 vibe 的，当下这个时间节点大概率做的可能靠 agent 方向多一点。 或者是个 workflow，或者是之前的 dify 二开等。 概率比较大。 每个面试官可能角度不一样，有的也许就爱看你做出几十个应用，洋洋洒洒。 但从偏向技术和工程的角度，我建议你不要贪多。 这个时代多没什么用，花点钱买点 token 的事。 做了什么爆款，也许有人会看重一些，但相信我，价值优先。 毕竟小猫补光灯都能上榜一。 我还是建议你打磨好一个项目。越是这个容易 vibe 出东西的时代，你在一个项目上打磨，投入的心血，对这个方向的理解，都价值连城。 哪怕方向在当下看起来也许是错的或者不受欢迎——比如简历上我看的每个人都碰过 RAG，一问为什么今天看起来有点日渐式微，很多人答不上来。 也不是说 RAG 就是错，如果你坚定的在这个方向上打磨，尝试过各种策略，把你的经验，踩过的坑，benchmark，结论，你做过的尝试——这些能和人描述出来—— 你知道你在一个真正想招工程师的面试官眼里有多发光吗？ （以上不是说 RAG 不行，RAG 是个涵盖超广的概念，其实 grep 也算 RAG 的手段，狭义广义的我就不展开了） 真的干过，思考过，一个方向折腾过——哪怕一路都是借助 AI，都是你的加分项。 巨大的加分项。

We’ve received notice that the Department of Commerce has lifted export controls on Claude Fable 5 and Mythos 5. We'll begin restoring access tomorrow, and will share an update soon. We’re grateful to our users for their patience, and to everyone who worked with us on redeploying the models.

Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours. We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a few smaller problems compounded for some users. Here's what we found and changed: - Actual usage: Auto-review had become more proactive, another change was triggering more subagent work, and background suggestions could run twice or retry too frequently after failures. We reverted the changes and fixed suggestion scheduling, duplicate generation, and retry behavior. This should reduce unnecessary background token consumption while preserving the work users explicitly request. - Usage reporting: Auto-review was incorrectly appearing as GPT‑5.4 usage, and failed or rate-limited requests were still shown as turns. Auto-review now appears as its own category, and only successful requests count toward the turn graphs. Rate-limited requests were never charged, but they were being displayed incorrectly. - Immediate relief: We reset usage limits while rolling out the fixes, then shipped hotfixes across the CLI, desktop app, and usage backend. - What to expect: New usage data should be clearer and actual consumption should be lower. Historical charts may still show auto-review under GPT‑5.4 because older turn data was not relabeled. Features that intentionally perform more work; such as /goal, subagents, and higher reasoning levels will still naturally use more capacity. All fixes are now deployed, and we've added more detailed monitoring so we can detect background-usage regressions sooner. We'll continue watching the results closely. Thank you for building and doing all sorts of things with Codex.