News, Manuals, etc. I read online.....no need for books when I'm looking for shorter informative articles. Books, however, I'll read fiction.

When I was learning recursion (eons ago, it seems), I was informed that both head and tail recursion could be "unrolled" to a loop of some sort (for, while, do....while, do...until, etc.) And recursion imparts a lot of overhead (push to stack, context switch, process, pop from stack), so you should unroll recursive functions as often as possible.

So, in this example, I don't think most people would think to use recursion at all --- head, tail, or mid recursion.

I would be more inclined to believe that if it were "developers", the screen would be too wide, not too narrow. Developers usually have multiple super hi-res, large monitors and would be more likely to not view it at "normal" resolutions during their unit testing.

It's less of an issue of recreating all of the "basic" controls and more a factor of every single designer wants to style buttons differently. You either buy into the native aesthetics or you don't complain when you don't have a native experience.

It may be the second or third most spoken IRL, but in terms of off-shoring, most of the jobs go to places that speak English (India), Chinese (China), Russian (Russia), and Portuguese (Brazil). So, knowing Spanish or French isn't as useful *in his profession*.

Nope.....that's how you know it's true.

PII should be classified based on sensitivity. At a certain level, that PII must be encrypted during transit. At the highest level, it must be encrypted during transit and at rest. SSN falls in the highest sensitivity level. SOP for years. This doesn't guarantee you won't get hacked, but it reduces / minimizes the impact if you are hacked.

PII - Personally Identifiable Information
SSN - Social Security Number
SOP - Standard Operating Procedure

(per the video description) From Los Angeles, you'd next see it in 2023. Which to me means that it isn't as rare as implied (unless it's like primes where there are some close ones and some far ones and the next next one would be hundreds of years later).

I did.....mostly because I probably won't watch it live. While neat from a rarity stance, it doesn't have much scientific relevance that I can think of. Cool, but the video is good enough for me.

I'd argue C# and then Java because the non-programming pieces are "pointy-clicky, draggy-droppy". Running your web based code in IIS doesn't take a lot of knowledge about how to get IIS up and running --- whereas trying to do the same with something like tomcat is a pain for someone who is already struggling to learn programming. [Plus, Visual Studio is a very developer-friendly IDE.]

Basically, remove all of the pain points so that they can focus on learning to code....... (for those of you who argue the using Microsoft products is enough of a pain point, it's easier for a noob than learning Linux because of the aforementioned pointy-clicky, draggy-droppy approach.....)

I think Javascript is a good choice in terms of barrier to entry and examples available online. The only thing I dislike is that it is a dynamic language -- and I think that people learning to program need a very structured language as they are learning (protect them from their ignorance).

I was the kid that would do extraneous proofs in Geometry just so I could use those theorems later on in the test.

My (limited understanding) is no.....but fewer of them "clog the pipe" and make it to the other end (lower resistance values).

I disagree with your coder lock-in statement. But I agree with your "throw a dart" metaphor.

Just because you CAN code an algorithm in a language doesn't mean it's the best option. Just because I can drive a screw into a 2x4 with the heel of my shoe doesn't mean I should.

Languages are developed to make certain problem domains easier. If they are flexible enough, people will adopt them for other problem domains as well. If they aren't flexible enough, they might stick around in their problem domain, but they'll stay on the outskirts. That's it.

Very true. For "the common man" to know what direction to take, too many choices can be bad......especially when there is more similarity than differences and not enough experience to know which differences will be important to them in the future.