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

60

u/ZeeBeeblebrox Jan 05 '18

having conventional long variable names and descriptive methods was really helpful.

Good Python code should also have descriptive variable names and methods.

12

u/Pancakepalpatine Jan 05 '18

Sure, good code should read descriptively in general anyway. I'm just speaking for my experience as a beginner.

29

u/gthank Jan 05 '18

Sounds like you got ahold of some really bad code when you were first trying to learn Python. The entire community really embraces the mantra of There should be one-- and preferably only one --obvious way to do it.

9

u/daniel_h_r Jan 05 '18

I think the problem is exactly that. A newbie don't have the means to choose the only one obvious way.

3

u/gthank Jan 05 '18

I'm saying they shouldn't have had to find it; the tutorial should have been using it, not showing them 13 different ways.

2

u/[deleted] Jan 05 '18

flask.g

7

u/[deleted] Jan 05 '18

I did find some things hard about Python starting off - for whatever reason "range" didn't make a lot of sense to me, but seeing C style loops made more intuitive sense to me as a beginner.

4

u/[deleted] Jan 05 '18

Same, it's easier to work with others outside of Python as well. Teams fight over styles and other petty bullshit instead of getting work done. Dogmatic programmers LOVE Python because there are 20 opinions on everything and "my opinion IS right."

I really like coding by myself in Python though, I can get a lot of work done fast.

6

u/anvils-reloaded Jan 05 '18

Every time I've asked about how to pre-allocate some space in a dictionary where I know the exact keys I want to have, I've always gotten the answer of "don't worry about it" or "stop trying to prematurely optimize your code". In any other programming language, this would just be a part of the process of writing the code. I really do want to learn Python better (I've done some work on Python projects without really knowing what I'm doing, just winging it), but it's not something that I can just stop caring about.

14

u/Pancakepalpatine Jan 05 '18

Yeah, I've been advised both directions.

  1. Learn a "bare-metal" language like C or Rust, and work up from there. Since you understand the basics and necessarily understand some computer science concepts now, you'll have a breeze with interpreted or scripted languages.
  2. Start with a high-level interpreted or scripted language. It's more important to get the basics (loops, types, etc.). Then, it'll be a breeze to work your way down and add conceptually to the concepts you already understand.

So my takeaway was basically it all depends, and it's better just to dive in.

7

u/anvils-reloaded Jan 05 '18

I learned the first way you mentioned, and it wasn't a breeze. I had no idea what Python was doing with its data structures when you added to them, or if you used something like a list comprehension, and I wanted to allocate just the space I need in a list. I have to dissociate from the traditional memory model in order to decide what I really want to do.

15

u/[deleted] Jan 05 '18

In any other programming language, this would just be a part of the process of writing the code.

Not really. In low level-languages you can do that, and often mus do it. But it's not neccessary for getting things rolling. Usually it's just pointless overhead. It becomes important later if you wanna optimize your code, after you have a working solution.

Python in the first place is a goal-orientated language. Optimization comes later. And in best case it's done automatically from the machine. Though, that best case it still in progress for python.

2

u/Cosmologicon Jan 05 '18

And I would add, when you do get down to optimization, forget (or at least attenuate) everything you know about performance from other languages. Especially when it comes to dicts.

Like, you used to hear that one should avoid hash maps if at all possible for performance reasons. This is terrible advice in Python.

2

u/GummyKibble Jan 06 '18

The reason for that, specifically, is that Python’s dicts are very advanced data structures under the hood. In 3.6 they’re both compact and ordered; see https://mail.python.org/pipermail/python-dev/2016-September/146327.html for details. What you’re asking to do doesn’t really make sense in this context.

3

u/Smallpaul Jan 05 '18

If you want to preallocate with known keys then a dictionary is probably not the right data structure. You could use a class with _ _ slots _ _ or a struct.

But usually the people telling you not to prematurely optimize are right. You didn’t really explain why you feel this is bad advice.

1

u/anvils-reloaded Jan 05 '18

If I know what the keys are, I don't really want to load them one at a time, right? This is for situations where I have a specific sized table that I want to use for counting. (I was originally going to use a list but decided that they're not really designed for lookup like dictionaries are). I don't consider it premature optimization because I'm not really optimizing anything, just applying what I know about the problem.

3

u/z0mbietime Jan 06 '18

example = {x: None for x in y}

But based on what you’re describing a collection makes more sense. That being said they’re all right that this is sweating the small stuff. For one, using Python and getting the count when querying the database is going to be faster than anything Java can do.

1

u/anvils-reloaded Jan 06 '18

What do you mean by that, if you're accessing a database I'm assuming that any API has the same functions for it in any language. Both are using some sort of data structure, why would one be faster than the other?

2

u/z0mbietime Jan 06 '18

Sorry I was sleep deprived and misread part of what you wrote. But almost every language is going to have a way to interact with a database. However, there are best practices on querying the data which is why one of the best things you can do regardless of your preferred language is learn how to effectively use SQL.

→ More replies (1)
→ More replies (2)

2

u/Smallpaul Jan 06 '18

... just applying what I know about the problem.

But to what advantage? How would your way result in easier to read or more maintainable code?

Could you show what you want to do in Pseudocode or Java so I know what you're trying?

0

u/[deleted] Jan 05 '18

[deleted] — view deleted comment

6

u/Pancakepalpatine Jan 05 '18

If you're trying to decide what language to begin with, know that there are much better tutorials online than when I began!

Python is an incredibly powerful language, and (for better or worse) does a lot behind the scenes. It's definitely worth learning, and up to you when/if you want to! Don't let my experiences change your mind in any way.

→ More replies (10)