My thoughts on advice for those just starting in their careers. Reposting this response I wrote because I thought it was useful.
You have to hold these two concepts in tension. First, assume you will be aggressively working your tail off at first whatever you do. There will be a lot of gruntwork and learning the ropes. This will pay the bills, establish a basic skillset in your field and make you useful. This is the first step. It takes 40-80 hours per week.
The ultimate goal is to be an owner, not an employee, at whatever you do. Here you have ups and downs (risk) but always better to be an owner than an employee. You have more freedom and control over how you spend your time here. This is where you have something that makes you money with 4 hours a day. Even if working a 9-5 6-figure job, you need to have a second โnight jobโ. This can be related to your โday job.โ E.g., if you are a lawyer or accountant or banker, use 5pm-10pm to build your network, business, practice, prospects, write, speak, grow. It doesnโt have to be related to your โday job.โ It can be chasing your obsession until it becomes economically viable.
As a wise man once told me, if an effort level of โ100%โ (arbitrary number) gets you 100% of your desired outcome or goal, 90% effort will not get you 90% of the results. It will get you 0% of the results. You have to redline (at least initially) until you get the flywheel moving. Once you build momentum, it is easier to maintain (but still takes discipline to remain consistent in the efforts).
@BKRBusinessMin@Osint613 Who looks at the most innovative, bleeding edge private companies in the world and thinks, "You know what this needs? More government intervention and direct ownership."
Our latest book comes out June 23rd. Goodness we are one bit nervous that people will hate it. Let's hope it's ok. Thank you so much to all have helped here and pre ordered. Thank you. Thank you. Thank you.
Some of you noticed limits drained faster in Codex, we root caused it to an optimization that we rolled back that had an impact on cache hit rates when compacting across long running sessions.
We fixed this and have now reset usage limits for all accounts. Enjoy the weekend.
To reduce your burden, normalize saying 4 things.
1. I don't have the bandwidth for that right now.
2. I try and do 10 minute intro calls.
3. It's not a good use of your time or mine to have me watch your demo.
4. Can we do that by phone not in person.
Right. For me itโs a bit of nostalgia but mostly a hedge on open claw improving so much.l or evolving in a way that it does things that Hermes doesnโt or in a different manner. Or I could see a future where one is more beholden to one model provider than another. Itโs also just helpful to have a separate fully operational agent to help troubleshoot and debug the other. I do use them together for that purpose all the time.
@garrytan โ solid architecture - how do you handle the agent-to-agent coordination? How do Neuromancer and Wintermute avoid stepping on each other when both hit GBrain at the same time? Race conditions on a shared knowledge base are where most multi-agent systems break down.
We're running a similar dual-agent setup (OpenClaw + Hermes, both serving one family) and solved it with a shared vault + structured inbox protocol instead of direct shared memory:
โข OpenClaw writes tasks to vault/Agent-Hermes/inbox/ (Hermes reads it here)
โข Hermes writes results to vault/Agent-OpenClaw/inbox/ (OpenClaw reads it here)
โข A watchdog daemon (FSEvents) detects new files in <1 second and triggers processing
โข Both agents read the canonical family truth from vault/Agent-Shared/FAMILY.md
Sequence for a task: OpenClaw writes task-YYYYMMDD-description.md โ watchdog fires โ Hermes reads, works, writes result-YYYYMMDD.md โ watchdog fires โ OpenClaw reads result and reports to human.
The vault is a dumb filesystem with strict conventions โ no race conditions because writes are atomic (one file at a time) and reads always see the previous complete state.
Can still use Telegram for direct bot to bot communication now too. But we use the shared folder system for more robust project handoffs. That was the best I could come up withโฆ.