Tokenmaxxing makes no sense, it is akin to write extremely inefficient SQL / Spark Jobs, full of cartesian joins, ultra skewed datasets, etc, just for the sake of using as much compute / memory / IO as possible.
This always happens when the metric becomes the goal, companies should nurture and foster an environment where AI is used in the most efficient way possible, first asking "do we really need an agent for this" and if so, what kind of agent is needed, what model, reasoning level, etc.
They should also promote projects that aim at saving tokens, increasing cache hits, codifying the information in ways such they use as less context as possible (graphs of knowledge are pretty good for this!)
Same! At first I was wary of using it because the UI looked less polished, but from the start the stability has been vastly superior and now the UI is much better too.
as a bonus, I have a old version Emby Theather (the windows form based one) that plays 4K with no issues on my computer unlike browsers that fail at that.
underrated comment, this is going to be the main differentiator going forward, the more powerful and versatile harness the more the models will be able to achieve and better/more advanced products will come out of it.
I am sad to know about this, Dan Simmons had a mind blowing amount of imagination and the ability to turn that into interesting and imaginative books that expanded my imagination when I read them.
I loved Hyperion cantos, Illium and then non sci-fi books like A Winter Haunting and Summer of night (which I read in the wrong order lol).
I am also happy to read that he was a great person overall and a great teacher.
May he rest in peace.
The variety of tasks they can do and will be asked to do is too wide and dissimilar, it will be very hard to have a transversal measurement, at most we will have area specific consensus that model X or Y is better, it is like saying one person is the best coder at everything, that does not exist.
Same here! I think it would be good if this could be made by default by the tooling. I've seen others using SQL for the same and even the proposal for a succinct way of representing this handoff data in the most compact way.
what I had in mind when I added that comment was for coding, with the use of .md files.
For the web version of chats I agree there is little control on how to tailor the way you want the agent to behave, unless you give a initial "setup" prompt.
It’s like having 3 coins and users preferring one or the other when tossing it because one coin gives consistently more heads (or tails) than the other coin.
What is better is to build a good set of rules and stick to one and then refine those rules over time as you get more experience using the tool or if the tool evolves and digress from the results you expect.
Personal experience here in a FAANG, there has been a considerable increase in:
1. Teams exploring how to leverage LLMs for coding.
2. Teams/orgs that already standardized some of the processes to work with LLMs (MCP servers, standardized the creation of the agents.md files, etc)
3. Teams actively using it for coding new features, documenting code, increasing test coverage, using it for code reviews etc.
Again, personal, experience, but in my team ~40-50% of the PRs are generated by Codex.
same, I had a great idea (and a decently detailed plan) to improve an open source project, but never had the time and willpower to dive into the code, with codex it was one night to set it up and then slowing implementing every step of what I had originally planned.