I don't want my package manager to format anything.
I don't want my package manager to lint anything.
I don't want my package manager to `run` anything.
I don't want my package manager to even manage environments (yes yes this one is a bit extreme).
I want to have single purpose tools that work together well.
This way I can have a flexible, composable toolchain that can both adapt to me and my specific project.
For example, I like conda, pip, ruff, mypy, flake8. Someone else might like venv, pip, black, pyright, flake8.
This is the heart of the Unix Philosophy and I feel like it's a philosophy each software community has to reject, suffer due to that rejection, and re-adopt on a regular basis. I'd rather we skip the suffering bit.
''' A four panel comic strip. Simple black on white. Stick figures for characters. In the first panel there is a stick figure man and a stick figure bird eating bird seed at his feet. He is slightly hunched over to show he is looking at the bird. In the second panel. He is more hunched over looking more closely at the bird. In the third panel he is even more hunched over practically with his head to the bird, he is crouched down, knees bent, hands on thighs. In the upper left of the third panel the tip of an enormous beak can be seen, but it's only a few lines so could be anything. In the final panel the beak has gobbled up the man and his arms and legs are flailing outside of the beak while the small bird continues to eat birdseed on the ground. '''
The key point about RL is that it is a sequential decision making process. If you don't have something (an agent) making multiple decisions over time while interacting with an environment, then why bother calling it RL?
"Don’t use agents or things like editor with integrated coding agents."
He argues that the copy/paste back and forth with the web UI is essential for maintaining control and providing the correct context.
Foxglove is the leading observability stack for robotics and physical AI. We accelerate robotics developers with logging, data management, and multimodal visualization. We're well funded (Series A, ~35 people) and assembling the most talented team in the industry to build a platform for all robots. Sound interesting? Join us!
** San Francisco, CA **
- ML / Robotics Engineer, Dev Relations (python, c++, rust, ros, lerobot, etc)
- Staff Frontend Engineer (typescript, rust, webgl, wasm)
** Remote / other locations (Seattle, London) **
- Forward Deployed Engineer (typescript, python, plus ideally some c++ or rust experience)
That’s when it hit him: The goal is to repeat. Repetition isn’t a goal that has to be programmed in from the outside; it’s baked into the very nature of things—to exist from one moment to the next is to repeat your existence. “This goal function,” Putnam wrote, “appears pre-encoded in the nature of being itself.”
So, here’s the game. The system starts out in a random mix of “on” and “off” states. Its goal is to repeat that state—to stay the same. But in each turn, a perturbation from the environment moves through the system, flipping states, and the system has to emit the right sequence of moves (by forming the right self-reinforcing loops) to alter the environment in such a way that it will perturb the system back to its original state."
I'm a big fan of this line of thinking. I've been arguing for years that RL should be based in homeostasis and this seems right along those lines. I wish I could have talked with him!