I can see few issues in the way you learned Python.
a) Relying on standard libraries rather than implementing your own logic. That's a problem I see in many programmers. They don't program, they bundle together code written by other people with a low amount of their own logic. They end up learning very little.
b) What you call syntactical sugar is the object oriented design of the entire language. JavaScript has the same problem, arguably squared because it's a prototype-based language.
Sure! The way I learned definitely wasn't perfect.
However, it's hard to recognize what you're learning imperfectly/incorrectly as you're learning it.
I personally think with a good enough guide/tutor you can start with any language (maybe even assembly :)). Five years ago, though, with the tutorial I was using and the starting place I found myself at, Python was not a good fit. That's not everyone's experience, but it was mine.
That's why I advocated that noobies should not use libraries.
To what end, though? Should they write their own ODBC connectors? Should they write their own OS libs? Time libraries? Their own JSON parser (actually this would probably be a really good project for a beginner to learn...)?
Standard libraries are most of what makes up any given programming language and is much of what makes up the "knowledge" of a language.
-2
u/[deleted] Jan 05 '18
I can see few issues in the way you learned Python.
a) Relying on standard libraries rather than implementing your own logic. That's a problem I see in many programmers. They don't program, they bundle together code written by other people with a low amount of their own logic. They end up learning very little.
b) What you call syntactical sugar is the object oriented design of the entire language. JavaScript has the same problem, arguably squared because it's a prototype-based language.