Thank you to everyone who took out 2020 developer survey!
actionhero from the npm, Inc. repository more than 300,000 times! Thank you. Now it’s time to look to the future.
As the core maintainer, this survey has been very helpful to find our community’s pain-points and obtain structured feedback. 36 of you responded, and in this post, I want to analyze the survey results and discuss common themes, and share my plans for the future.
A quick note on the survey methodology & bias: The survey link was posted on the Actionhero website, NPM page, Slack Team, and Github page for ~5 weeks. There’s a strong bias in these results toward folks that already use Actionhero regularly, as they’ll be visiting those pages the most often. The survey was also only posted in English and run via Google Forms, which may have influenced the types of folks who were able to respond.
First and foremost… it seems that most Actionhero developers are satisfied! We received high marks on: "Developer Experience": 4.1/5, "Ease of Use": 4.0/5 and "Documentation": 3.3/5.
Of these 3 areas, "Documentation" is the area we need to focus on the most. This matches some of the free-form feedback received as well (more on this below).
The average Actionhero developer has been using Actionhero for over a year, and we don’t have many new users compared to "veterans".
Folks are either finding out about Actionhero via Coworkers or GitHub, but not at conferences or social media.
In the "What would you like to see from Actionhero in 2020?" free-response question a number of you wanted better examples and documentation… and hinted this might be a way to help attract and onboard new users.
The most popular plugin by far is
[ah-resque-ui](https://github.com/actionhero/ah-resque-ui) in second place. Which makes sense… folks want to to connect to the most popular databases and inspect the status of their tasks. The Task system is one of the main reasons folks are choosing Actionhero.
Many of you wanted more plugins to use in your projects. The most popular topics were:
So if you were to ask me what new features should we add to Actionhero in 2020, I would put on my best Steve Balmer voice and respond with "Plugins, Plugins, Plugins"!
I think that the core of Actionhero is in a great place now that we’ve moved to Typescript, so I don’t expect another change that drastic in 2020. I believe we should focus on adding new functionality via plugins. For example, I think we can support the Serverless Framework via a plugin as a new "Server". I think we can make deployment "packs" for most of the popular platforms (AWS, GCE, etc) to help with the environment and more… also via plugins.
Speaking of plugins, many of the free-response comments listed that how Actionhero boots was problematic, as it didn’t allow a plugin to "inject" settings, change the environment variables, or otherwise deal with something needed by the environment. Our previous
boot.js tool wasn’t enough. This early piece of feedback was already used to drive the v22 release, moving to a more developer-managed runtime.
It looks like React and Angular are tied for popularity among the folks that use Actionhero, along with Vue.
Most people don’t use Chat while Most people do use Tasks.
Actionhero is deployed in so many different ways.
Our community is almost ~50/50 on Typescript.
And finally, the majority of Actionhero users are in the USA, and speak English when developing Actionhero. Germany and the Ukraine (with their respective languages) are #2 and #3 in popularity. 🇺🇸🇩🇪🇺🇦
Putting on my Product Manager hat, here’s my priority list of what to work on, in order based on this survey:
server.ts to allow for local modifications, loading config into the env, etc. This was the core change in the v22 release of Actionhero.
[actionhero-tutorial](https://github.com/actionhero/actionhero-tutorial) project to Typescript. Done!
[ah-resque-ui](https://github.com/actionhero/ah-resque-ui) to work with v20+ of Actionhero… and perhaps include it in newly generated Actionhero projects?
I would love enable more members of the community to help with this work, so I am making an open commitment of my time to help you work on these features! I think we’ve made Actionhero easy to work on, as it uses so many of its own concepts internally, has a great test suite, and many dependancies. If you are new to programming, or new to Actionhero — I’m committing a few hours a week to help new developers learn how Actionhero works and to make it better. Let’s call these Actionhero Office Hours . Please join me on slack.actionherojs.com to choose a feature to work on, and talk about ideas!
I hope for these to be like Office Hours in a University — while we all have the same general topic (Actionhero!), it will be unstructured time to dive deep into a particular area, both with me and the other attendees. Within the first few minutes, we’ll collect the topics you come with, and divide up the time in the session between them. Hopefully I or the other attendees can help unblock you, or you might find a peer interested in the same topic to work with! After a few initial Office Hours, we can see which other times make the most sense for the community, and perhaps do 2-per-week. We can work on Pull Requests, new plugins… or even that Actionhero-centric tech talk you are working on!
The first inaugural "Actionhero Office Hours" will be between 5–6PM (USA Pacific Time) on March 4th, and then repeat every Wednesday. The google hangout URL will be posted in our slack.actionherojs.com and Twitter a few hours beforehand.
Thank you, and I look forward to seeing you at Office Hours 🎓!