Tell Us What You Built: Share Your DevoxxGenie Success Story
The dedicated success-story page and embedded form have been retired. This announcement is retained for historical context. For current feedback and workflow discussions, use GitHub Discussions.
We have a lot of numbers. The growth curve keeps climbing, and the analytics deep-dive told us which providers and features people actually reach for. What none of that tells us is the interesting part: what you are building with DevoxxGenie, and what it changed about your day.
The original invitation was to share those experiences through a dedicated form. That collection page is now retired; GitHub Discussions remains open for feedback.
Why we are asking
Analytics are great at what and terrible at why. We can see that most usage runs on local models. We cannot see that you moved to a local model because your employer will not let code leave the building, or that a 40 minute review ritual turned into a 5 minute one, or that the feature you rely on most is the one we almost cut.
That gap matters for three reasons:
- It sets the roadmap. Every serious feature in the plugin, from agent mode to spec-driven development, exists because someone described a real workflow that did not fit. A dashboard has never once suggested a feature.
- It helps other developers. "Should I put an AI assistant in my IDE, and can it run on my own hardware?" is a question a lot of teams are asking right now. A concrete story from someone with the same constraints answers it far better than a feature list does.
- It keeps an open-source project going. DevoxxGenie is free and open source. Knowing the thing is genuinely useful to people is most of the fuel.
What makes a good story
Do not overthink it. A few honest paragraphs beat a polished case study. The things we are most curious about:
- What you build. Language, stack, team size, the kind of codebase (greenfield, legacy, monorepo, embedded, whatever it is).
- What you actually use it for. Reviews, refactoring, tests, docs, understanding unfamiliar code, batch task execution with the Agent Loop?
- Local or cloud, and why. Privacy rules, cost, latency, offline work, or simply because a model on your own machine turned out to be good enough.
- What changed. This is the bit people remember. Anything you can put a number on is gold, but "I stopped dreading dependency upgrades" is a perfectly good outcome too.
- What still annoys you. Genuinely. The critical stories are the useful ones, and nothing gets fixed that we never hear about.
Where stories end up
The original form invited stories for possible publication on the site, blog, or newsletter, subject to explicit consent and the contributor's choice of credit. That form is no longer available. GitHub Discussions is a public forum: do not include private project details or secrets in feedback there.
Not a success story? Still send it
Bug reports are best filed as GitHub issues, where they can be tracked and fixed. For workflow friction, ideas, or general feedback, start a GitHub Discussion.
Take five minutes
Share feedback on GitHub Discussions
If DevoxxGenie has saved you time, taught you something, or quietly become part of how you work, we would still like to hear about it through the community channels above.
Thank you. 🙏
