I always like to joke in coding interviews that I really like to make variable names as long as I can so they are very precisely named. Then when I get to a double nested loop I hit them with iterator and jiterator instead of I and j
I always like to joke in coding interviews that I really like to make variable names as long as I can so they are very precisely named. Then when I get to a double nested loop I hit them with iterator and jiterator instead of I and j
The idea is that they can’t work longer than the peasants live, so if they want to stay in power they have to help the peasants get better healthcare
To be fair he’s had the same mindset since the 50’s as well, it was just a progressive mindset that we still haven’t caught up to as a society
Is them some nipple rings in your pockets?
And even if it didn’t help my chances directly like that, even getting a small chuckle would help me be more comfortable and confident.
What do those lines even mean?
When I’m doing coding interviews I always like to start off and say I’m a big fan of very long variable names. “As descriptive as you can be” I say. Then I get to my first for loop. Instead of i I use “iterator” and then when I start a nested loop I use “jiterator” and it always gets a laugh.
My last world used 1-4 train cars on a two way rail network arranged in a grid, with train station limits and circuits controlling the station to only be on when it had the right amount of resources. (Whether that be enough resources for an output station or low enough resources in an input station) this was enough to easily handle somewhere near 700 trains traveling between around 800 stations supplying a modular factory that sustained 5.6k spm. I stopped that file due to performance restraints, the train network was capable of much more. On my new space exploration play through I think I’ll stick with the same.
What a surprising result!