Brainstorming Session Prior to Writing Nushell Survey

Nushell Survey Preliminary

Note you have to be signed in to HackMd to edit this document. I am signing in simply by using my Github login which it does for you automagically…

Question One for everyone !

Do you think now is a good time to do a survey ?

Is doing a survey a good idea ?

So here is a scratch pad for ideas for our possible upcoming Nushell survey…

Once everyone has put their ideas down here then we can begin to work the actual survey.

This document can serve as our initial brainstorming session…

When you add to this document you can put your name and your ideas and if you think of more stuff later come back and add to the ideas.

then we can get in there and correlate later

We will probably do another HackMd document for the correlation of ideas as we narrow down the survey and make it clean, concise and short.

As and end user I was always very much "turned off" by long surveys…

JT initial notes…

Do you use Nushell?
Yes / No / Stopped using it
2. If Yes

1. I use Nushell as…
   My shell / a scripting language
2. I use Nushell: Daily / Weekly / Monthly
3. My favorite parts of Nushell are:
4. I wish Nushell did these things differently:
5. Final comments
6. If No
   1. I don't use Nushell because
7. If I stopped
   1. I stopped using Nushell because

Storm ideas…

One question I would be curious to know is whether they use nushell at work or at home ?

If they use Nushell at work how is it used ?

Also do people use Nushell in the cloud or just on work or home computers…

Also preference for terminals versus nana type user interfaces

Also question about plugins / dataframes / how do they use dataframes ?

Is dataframes something nushell users are interested to learn more about…If they are not using them.

Its been awhile since we have done a survey –– so I think we should really consider feedback from everyone in crafting a survey that is short and to the point / yet hits all of the big picture
items we want to know about

Darren

Above all, the survey questions should be actionable and a plan to implement results we agree on. It's fine to have general questions that we're just curious about but if we don't do anything with the results, it's wasting everyone's time. That's not to say that we have to implement everything people suggest but we should write a blog saying, we plan on doing x and we do not plan on doing y for these reasons. Kind of a response to the survey blog post.

It also may be a good idea to formulate the questions in such a way that they can be easily quantified and consumed by nushell in order to spit out metrics. Like instead of having answers like Rarely, Never, Sometimes, etc, have 1, 2, 3, 4, 5. Looking at the old surveys it kind of hard to quantify the results. Yes/No's should be 1, 0, again so we can just sum them up.

Row 11 from this sheet has the previous survey results
https://docs.google.com/spreadsheets/d/1XtaWyMB44DjqZSOXW37-c6qjAPMSYxAS0Laa-vd9O4o/edit?usp=sharing Row 14 has the previous reddit results.

One thing I'm interested in is knowing what OS and Terminals people use.

List of Terminals

• cmd.exe
• Windows Terminal
• Cmdr.exe
• ConEmu.EXE
• CygWin
• hyper
• iterm2
• wezterm
• alacritty
• Terminal.app
• kitty
• gnome terminal
• can someone list other popular linux terminals?
• other

We should probably have people say what version of nushell they're on.

It would be interesting to have some dataframe questions like "Do you use nushell dataframes", "Do you find it intutive(1)/i-dont-care(2)/non-intuitive(3) to use", and other dfr/lazy-dfr questions.

Maybe some Sqlite questions?

Generally speaking, this may be an opportunity to introduce new features we've added over the last year.

Do we need to have a every-thing-batteries-included release or just a core-release with minimal commands?

Storm comments

Darren's comments got me thinking a lot more about this…

I agree with what he is saying.

Survey questions should correlate with action items of work we will do…

Should we wait till post 1.0 since we already know what needs to be done prior ?

Rather than a survey (for now).

I think (maybe) ? we should do more of a "live survey"

Meaning… We should have the "Nushell quarterly discord community session…

Then the folks who really want to give us feedback can communicate those ideas to us and we can have a discussion about them.

Reilly

I'd like to see if people are getting stuck (which could require documentation or UX improvements). Something like:

Have you been unable to accomplish something in Nushell because you weren't sure how? If so, what were you unable to accomplish?