One of the examples in the Listening book for my level 1B (little to no English) class was "Take these cans of Soylent Green to the cafeteria at [address]."
Why don't we pay people to pick cotton? We had enslaved black people picking it, then indentured servants, now uzbeks. Why not just pay these people? Even less than minimum wage?
I've been backing up some video's onto dvd's since my backup drive is pretty full and the fact that I can fit a whole season of Game of Thrones in 720p onto one dvd really makes me question Blu-Ray even more; Its especially interesting since many Blu-Ray players can read data discs/flash drives. I know 1080p is better, but unless I had them side by side I doubt I could tell much difference. And yes I know about compression and whatnot, its just a thought.
I've just realized that this is my most reading intense school year yet. I've been assigned 18 books, and still have two to go in as many months, and I've read as many of those as I've read in my last four years at Latin school -- assigned or otherwise.
English 11, reachback English, Ms. KP's US history, ms KP's American Foreign Policy. I should note that this doesn't count the legendarily large packets she gives us.
Today's discovery of someone else's programming fail: 1. Creates a list object 2. Names it queue 3. Uses it as a stack *Sigh* We all got a good laugh out of that in the office. Reading mobile game developer's code is occasionally enlightening, but often just hilarious.
Hey, a list is a perfectly reasonable implementation of a stack. A stack is also basically just a LIFO queue. Maybe I need more details here, but I don't see what's wrong based on your description.
But a stack is a LIFO queue (the two terms are synonymous), though I'm being pedantic here. Most people generally assume a plain-old queue is a FIFO queue, so I can understand why there may be some ambiguity there.
Out of curiosity, do you know if English is this particular programmer's first language? Maybe they called it a queue, thinking in terms of a LIFO queue, because the more common English term "stack" didn't come to mind?
Naming conventions are important, especially when other people are trying to understand your code. People who have taught themselves programming and so don't stick to conventions make life harder for everyone working with them.
This was just in either C# of Javascript, so it just seems like a lack of understanding of naming conventions. Also, if they want stack functionality, the thing they want isn't a queue. A queue implies first-in, first-out mentality, stack implies first-in, last-out mentality. It's not rocket science.
Comments
Now when mentioning Rock, paper, scissors this should also be included for a joke.
1. Creates a list object
2. Names it queue
3. Uses it as a stack
*Sigh*
We all got a good laugh out of that in the office. Reading mobile game developer's code is occasionally enlightening, but often just hilarious.
Out of curiosity, do you know if English is this particular programmer's first language? Maybe they called it a queue, thinking in terms of a LIFO queue, because the more common English term "stack" didn't come to mind?