ncds42's comments

Your last comment is, frankly, complete bullshit.

People have already created TAS programs that can take out infinite numbers of enemies with minimal stock (ex: medvac/tank vs. infinite ultralisks). Or have zerglings that perfect 1 siege blast per 1 zergling splitting.

As far as micro, AI already has proven capability to absolutely dominate human micro, like not even close.

As far as build paths and macro decisions, AI isn't there yet but all it takes is one player and one programmer to come up with an in-the-middle and well-rounded build path that doesn't lose to any cheese; Sacrifice some economy to just have an army at all times_ and the AI will micro dominate the rest in extremely, humanly impossible army trades (I mean winning a 40 stock vs. 200 stock army battle).

Honestly just imagine having ONE mutalisk perfectly micro all-game, never receive death damage that just outputs as much damage as humanly possible at every angle. And you could have all 20-140 of your army stock doing this at all points in the game.

No contest. Just hasn't had time devoted to it yet.

Unless there are in-depth APM limitations on the AI, there's no contest for AI vs. A human.

Using C as an example is a straw man. There's been A LOT of progress since C. Can you say the same for Java or Python? Not as much.

He didn't condemn Kotlin and swift. He is saying that they aren't necessary and don't solve the original problem. That the constant search for a new framework or of language that will fix everything is a futile attempt to avoid learning how to more effectively code with the tools you already have.

Bad software has done worse things than release private info. Just a few worse things: failed space missions and cost NASA credibility, killed hospital patients, bankrupt Knight Capital, almost caused World War III due to a false-positive nuclear-launch warning, caused wide-spread blackouts, killed people (lookup Patriot Missile).

We as developers are just waiting for something so terrible to happen that someone is forced to take notice.

Uncle Bob's true value to me was to teach me how bad of shape the software world really is in. Look at any engineering discipline. There are standards, there's a rigorous design process, there's checks from more experienced engineers, there are best practices, etc. Software is like the wild west, and if people don't realize that and try to create some sort of standard than eventually someone with no knowledge of the field will. He's trying to encourage people to understand the problem and think towards creating rules so everyone can perform and collaborate better. Eventually software will become like other more established fields but it's up to our generations to take us there.