Young engineer, too. Just hadn't taken a programming class, ever. He had the software record a macro of what he wanted to do, and just copypasta'd that 1000 times.

I felt bad asking him how long that took (days) and then showing him that the loop to do it took 15 minutes to write and test.


Now, given that evolution has done the hard part, I suspect we will get artificial brains much faster.

Back when I was doing support instead of development, one of my duties was to help users with their macros (within reason). One of my more memorable calls was the guy whose macro wouldn't run. Compiled fine, just wouldn't run. So I had him send it to me. When I got it, it was (IIRC) something like a single method with 60K lines of code. The JVM took one look at that Noped right out of there. Upon further examination, it was the same 40 or 50 lines, over and over, with CAD part name assignments.

Customer got a primer on the concept of 'Loops'.

And the human brain uses something like 20W a day.

ThTh7: It's not that complicated, you just have to understand what a standing shock is. Predicting when they will form isn't even that complicated.

Predicting WHERE they will form can be... complicated. And designing your aero surfaces to cause them to form in a specific location will keep your computing cluster humming along for days, even weeks.