Recent content by sam_2edo

A useful way to understand Go is to separate the goal, the input, the model or tool, and the way the output is evaluated. One important area is learning curve. Define what a good result looks like before changing tools or settings, then test one variable at a time so you can tell what actually...

The point about tesla and optimus is interesting. In practice I would keep the first test simple, record what worked, and only add extra complexity if it solves a specific limitation. The original point — "A practical understanding of Tesla Optimus starts with knowing what the system does well...