aws / aws/aws-toolkit-visual-studio
Should my company still use Amazon Q?
- Dominant language
- No language data
- Stars
- 135
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
My current recommendation is no, and this extension is why.
The Visual Studio version is crap, it has so many issues and is being treated like an open source project when we pay Pro pricing.
I have created two bug requests that are very specific and informational. Should be pretty straight forward to address. It has been a month and not even a comment on either.
So I ask, why would any company want to stay with Amazon Q when other companies actually show interest in their customers, especially the paying ones?
Contributor guide
Research direction
The issue contains no file, test, entry point, or concrete defect to investigate. Start by locating the two separate bug requests referenced in the body and review their current status; this issue itself has no defined implementation scope or verifiable done condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100