11,480 karma · joined December 18, 2009
@iandanforth
Source available - https://www.openhumans.org/member/iandanforth/
meet.hn/city/us-Pittsburgh
Is this a case of bureaucracy forcing people into illegality?
My plan is to create shadow accounts for Atlas and use it to automate tedious research tasks that span multiple websites that other AIs have trouble accessing.
Duck typing is one of the best things about Python. It provides a developer experience second to none. Need to iterate over a collection of things? Great! Just do it! As long as it is an iterable (defined by methods, not by type) you can use it anywhere you want to. Want to create a data object that maps any hashable type to just about anything else? Dict has you covered! Put anything you want in there and don't worry about it.
If we ended up with a largely bug free production system then it might be worth it, but, just like other truly strongly typed languages, that doesn't happen, so I've sacrificed my developer experience for an unfulfilled promise.
If I wanted to use a strongly typed language I would, I don't, and the creeping infection of type enforcement into production codebases makes it hard to use the language I love professionally.
One statement surprised me was that the author thinks "models over time will just be able to output JSON perfectly without the need for constraining over time."
I'm not sure how this conclusion was reached. "Perfectly" is a bar that probabilistic sampling cannot meet.
How is this not a straight up lie? For this to be true they would have to throw away labeled training data.
For evil-aligned founders it's important to realize that exploiting workers is one of the best trod paths to success. If you can get away with it without causing a revolt you're almost certainly getting more for your money. So being up front with 996 is absolutely in your interests. Being hard-core, 10x, cracked (pick your generation's euphemism) is just good marketing. Be prepared to cut anyone who burns out, try to get people without any ties or those who can't afford to quit. Maybe even create a cult of personality around yourself.
There is no merit to discussing if the target is that thing, it doesn't matter. It's an ideological attack. If you take it on its face then the attackers win because you're treating them as if they were honest participants in a discussion, which they are not.
And remember even if the investigation (which is a farce) goes nowhere, allowing it to exist unchallenged means that some people are going to be harassed and intimidated. But, that too is the point, fear is what they want.
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.
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!
The promise and potential of LLM based language learning apps is that you can cross that gap to full immersion in a way that has never been possible before.
Please be more ambitious.