I’m thinking about the questions for this year’s State of Elm survey, and am at the point where I could use some feedback on them.
So, here they are with questions below.
Do you use Elm?
Yes, at work
Yes, in side projects
Yes, as a student
I used to, but don’t any more
No, but I’m curious about it
No, and I don’t intend to
In which domains are you applying Elm?
In prior years, this has been things like “healthcare” and “education”.
How long have you been using Elm?
This is a scale with a small number of months, then a small number of years.
How far along is your most mature Elm project?
Options:
Considering for a future project
In the planning / learning / exploration phase
In development
In staging
Shipped / released to users / in production
Is that project at…
work, side project, open source
What versions of Elm are you using?
What is your level of experience with functional programming?
What programming community are you “coming from?”
Last year this was “what language”. Note on this question: “none” or “new programmer” should be encouraged as a valid answer.
Where do you go for Elm news and discussion?
What did/do you use to learn Elm?
Resources, classes, et cetera?
Is there an Elm meetup near you?
What’s the nearest big city to you?
Do you format your code with elm-format?
Same answers as last year, essentially:
yes, and I prefer it
no, I don’t like it
no, but I’ve heard of it
no, and I’ve never heard of it
What do you like the most about your use of Elm?
What has been the biggest pain point in your use of Elm?
When you have to integrate with JavaScript, what’s usually the reason?
My questions about these questions:
Do they answer the things we want to know about the community?
Is there a better place to host this than Typeform? I’d basically like to populate autocomplete for fill-in-the-blanks with sanitized answers from last year.
How can we measure the maturity question? It’s a bit awkward.
Last year a few people noted that it was very industry-focused. That was intentional, but how can we make these questions more approachable to, say, students? Or non-users?
Only thing I’ve got to note about the questions is Q1. Wouldn’t it be strange if people taking an Elm language survey answered “No, and I don’t intend to”? And if they did, what good would the rest of the answers be for the Elm community?
Personally, I’d like to know how people are dealing with styles. Are people using regular css, elm-css, styled-elements, etc.
That’s a good question. I knew it would raise some eyebrows! Basically, people totally just answer these surveys in the situation that they never intend to use the language but have Opinions™. I want to regard their responses differently (read: very lightly, if at all.)
I’d like to see something about automated testing; the most important being “what things/how much do you test in your Elm projects”, and if there’s room for two questions, maybe also “what tools do you use for testing your Elm projects”.
I think another useful question would be what tooling do you when developing your elm projects, with checkboxes to select from elm-test, elm-reactor, elm-server, elm-brunch, webpack, etc.
To both of you, then: what data would you hope to get out of those responses? What questions would it help us to answer? I thought of adding tooling questions but can’t think of an answer to that myself.
For styling, it’s a question I see ever now and again on slack. I think the main benefits of having a styling question in the survey are:
Promotes cool stuff like elm-css and styled-elements
If people are not using such projects, then why? Do they need more exposure, more focus in tutorials…? Or maybe people just don’t have a problem with css?
Are people comfortable using regular css, or do people prefer to skip css altogether and just focus on the higher level details.
CSS seems to be the one frontend thing where Elm hasn’t really landed yet (for me, anyway), and so it would be interesting to know more about how people are handling that part of frontend development.
I’d like to see a question like "What is the one major feature you would like to see in Elm?" Alternatively, “What do you see as the biggest missing part of Elm right now?”
For the tooling question, the hope would be to identify whether or not and how strongly people are dissatisfied by the official tools, and to identify the popular solutions so the features could be looked at to improve the official tools. Specific questions the data could answer: do people tend to use elm-reactor and if not, what do they use instead; how many people prefer alternatives to the elm-test runner. (I guess the stuff about brunch/webpack/etc are less important to me, though maybe it’s useful to know which build systems are most important to support)
The purpose for the “what do you test” question is to get a sense of the overall community’s perspective on testing, since most of the existing tools have been built based on the preferences of those who’ve built the tools.
That’s “what has been the biggest pain point in your use of Elm”. The responses from that last year sufficiently covered that facet. I bet they will again this year.
Ok, I’m really loving these questions. I think we can probably add a couple more before people drop off. I’ll see if I can work them in to the next draft.
Ok, here’s that next draft. I’ve grouped the questions and bolded the new ones.
Some specific questions:
@avh4: how useful is getting the data about elm-format? I’m inclined to leave that question in this year because I’d like to see if there’s any year-over-year change. But if you don’t think it’s intrinsically valuable, it could get dropped.
Is there any way we could make this more accessible to students / beginners?
Your Background
Do you use Elm?
Yes, at work
Yes, in side projects
Yes, as a student
I used to, but don’t any more
No, but I’m curious about it
No, and I don’t intend to
What is your level of experience with functional programming?
What programming community are you “coming from?” (changed from “what language”) (note on this question: “none” should be encouraged as a valid answer.)
Where do you go for Elm news and discussion?
What did/do you use to learn Elm? (resources, classes, et cetera?)
Is there a local Elm meetup near you?
What’s the nearest big city to you?
Where do you use Elm?
In which domains are you applying Elm?
How long have you been using Elm?
How far along is your most mature Elm project?
Considering for a future project <- not great
In the planning / learning / exploration phase
In development
In staging
Shipped / released to users / in production
Is that project at… work, side project, open source
What versions of Elm are you using?
How do you use Elm?
Do you format your code with elm-format?
What tools or frameworks do you use to style your Elm applications? (“I just write plain 'ol CSS” is an acceptable answer here!)
What tools do you use to build your Elm projects?
What tools do you use to test your Elm projects?
What do you write tests for in your Elm projects?
What do you like the most about your use of Elm?
What has been the biggest pain point in your use of Elm?
When you have to integrate with JavaScript, what’s usually the reason?
I’d be interested to know what proportion of Elm users are also professional programmers/software developers, and what proportion are casual/hobbyist programmers. I recently went to an Elm meetup and it seemed like almost everyone did some kind of programming as a day job (although not too many were using Elm at work). But maybe it’s just that hobbyists like me don’t usually go to meetups?
Well, like, “I use Elm in side projects from my regular job as a Java programmer” seems to me slightly different from “I use Elm in side projects from my regular job as a dentist/personal trainer/accountant”. I’m not sure those are really quite the same kind of Elm users or have the same experience. But maybe I am splitting hairs?
I’m interested in the demographics of Elm users. I’ve had a few people ask me recently about the gender ratio in tech, and I usually pull up the stats from the Stack Overflow Developer Survey. While web-dev is already less male-heavy than the industry as a whole, my hypothesis is that the Elm community is a bit closer to an even ratio.
