@manateelazycat: YC's video is worth watching. He hit the nail on the head sharing how AI-native companies should think about organizational structure. I really agree with several key points: 1. The company is a Roman legion, where individual soldiers are strong and there are no weak links, so they never fall into chaos during any tactical execution. 2. The co-pilot model is wrong; we should let AI do it completely because AI executes 10 to 100 times faster than you. If it makes mistakes, just redo it; the second and third attempts are still much faster than you writing code manually. 3. Burn tokens, not heads. That is so true. I think any AI-native company should give employees unlimited tokens. Like our company: many ask how we reimburse AI costs. We don't reimburse; we give everyone unlimited GPT 5.5 tokens, use as much as you want, no reimbursement process. Only with unlimited tokens will people use them and unleash their creativity without psychological burden. 4. Make everything clear and readable for AI. Let me interpret: previously you wrote documents manually, and people didn't want to. Now open up all document interfaces and MCP to AI as much as possible. When you open up to AI, it can use its organizational capabilities to create new company processes. Previously, building internal infrastructure systems was difficult due to huge workloads and many aspects. Now, as long as you expose enough MCPs and APIs, new processes are a matter of one sentence. 5. People are temporary, but contextual documents are important. That's also well said. In the future, the most important things for software companies will be requirement documents, context documents, and process documents. Because code is easy to recreate, but these documents and thought processes are the company's real assets. Alright, that's today's share. Welcome to like, bookmark, and repost. Follow me, I'm a veteran who has been working on operating systems for over 20 years. My daily job is browsing Twitter and reposting valuable content to save your time.

This video from YC is worth watching

He insightfully broke down how AI-native companies should think about organizational structure.

I strongly agree with several of his points:

1. A company is like a Roman legion. The key strength of a Roman legion is that every soldier is individually capable — no weak links — so they never fall into chaos when executing any tactic.

2. The co-pilot model is wrong. You should fully delegate to AI, because AI’s execution speed is 10 to 100 times yours. If it makes a mistake, just redo it — doing it a second or third time is still much faster than writing code manually.

3. Burn tokens, not heads. This is absolutely right. I think any AI-native company should give employees unlimited tokens. In our company, many people ask how we reimburse AI costs. I say we don’t reimburse — we give everyone unlimited GPT-5.5 tokens, use as much as you need, no reimbursement process. Only with unlimited tokens will people feel free to use them and unleash their creativity without any mental burden.

4. Make everything clearly readable for AI. Let me interpret this for you. Previously, all documentation was written manually, and people didn’t want to write it. Now, open up all your documentation interfaces and MCPs to AI as much as possible. When you do, AI can use its organizational capabilities to create new company processes. For example, when we used to build internal infrastructure systems, the workload was huge and covered many areas, so many things couldn’t move forward. Now, as long as you expose enough MCPs and APIs, a new process is just a single sentence away.

5. People are temporary; contextual documentation is what matters. This is also very well said. In the future, the most important assets for a software company will be requirement documents, context documents, and these process documents. Because code is easy to recreate, but these documents and the thought processes behind them are the company’s real assets.

Alright, that’s all for today’s share. Welcome to like, bookmark, and share.

Follow me. I’m a veteran with over 20 years in operating systems. My daily job is to browse Twitter and reshare valuable content to save you time.

Y Combinator (@ycombinator): In a recent batch talk, YC General Partner @t_blom broke down how to build a self-improving, AI-native company.

He walks through how to create recursive, self-improving AI loops, and why founders who get this right will run companies that improve while they sleep.

00:00 —