-
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
Feedback Dec 2024 - all sessions #58
Comments
We should in the beginning say something about Python not being built around dataset (like R and especially Stata) as it is a general programming language. So before we can talk about data sets we will have to cover some of the basics before it will make sense how one interact with a dataset in Python. We can frame it as the biggest benefit of learning Python is related to the biggest challenge when coming from R and Stata is that Python is general purpose. This makes it very powerful, but one need to think slightly different about it when starting to use it. |
We should also say that since Python is open source and general, there are many contexts where we can run Python code. We should say that notebooks tend to work very similarly in Colab, Jupyter Notebooks and Databricks. But there are other ways to run code such as scripts. And we should stick to notebooks when answering to not make the intro to python more complex than it already is for someone coming from Stata or R |
A participant was confused by |
We should not include in |
Consider updating the negative index example to something more practically useful, like |
consider moving f string and |
Session 2: include examples of if conditions with parentheses to show it's possible to group them |
task 8 should go before because it's an easier exercise than task 7 |
A participant pointed out: Task 2 and Task 10 are practically the same? |
general comment: we might want to reconsider if we want to give people time to try exercises/tasks on their own. I noticed a slight dropout in participants connected and a few in the room left while we were waiting. This is a good method for the most engaged to participate, but I think some are just not going to try the exercises and will become uninterested. My sense is it produces a trade off between attendance and learning, we need to decide which we want to prioritize |
Session 3: "converting data types" section code should be better formated:
Above crosstab: "Note the resulting DataFrame cars_monthly_pivoted has make as its row index, and year its column names." make & year should be formatted as code crosstab: "The Same can be achieve with the pd.crosstab function, but with different arguments:" Same should be lowercased "groupby": existing code results in a warning "exercise 3.3.6" step 4, instead of |
Session 3: we should consider changing the name to only "Pandas" given that we're not covering NumPy anymore |
session 3: Databricks was asking to install |
There's still the python library part though... |
libraries and Pandas maybe then? |
Let's use one issue for all sessions as we do not tend to have that much feedback anymore
The text was updated successfully, but these errors were encountered: