I think removing unnecessary code and generalizing redundant parts should be a given. On the other hand, early optimizations such as caching or in-lining should be avoided unless needed.

Plain old JSON, with types defined.

Way too slow even at moderate scale.

Slow humans is not as much a bottleneck in Dota as it is in Starcraft. It's easier to "brute force" Starcraft by sheer APM, which is easy for AI to do.

Nobody would find that interesting though. Just like the Dota not, and Deep Mind's Quake bot, accuracy and APM would of course be capped to human levels.

Because investing has become integral in personal finance and market cap gives an estimate of a company's value, room to grow, etc.

I appreciate how you state that investing has become an internal part of personal finance. I agree with you, but unfortunately nobody taught us this where I am from.

Same for me, other than tidbits I got from my parents occasionally. Like many of the important things I learned in life, I had to teach myself.

But for investing the market cap is irrelevant, the stock price development is relevant, dividends are relevant, interests are relevant. There are a lot more indicators which are more relevant if you want to invest in a company or not than the market cap.

I disagree. Look at the airplane, it's clearly made in 3D software.

Very possibly. But that would be easily reproducible with layers as well.

Look how there is no perspective change on the rising blocks and the shadow underneath. Blocks just move straight up and down and shadow just increases/decreases in size.

People movements are just tween animations.

Its an orthographic rendering, that's why there are no perspective shifts.

So, like certifications? Last I heard those are frowned upon in our industry.

Only because they are too easy, or for profit, or focused on using a given product or unimportant concepts.

Avoids the extra step of hashing the object to make the key by simply passing the object itself.

I read these two as well. Computer Organization and Design and Computer Architecture on my 2nd and 3rd-level computer architecture courses respectively. Glad to hear Hennessy and Patterson getting the Touring award, always had a good hunch about Computer Architecture despite not knowing as much back then.

That's a very black and white point of view. There's lots of grey areas and varying urgencies for problems. I'm sure most respectable programmers would take care of matters as fast as they could, even if it isn't that urgent.

If it takes me an hour to take systems back up after things go bad during the after-hours, it's not because I was purposely not doing my work. It's because that's literally what took me to fix the problem.

Programmers aren't magicians and we certainly aren't out there to get you and waste your time on purpose.

Tangent

--------

>Programmers aren't magicians

All right, so this part is tangential but after I posted my (GP) comment I realized that in one sense programmers are magicians. I had left the following aspect out of my black-and-white comment:

(I hadn't considered that) some of the best programmers I know don't REALLY read every word, the way you read my comment or I read yours. There's just no way there's enough time, given the speed of use of totally new information in totally new documentation that I've seen. It would be inhuman if they really read every word.

I think they must skim and scroll and use magical ways of picking out just what they need.

So when someone links a 500-page specification and tells you to "read it" (which might take, say, two weeks of an hour a day to read, starting at the first word and ending on the last -- perhaps they legitimately expect you to "read" it in 1 minute 48 seconds, since that's how long it takes to "read" it.

Back on topic

---------------

You've directed most of your response to how long it takes to do something. But I had actually directed my comment at how long, when designing (documentation/installation/whatever) you expect people to spend doing something.

With the tangent I just added, I realize that perhaps some of it is misleading. If you direct someone to do something that takes 15 hours, that doesn't mean you don't expect them to be done within 3-10 minutes. Because programmers have magical abilities at times.

So it is far from as certain as I had said.

Used to feel that way until I got a high-power blender (Vitamix, Blendtec, Ninja, etc) and a juicer. It's very easy to make vegetable soups with a blender. I still eat meat though.