996 karma · joined April 5, 2013
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!)
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.
* Isolated workspaces: Each task runs in its own worktree so changes stay organized and conflict-free
* Review changes: Inspect diffs and proposed edits before applying them to your codebase
* Stay in flow: Switch between tasks without losing context or progress
* Automate workflows: Reuse repeatable tasks with configurable skills
* Works with your tools: Open changes in your editor and integrate with your existing setup
* Track progress: Follow what each agent is doing in real time
* Windows sandboxing: Run agent mode inside an OS-level sandbox, with bounded permissions and explicit approval for escalation
* Ship faster: Move from idea to working code with less overhead
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.
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.
Again, personal, experience, but in my team ~40-50% of the PRs are generated by Codex.
We configured it so it send me real time alerts when uncommon birds are detected.