503 karma · joined September 8, 2010
Here's some quick feedback -- hope it's useful:
1. Is the little bug icon sufficiently visible? I'm not sure...
2. Do visitors automatically know what to do with the bug? You have a tooltip, but do all visitors know what "Spotted a bug?" means?
3. [more of a suggestion; perhaps it does this already] Would be great if the bug position pulled in a CSS class or the content surrounding the "dropped" bug -- to give more context to the site owner.
The "context-in-the-codebase" thing for AI-based IDEsis overrated IMO. To extract the most from it, you have to remember to @mention the files.
If you don't remember to @mention specific files, the agent simply tries to perform searches (i.e., it has access to that tool) on the files and folders until it gets some results... and will usually keep broadening the search until it does.
It works well enough I suppose. But I still find myself beginning new chats (for example, per feature) because the model still loses its place, and with all the code/lint fixes it does, it starts to lose context.
Then you're right back having to @mention more files to ensure the model knows how to structure your front end, back end, etc.
(Please excuse any misnamed development terms.) :-)
"In 2025, Quilty forecast that it [Starlink] will count 7.8 million people around the world as customers and generate $11.8 billion in sales."
It is currently and likely will continue to be the biggest revenue driver for SpaceX, Mexico or not.