r/Python • • Jan 05 '18

Really??

Post image
2.0k Upvotes

317 comments sorted by

View all comments

83

u/Pancakepalpatine Jan 05 '18

I actually did this exact same thing.

I started with Python, but couldn't wrap my head around what it was actually doing for many of the code snippets and examples I was looking through while I was learning. On top of that, there were 23 ways to write the same expression with 16 standard library choices you could use. After a month or so of frustration, I quit programming for about a year.

Then, I tried to learn Java. The amazing thing was, there was little magical syntactical sugar (compared to Python), and so I could actually read and comprehend code. The JVM was confusing, but as an introductory language, having conventional long variable names and descriptive methods was really helpful.

I know this isn't everyone's experience, and in fact it's the opposite of many people's, but Python was way too "wishy-washy" when I was starting. Now, though, I love it.

(P.S. this was my experience based on the way I learn things, and your results may [have] differ[ed].)

(P.P.S. I learned to code back in the day with codingbat.com. If you're just getting started, it has the most basic of the basic, no-frills tutorials. Even CodeCademy or similar has a bunch of extra stuff, that may be helpful, or may not.)

-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.

2

u/Pancakepalpatine Jan 05 '18

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.

1

u/[deleted] Jan 05 '18

However, it's hard to recognize what you're learning imperfectly/incorrectly as you're learning it.

The point is that, imho, there's very little you can learn by following tutorials and using libraries.

You learn to program by solving problems through code. You need to write that code and to solve those problems.

If solving the problem is understanding some documentation of an API that solves the problem for you, you're barely solving any problem.

That's why I advocated that noobies should not use libraries.

I mean, I can see why you don't want to write a request library on your own, but that's pretty much all I'd allow to a starter.

2

u/Smallpaul Jan 05 '18

Your rule is much to broad. What about turtle graphics? What about vpython? What about Pygame.

Without libraries, all you can do is text manipulation or math. Many consider that boring.

1

u/[deleted] Jan 05 '18

That's not true. You don't do just text manipulation or math.

You compress files, convert them, and do plenty of other stuff.

What I meant is that it makes no sense to use libraries for everything when you could actually learn something to make it without them.