Earlier quoted context omitted.
> humans can also drive e.g. in Turin or Paris at rush hour, on mountain roads under the snow or in the Cornwalls roads while under tempest rains. I'm not sure the median human driver can do all that.
The roads in those places are full of median and below median drivers.
The end of classical Computer Science is coming
51–60 of 77 posts
Re: The end of classical Computer Science is coming
#52in 1943, Warren McCulloch and Walter Pitts created a computational model for neural networks. One approach focused on biological processes while the other focused on the application of neural networks to artificial intelligence.
The author stated that a 3 sentence passage would not be comprehensible 20 years ago, but not true. Anyone could understand what they were saying from the context.
Code that writes code, which he is essentially talking about, heck, I wrote one when I was a freshman back in 1980. Because code that writes code is what it all boils down to. Using fancy words might get someone a job promotion for using the current buzzwords, but that's just buzzwords.
Color me not impressed.
Re: The end of classical Computer Science is coming
#53> CEO and Co-Founder Fixie.ai. Okay, so this is an advertisement.
Re: The end of classical Computer Science is coming
#54Re: The end of classical Computer Science is coming
#55Earlier quoted context omitted.
Google translate: === One day in the spring, at the hour of an unprecedentedly hot sunset, two citizens appeared in Moscow, at the Patriarch's Ponds. The first of them, dressed in a summer gray pair, was short, well-fed, bald, carried his decent hat with a pie in his hand, and on his well-shaven face were glasses of supernatural size in black horn-rimmed. The second, a broad-shouldered, reddish, swirling young man in…
Machine translation isn’t for translating literature at the moment. Maybe that’s why you’re feeling it falls short. For conversational vernacular or straightforward instruction, it’s great. I can’t remember the last time I used pork-pie hat in a conversation, for instance. Perhaps you could qualify your initial statement that we can’t translate literature in a way that isn’t ugly. That would be true. But machine tran…
And this is the reason why I'm not buying "the end of classical Computer Science". AI doesn't work with text very well (reference to your comment "Machine translation works pretty well" - no, it isn't), and often can't even translate/recognize conversations. For example, auto-generated YouTube CCs often suck.
Re: The end of classical Computer Science is coming
#56"I'm not a classical style developer and that's fine because because programming is over."
"I'm a classical style developer and I'm safe because AI can never do this."
At the moment, either might be true and either might be false, and both might be merely some percent true and false at the same time.
The only real mistake is probably jumping to either assumption at this time.
Well I'm sure an argument can be made about fence sitting too so whatever.
Re: The end of classical Computer Science is coming
#57> Fast forward to today, and I am willing to bet good money that 99% of people who are writing software have almost no clue how a CPU actually works The fact that many people do not know exactly enough what they are doing can be seen in the result. The people whose goal is to write as robust and efficient software as possible still do have to know and control the details. It's like driving a car; you do not have to b…
> we are obviously still a long way from replacing humans as drivers. This is only because we as a society have an extremely low tolerance for errors in automated driving and essentially require by default superhuman performance (a self-driving car with an error rate of the median human would never be allowed to be set loose by itself). In scenarios where a 0.1% error rate, 1% error rate, or maybe even 10% error rate…
Re: The end of classical Computer Science is coming
#58Bull. At best, you'll reduce the time spent writing code at the cost of greatly increasing the time spent writing tests to give you sufficient confidence that your autogenerated code actually does what it is supposed to. And if it doesn't, good luck fixing it.
Re: The end of classical Computer Science is coming
#59Earlier quoted context omitted.
Machine translation isn’t for translating literature at the moment. Maybe that’s why you’re feeling it falls short. For conversational vernacular or straightforward instruction, it’s great. I can’t remember the last time I used pork-pie hat in a conversation, for instance. Perhaps you could qualify your initial statement that we can’t translate literature in a way that isn’t ugly. That would be true. But machine tran…
Yes, it is for trivial conversations. I could give you few more examples, technical book - you would say "ah, and it isn't for translating technical books", and so on. And this is the reason why I'm not buying "the end of classical Computer Science". AI doesn't work with text very well (reference to your comment "Machine translation works pretty well" - no, it isn't), and often can't even translate/recognize conversa…
Re: The end of classical Computer Science is coming
#60> Fast forward to today, and I am willing to bet good money that 99% of people who are writing software have almost no clue how a CPU actually works The fact that many people do not know exactly enough what they are doing can be seen in the result. The people whose goal is to write as robust and efficient software as possible still do have to know and control the details. It's like driving a car; you do not have to b…
I know exactly how a CPU works, but I can’t say I ever spend much time thinking about that while I’m writing code. Thinking about low level details is often useful, but I can’t say I sit there pondering logic gates while trying to solve programming problems very often.