> The script runs in the Code Execution tool (a sandboxed environment), pausing when it needs results from your tools. When you return tool results via the API, they're processed by the script rather than consumed by the model. The script continues executing, and Claude only sees the final output.
Anyone knows how they would have implemented the pause/resume functionality in the code execution sandbox? I can think of these: unikernels / Temporal / custom implementation of serializable continuations. Anything else?
Presumably, a tool call is just a library call in the script. The implementation would need to ask the environment outside the sandbox (through a socket?) to take some action on its behalf.
That's cool, but they say the code execution would wait till the tool call is done. Would they be just keeping the code execution process alive? That seems like a bad idea given tool calls can take an unknown amount of time to finish. I am guessing they would be putting the python orchestrator code to sleep when the tool call starts and restoring the state when the tool call is done.
From your point of view, what's the approach taken by someone who rose to the rank? Is it mostly people and process management and less to do with tech?
> do you find yourself developing the MVP of a particular feature to "get water through the pipes" and then handing that off to some other team to get it to "production ready"?
I liked your take and curious to know what you think a CTO should be doing here
Generally, I don't advocate for code getting thrown over the fence, regardless of the dynamics associated with the particular exchange. So the ideal approach here would be for the CTO to partner with a trusted engineer with some leadership capacity (tech lead, staff, etc.) and work through the architecture design and technical specifications for the project and get it off the ground and then hand that off to the tech lead that they partnered with so that they could carry it over the line, possibly with a team. Understanding the vision behind the project and why the CTO thought it was valuable is a critical aspect here. It turns what would otherwise be a low leverage project, mostly involving architecture and coding, into a much higher leverage project that's focused on educating and empowering other leaders in the organization. It also allows the CTO to stay close to the technical foundations and code so they don't lose touch with the organization that they're leading.
> What kind of code “looks good” to you? What kind of code “looks ugly”?
IMO this is not taste, it's your pattern recognition skill based on what you think is better in terms of correctness, performance and maintainability.
> Which design decisions you feel really good about, and which ones are just fine?
It's not just a feeling, it comes from reasoning.
Good taste == good skill isn't it?
When someone chooses a functional lang over an object oriented one - is this because of better taste? They’ve learned, through experience, what kinds of problems map more cleanly to immutability and composition versus encapsulation and state. Their "taste" for one paradigm over another is just a reflection of the skills they’ve built up in recognizing tradeoffs, debugging pain points, and anticipating long-term maintainability. What looks like taste is really just expertise shaping intuition.
I get why the author feels a team member who doesn't align with the team's goals has bad taste. But it's really just this - the opinions they have formed from their experience don't match yours.
I have a directory named “mystuff” that’s gitignored globally, in every repository I work on. This is where I store commands, snippets, scripts, ideas, meeting notes etc. To organize things I find on the web, I simply use bookmark folders in the browser.
In our company we use both github wiki and google drive to share knowledge.
Anyone knows how they would have implemented the pause/resume functionality in the code execution sandbox? I can think of these: unikernels / Temporal / custom implementation of serializable continuations. Anything else?