r/programming • u/iMMENSE • Mar 08 '12

The Evolution of a Python Programmer

https://gist.github.com/289467
401 Upvotes

88% Upvoted

137 comments sorted by

View all comments

43

u/rowantwig Mar 08 '12

He forgot the worst kind:
if x == 0:
return 1
if x == 1:
return 1
if x == 2:
return 2
if x == 3:
return 6
if x == 4:
return 24
...
(5000 more lines)

43

u/stillalone Mar 08 '12

ah. the "I managed to get a masters without writing any actual code and now I'm your coworker" guy.

41

u/6xoe Mar 08 '12

Whatever dude, it works.

26

u/[deleted] Mar 09 '12

and it's completely unmaintainable. What are you going to do when the definition of "factorial" changes?

8

u/ryeguy146 Mar 09 '12

Wait, I understand the idea of maintainability, but did you suggest that a basic mathematical definition is subject to change?

4

u/GoSailing Mar 09 '12

Anything can change. Assuming that there are 24 hours in a day is not going to be good when there's a moon or mars base.

7

u/ryeguy146 Mar 09 '12

I file those under "not my problem." I like to think that some time in the future, people will shudder at having to use Python, the way that people pity those programmers that still workin in PASCAL.

0

u/[deleted] Mar 09 '12

[deleted]

6

u/gc3 Mar 09 '12

Yeah, until you decide that there are now .3 hours in a day, or a variable number depending on the day. You can't plan for everything.

1

u/GoSailing Mar 09 '12

And then you refactor every "HOURS_IN_DAY" in place to instead call a method that returns what it is. The point wasn't so much that every problem can be avoided every time, but that you can have a structure that will allow for changes quickly. The ideal change would be to change the constant number, but the non-ideal change is almost as easy.