debugging this kind of issue with old tools certainly could distract a learner.
For most learners, it’s not an issue at all. Not for quite some time. Because most learners don’t attempt to create their own local installations and work on the problems themselves for some time. The interface offered by DQ ensures they can focus on learning the fundamentals without having to worry about that initially.
This is not to say that they shouldn’t be doing this. They should definitely, at some point, work on a local installation. And DQ should definitely help understand how to do it and what the differences might be or what issues they might run into.
After all, this is a programming language learning platform
It’s not a programming language learning platform. Broadly speaking, it uses specific programming languages/tools/frameworks to focus on teaching fundamentals corresponding to a specific domain.
And there’s a difference between learning how to program to solve specific problems vs learning a programming language. The focus is more on the former.
Having an up to date environment for learners is business value for DataQuest.
That’s not really true in this case. What students learn from the courses is not that dependent on the environment being used right now.
If you take the code that you use based on what’s taught in their content, and then run it in your local environment with the latest versions of python and pandas, I don’t think you would face any issue that would be too complicated to handle.
You can also check the new feature releases easily -
And from the above page you can go through the previous versions and what new features they have had. Most of those features are not something that will make an impact on learners going through the courses on this website.
I have worked on some python-based projects in the past two years. And I have used different python versions for them. And over the past couple of years, there have been only two features that I have come to learn about was because people were pointing out how helpful they could potentially be. And even those two haven’t had much of an impact on the kind of projects I have worked on. I am not focusing on what happens in the industry, because that is a completely different point of discussion not applicable here.
There is a difference between what people expect to learn and what is enough to learn. And that varies depending on the scope of what we are learning.
If DQ decides to update to a version, then sure, they should. Absolutely. But it’s not something of business value. Because we are not learning how to use those features in the context of their courses. When that context changes such that there is a specific feature in a newer version of a language/tool/framework that a student/practitioner/developer should learn as it would have a direct impact on them for the better (especially for their career), then they should update their platform.