-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
State of AI 2025 Preview #278
Comments
|
Suggestion: put IDE/code generation sections first to avoid people filling out "cursor" in "coding assistant" section? |
Since this is targeted at web devs, I wonder if there should be questions about APIs as well. Edit: I now see that there's an AI browser API which I missed. |
|
Braindump of notes as I run through the survey:
The things I'm missing the most out of this as someone who's following AI very closely (weekly podcast for the past 2 years) are:
|
I think we miss "GitHub Spark" alongside v0 and bolt in the code generation section. It's in technical preview but will probably aim at being a big player : https://githubnext.com/projects/github-spark/ |
To answer about agents: the problem is that we are entering the build-your-own LLM solution category. That could be inserted somehow into the "Usage" question, asking whether people are crafting their own AI pipelines/agents/whatever advanced solutions. This could be relevant given that with frameworks such as langchain it can be actually relatively easy and I see a lot of developers crafting their homemade tools. |
Another question: should we ask about specific models, rather than just "apps"? e.g. GPT 4o, o1, deepseek r1… I guess I'm not sure how many people are aware of which model they're even using? |
|
Thanks so much for all the feedback! I'll have to do some more research into all these topics! Generally I would say these are all great suggestions but maybe still a bit too niche/early-adopter-focused?
I'm not sure I know enough about agents to write that question, and I feel maybe it's still a bit too early? Operator isn't even fully available yet.
I think we could ask this as a yes/no question for now? And then maybe get more granular next survey?
These also seem a bit too niche given that we're not surveying only AI-industry people, but "regular" web developers. |
@SachaG an agent is more a pattern than a specific solution, basically it's an agent as soon as your LLM starts talking to itself and using tools, it can be as simple as a while loop around an API call. So web developers may implement their own agent, or use one at company level. I think tracking agent usage/development it could be a good indicator of devs and ecosystem maturity. Or at least whether they have some sort of homemade/company-wide LLM solution around. Apart from that I've discovered the open source project Cline, which seems pretty popular. It works as a VS code extension like GitHub Copilot and could be mentioned alongside other assistants. Also I suspect Microsoft Copilot will be conflated with GitHub Copilot. |
Hello 👋 @eric-burel told me about this exciting initiative, great job guys and thanks for doing it 😄 I'm not sure to understand if you want to do a survey about AI tools for developers, about AI tools used by developers to create product or both. If you also aim AI tools used by developers to create product, then I think you could add questions/sections for:
Also, I have few remark about existing sections, feel free to comment on my comment 😁 Models part
Also it could be interesting to ask user which kind of model they are using, usually we can classify LLM in 3 categories:
Other tools part(Could be a library part) Some suggestion on interesting tools from the ecosystem: I think for each tool, an interesting question could ask if the user use this tool for a POC, personnal project or a production project:
|
Here is a preview link for the upcoming State of Web Dev AI 2025 survey, the first ever edition of this new survey:
https://survey.devographics.com/en-US/survey/state-of-ai/2025
I would love to get feedback on:
The text was updated successfully, but these errors were encountered: