Live data from Hacker News

What a Programmer Sees When He Watches Inception

latestatic.com

31–40 of 78 posts

Re: What a Programmer Sees When He Watches Inception

#31
post #27

Earlier quoted context omitted.

"He" is a common vernacular; get off your soapbox.

Question: When you read the title, did you imagine the article was by a female author?

The sex of an author who's article I'm reading has never crossed my mind. Who gives a crap if they're male/female? They're an author, they should be treated as such.

Re: What a Programmer Sees When He Watches Inception

#32

Can someone explain why the zero g scenes didn't cascade down through each dream level? They were feeling forces in the first dream in the van and those would go to the hotel but those sleeping there would not feel the same forces (eg lack of gravity) the next level down. I did really love the idea behind the totem though, very clever.

The totem reminded me of passing a reference down a series of recursive calls. Hehe.

Re: What a Programmer Sees When He Watches Inception

#33
I found the movie didn't make a whole lot of sense at times. It felt like the writer cut a lot of corners when it came to the whole logical coherency of the plot. Maybe if we blow something up they won't notice!

The plot was entertaining and a good idea, but it left a lot to be desired. It's not destined to become a classic like: Fight Club, 12 Monkeys, Requiem for a Dream, Primer. If you enjoyed Inception, do yourself a favor and check those out if you haven't seen them.

Re: What a Programmer Sees When He Watches Inception

#34
Furthermore, ... I thought it was interesting the movie only went down 4 levels. I have a rule of thumb when working on hierarchical structures (like a directory tree holding lots of data) that three levels of hierarchy is all a person can hold in their head at a time. This is sort of the like the 7 items +/- 2, except I think that the seven items rule only applies "across" a structure. To understand more than three levels deep requires supplementary structures like indexing, sorting, or nesting ...

(of nesting (of nesting (...)))

Re: What a Programmer Sees When He Watches Inception

#35

Can someone explain why the zero g scenes didn't cascade down through each dream level? They were feeling forces in the first dream in the van and those would go to the hotel but those sleeping there would not feel the same forces (eg lack of gravity) the next level down. I did really love the idea behind the totem though, very clever.

There are a lot of inconsistencies and you just noticed another one but it's still a really good movie because the inconsistencies are all subtle enough that you are willing to overlook them when you are watching the movie.

Re: What a Programmer Sees When He Watches Inception

#36
post #33

I found the movie didn't make a whole lot of sense at times. It felt like the writer cut a lot of corners when it came to the whole logical coherency of the plot. Maybe if we blow something up they won't notice! The plot was entertaining and a good idea, but it left a lot to be desired. It's not destined to become a classic like: Fight Club, 12 Monkeys, Requiem for a Dream, Primer. If you enjoyed Inception, do yourse…

+1 for Primer.

Re: What a Programmer Sees When He Watches Inception

#37

Furthermore, ... I thought it was interesting the movie only went down 4 levels. I have a rule of thumb when working on hierarchical structures (like a directory tree holding lots of data) that three levels of hierarchy is all a person can hold in their head at a time. This is sort of the like the 7 items +/- 2, except I think that the seven items rule only applies "across" a structure. To understand more than three…

When they added the 4th level, I explicitly thought to myself "Oh, this is an effort by the filmmaker to pull us out of logical thought by making it too much to organize in our heads in real time."

Re: What a Programmer Sees When He Watches Inception

#38

Can someone explain why the zero g scenes didn't cascade down through each dream level? They were feeling forces in the first dream in the van and those would go to the hotel but those sleeping there would not feel the same forces (eg lack of gravity) the next level down. I did really love the idea behind the totem though, very clever.

Why doesn't the totem work if someone else touches it, though?

Re: What a Programmer Sees When He Watches Inception

#39
post #27

Earlier quoted context omitted.

Question: When you read the title, did you imagine the article was by a female author?

The sex of an author who's article I'm reading has never crossed my mind. Who gives a crap if they're male/female? They're an author, they should be treated as such.

If your not considering the sex, race, or age of an author then you are not considering all aspects of the article especially when the article is an opinion piece. We already know that the sexes think different, maturity matters and the races have different perspectives so why ignore a pertinent bit of information?

Re: What a Programmer Sees When He Watches Inception

#40
post #38

Can someone explain why the zero g scenes didn't cascade down through each dream level? They were feeling forces in the first dream in the van and those would go to the hotel but those sleeping there would not feel the same forces (eg lack of gravity) the next level down. I did really love the idea behind the totem though, very clever.

Why doesn't the totem work if someone else touches it, though?

The point of the totem is that only you know how it behaves, and how it feels and how it's weight is distributed.

If someone else has held and seen your totem, they can possible recreate it exactly in a dream. If they can recreate it then they can trick you into thinking you aren't dreaming when you actually are.

Post reply on HN