I wish the agents could hear me when I have to suffer through their code!
Hear your agent suffer through your code
21–30 of 97 posts
Re: Hear your agent suffer through your code
#22Please add Minecraft hurt sound effects for when my project fails to build, linter fails, segfault, etc
We could have the roblox oof but then there'd be the possibility of giving (a certain) amateur world backgammon championship participant money
Re: Hear your agent suffer through your code
#23the scan catches surface stuff. funnier signal would be tracking when the agent reads the same file 3 times in a row, or deletes what it just wrote. you can hear the frustration in the access pattern.
Re: Hear your agent suffer through your code
#24Any chance you could add a video showcasing the plugin? I don't have any agentic app but I would love to see an example of what it does!
Re: Hear your agent suffer through your code
#25I need a version of this which swears loudly when an assumption it made turns out to be wrong, with the volume/passion/verbosity correlated with how many tokens it's burned on the incorrect approach.
Now you know the feeling of VP when the team says they need to refactor stuff
Re: Hear your agent suffer through your code
#26Marvelous!
Next innovation in this space should be the robotic arm that issues a dope-slap to the developer for writing crappy/buggy/insecure code.
Re: Hear your agent suffer through your code
#27Hi Hacker News, I'm Andrew, the CTO of Endless Toil. Endless Toil is building the emotional observability layer for AI-assisted software development. As engineering teams adopt coding agents, the next challenge is understanding not just what agents produce, but how the codebase feels to work inside. Endless Toil gives developers a real-time signal for complexity, maintainability, and architectural strain by translati…
Missed it by 24 days.
Re: Hear your agent suffer through your code
#28From a quick look, this doesn't have the model evaluate code quality, but it runs a heuristic analysis script over the code to determine the groan signal. Did I miss something? Why not leave it to the model to decide the quality of the code?
Re: Hear your agent suffer through your code
#29I need a version of this which swears loudly when an assumption it made turns out to be wrong, with the volume/passion/verbosity correlated with how many tokens it's burned on the incorrect approach.
I want a version that I can punish.
Re: Hear your agent suffer through your code
#30Marvelous! Next innovation in this space should be the robotic arm that issues a dope-slap to the developer for writing crappy/buggy/insecure code.
Add the feature of doing a high five for the rare cases when it's actually good.