My reactions to the demo (when all is good there is no reaction, so here are only the problematic ones, sorry)
1) import matplotlib.pyplot as plt
Why "as plt"?! Let the import alone. But this is a matter of style.
2) Get titanic csv data from the web [...]
Surprise, it turns out that "the web" is an URL on raw.githubusercontent.com Hopefully I'll be able to spell an URL of my choice
3) clean records from titanic data where age is null
Somehow I already know that there is an Age field and somehow it knows that it must capitalize age into Age
4) fill null values of column Fare with average column values
The generated code looks great but somehow I managed to spell a capitalized Fare this time :-) (this is probably a typo in the demo)
5) Hey,Github! New line
Inserting a new line can't take so many words. We're going to do without new lines or rely on a formatter or something equivalent.
6) plot line graph of age vs fare column
This is where it becomes evident that there was no need to import as plt because I'm not pressing those keys anyway. But this is style and it's going to be uniform across all the users of these tools.
7) Hey, Github! Run program
Good.
Considerations:
A) Why do commands (new line, run) need "Hey, Github!" which is pretty long and terrible to repeat all the day long (just imagine having to say Hey Joe every time we have to say a sentence to Joe, withing a long conversation with Joe) and text-to-code doesn't?
B) We got a graph at the end. Now what should I do to edit the code in those 99% of cases where I got the graph wrong? An acceptable answer could be mouse and keyboard. It's a little underwhelming but voice to code already gave me the structure of the code.
C) Does that mean that Microsoft and GitHub are going to know all the closed source code we'll write for our customers (there might be contractual implications) or is this something that will be self hosted in our machines?
1) import matplotlib.pyplot as plt
Why "as plt"?! Let the import alone. But this is a matter of style.
2) Get titanic csv data from the web [...]
Surprise, it turns out that "the web" is an URL on raw.githubusercontent.com Hopefully I'll be able to spell an URL of my choice
3) clean records from titanic data where age is null
Somehow I already know that there is an Age field and somehow it knows that it must capitalize age into Age
4) fill null values of column Fare with average column values
The generated code looks great but somehow I managed to spell a capitalized Fare this time :-) (this is probably a typo in the demo)
5) Hey,Github! New line
Inserting a new line can't take so many words. We're going to do without new lines or rely on a formatter or something equivalent.
6) plot line graph of age vs fare column
This is where it becomes evident that there was no need to import as plt because I'm not pressing those keys anyway. But this is style and it's going to be uniform across all the users of these tools.
7) Hey, Github! Run program
Good.
Considerations:
A) Why do commands (new line, run) need "Hey, Github!" which is pretty long and terrible to repeat all the day long (just imagine having to say Hey Joe every time we have to say a sentence to Joe, withing a long conversation with Joe) and text-to-code doesn't?
B) We got a graph at the end. Now what should I do to edit the code in those 99% of cases where I got the graph wrong? An acceptable answer could be mouse and keyboard. It's a little underwhelming but voice to code already gave me the structure of the code.
C) Does that mean that Microsoft and GitHub are going to know all the closed source code we'll write for our customers (there might be contractual implications) or is this something that will be self hosted in our machines?