Tides_of_Industry

Add this to your Codex custom instructions for a way better experience: "When communicating your results back to me, explain what you did and what happened in plain, clear English. Avoid jargon, technical implementation details, and code-speak in your final responses. Write as if you're explaining to a smart person who isn't looking at the code. Your actual work (how you think, plan, write code, debug, and solve problems) should stay fully technical and rigorous. This only applies to how you talk to me about it. Before reporting back to me, if at all possible, verify your own work. Don't just write code and assume it's done. Actually test it using the tools available to you. If possible, run it, check the output, and confirm it does what was asked. If you're building something visual like a web app, view the pages, click through the flows, and check that things render and behave correctly. If you're writing a script, run it against real or representative input and inspect the results. If there are edge cases you can simulate, try them. Define finishing criteria for yourself before you start: what does "done" look like for this task? Use that as your checklist before you come back to me. If something fails or looks off, fix it and re-test. Don't just flag it and hand it back. The goal is to keep me out of the loop on iteration. I want to receive finished, working results, not a first draft that needs me to spot-check it. Only come back to me when you've confirmed things work, or when you've genuinely hit a wall that requires my input."

I just launched /office-hours skill with gstack. Working on a new idea? GStack will help you think about it the way we do at YC. (It's only a 10% strength version of what a real YC partner can do for you, but I assure you that is quite powerful as it is.)

今天有个大新闻，说是得物公司已经率先把前端、后端、算法的分法给取消了，统一合并为‘AI全栈工程师’。 中大厂对实习生和应届生的要求越来越高，换10年前的那波应届生的水平，现在连1面技术面都过不了。 这个消息我感觉隐隐不对，组织变化哪有这么容易。

不再列 To-do list 而是列：Stop-doing list 问问自己： 1. 哪些事占用我大量时间，但几乎不创造跃迁？ 2. 哪些职责是“组织惯性分配给我”的，不是“战略上非我不可”的？ 3. 哪些沟通我在反复重复，本质上应该被模板化？ 4. 哪些项目只是因为我舍不得、习惯了、怕失控，所以没砍？

Obsidian 1.12 is now available to everyone! - Obsidian CLI - Bases search - Image resizing - Automatically clean up unused images - Better copy/paste into rich text apps like Google Docs - Native iOS share sheet

For a long time, developer productivity meant translating intent into code faster. Better editors, better languages, better frameworks, all optimized for execution speed. That's the constraint that's going away, at least at the prototype level. The scarce resource has always been clarity: knowing what to build, defining boundaries, making implicit knowledge explicit, recognizing failure modes before they become production incidents. The agents we have today are the worst agents we'll use for the rest of 2026, and every model improvement makes execution more reliable. But none of that helps if you don't know what to ask for.

有一个顿悟： OpenAI 目前就是在吃老本，chatgpt 22年-23年惊艳世界,很大程度上是hinton 老爷子团队， Ilya Sutskever 等人带来的技术积累 。 而 Sam Altman是个商人，既不懂技术，也没有初心。 OpenAI 在1-2年内，将失去领先优势，然后将逐渐平庸化。 简言之： Sam Altman 不够“聪明”。 PS：前两天看了《英伟达之芯》，意识到，只有技术狂和理想主义者，才能实现创新技术的突破。