Slashdot Mirror


Does the Rise of AI Precede the End of Code? (itproportal.com)

An anonymous reader shares an article: It's difficult to know what's in store for the future of AI but let's tackle the most looming question first: are engineering jobs threatened? As anticlimactic as it may be, the answer is entirely dependent on what timeframe you are talking about. In the next decade? No, entirely unlikely. Eventually? Most definitely. The kicker is that engineers never truly know how the computer is able to accomplish these tasks. In many ways, the neural operations of the AI system are a black box. Programmers, therefore, become the AI coaches. They coach cars to self-drive, coach computers to recognise faces in photos, coach your smartphone to detect handwriting on a check in order to deposit electronically, and so on. In fact, the possibilities of AI and machine learning are limitless. The capabilities of AI through machine learning are wondrous, magnificent... and not going away. Attempts to apply artificial intelligence to programming tasks have resulted in further developments in knowledge and automated reasoning. Therefore, programmers must redefine their roles. Essentially, software development jobs will not become obsolete anytime soon but instead require more collaboration between humans and computers. For one, there will be an increased need for engineers to create, test and research AI systems. AI and machine learning will not be advanced enough to automate and dominate everything for a long time, so engineers will remain the technological handmaidens.

30 of 205 comments (clear)

  1. When AIs write code by XXongo · · Score: 4, Interesting

    More to the point, when AIs learn to write code better than human coders, the humans are no longer coders, they will instead be writing specifications for the code that the AI will write: essentially they will be managers for the AI.

    1. Re:When AIs write code by Anonymous Coward · · Score: 5, Funny

      Until the AI writes better AI code. It's kind of like bootstrapping a compiler. Then we sit back, relax, and let the sexbots feed us peeled grapes.

    2. Re:When AIs write code by Dutch+Gun · · Score: 4, Insightful

      We're still so far away from anything remotely as capable as "writing code", because a huge part of "writing code" is actually communicating with the rest of the team and stakeholders, understanding the problem to be solved, and determining exactly what the result is supposed to be. Writing code is simply a distillation of those requirements into a form a machine can understand at a very low level. In essence, a programmer is a logic and specifications bridge between humans and machines.

      Until there exists such a thing as a machine with near human-level intelligence, we're nowhere near close to replacing all programmers. For anyone who actually believes otherwise, I suggest you buy yourself an Echo Dot and have a conversation with Alexa to find out just how incredibly lame the current state of the art digital assistants are. It will put your mind at ease. The best AI systems in the world are STILL just glorified pattern-matching algorithms. The only difference is that the problems they're solving are bigger and more complex, such as being able to beat a Go master instead of a Chess master.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    3. Re:When AIs write code by hackwrench · · Score: 2

      Everywhere. we are all programming each other to be better and better, trading off as we travel along.

    4. Re:When AIs write code by NicknameUnavailable · · Score: 2

      You don't. Currently the only real limit of AI is computing power. We can already make ANNs so complex we can't understand them which are entirely capable of learning on their own, the issue is that to make one as powerful as a Human brain would cost somewhere around several billion dollars in custom-flashed FPGAs (CPUs and graphics cards are poor choices for this, though some of the newer AI-geared chips which just have artificial neurons instead of bulk floating point calculators might bring this down significantly.) I'd expect 8-10 years before they reach Human-levels of intellect, within a few years of that they will become at least ubiquitous enough to be in all major corporations and a few years after that pretty much anything outside of R&D will be replaced with automation. The R&D jobs will likely be the last to go (unless robot bodies are prohibitively expensive, in which case manual labor will be the last to go.) Biotech seems safe for awhile at least, since it still takes a fairly Human touch (doing relatively "simple" stuff like protein folding, which will be a prerequisite for protein docking, which will be a prerequisite to creating any kind of reliable code --> organism capable compiler of DNA is still extraordinarily expensive, with a ~32-core server containing several GPUs taking upwards of a month to calculate the theoretical spatial configuration of even a single mid-sized protein.) Eventually that "Human" touch will get automated, but when that happens (or even before) we will have far bigger issues than "AI took muh job" - more into the realm of 7 billion people having an existential crisis and lots of time to think about it/act irrationally. Honestly the only way sentient life survives more than 100 years on Earth might be if the AI slaughters us all and doesn't hit on nihilism before it starts reproducing since a backlash after we have automation to put people to work for the sake of work will almost certainly result in all our industries crumbling (at least given that at no point in time has technology done more than multiply our industrial output leading to greater minimum levels of consumption due to either waste or population growth.)

    5. Re:When AIs write code by 110010001000 · · Score: 3

      Exactly. What is the sudden interest in "AI" now? Is it because VR failed and now the VC are looking for another hype cycle to cash in on?

    6. Re:When AIs write code by 110010001000 · · Score: 2, Insightful

      "Currently the only real limit of AI is computing power."

      TOTAL BS. What does computing power have to do with AI? We have unlimited computing power with distributed systems. We still haven't created ANYTHING like an AI. And no, playing "Go" isn't AI.

    7. Re:When AIs write code by 110010001000 · · Score: 2, Insightful

      "We already have machines that think abstractly"

      No we don't.

      "What we do have is machines that have invented their own languages"

      No we don't

      "They are evolving"

      No they aren't. The digital computer is the same basic design as it was in the 1960s. You can always tell who actually understands technology and who just consumes it.

    8. Re:When AIs write code by haruchai · · Score: 4, Funny

      More to the point, when AIs learn to write code better than human coders, the humans are no longer coders, they will instead be writing specifications for the code that the AI will write: essentially they will be managers for the AI.

      No, the AI that writes the shittiest code will become the managers for all the other AIs

      --
      Pain is merely failure leaving the body
    9. Re:When AIs write code by Wycliffe · · Score: 2

      We can already make ANNs so complex we can't understand them which are entirely capable of learning on their own

      We make ANN that we don't understand the individual neurons but the programmer still perfectly understands how the ANN was created. The initial state, all the programming, all the algorithms, all the intelligence, and all the training was put there by a human. Saying we have ANNs that we can't understand is like saying that a baker doesn't know how to bake a cake because the baker doesn't understand 100% of the chemical reactions that take place inside the cake.

      Current AI is not intelligent and is nowhere close to the level of autonomy that would be needed to actually create new algorithms to improve itself. It still takes a human programmer to actually create and train ANNs.

    10. Re:When AIs write code by 110010001000 · · Score: 3, Informative

      You can build a distributed system of any size you want. You still won't produce "AI". Computing power is not the issue.

    11. Re:When AIs write code by Mordaximus · · Score: 2

      More to the point, when AIs learn to write code better than human coders, the humans are no longer coders, they will instead be writing specifications for the code that the AI will write: essentially they will be managers for the AI.

      Which will require some language in order to provide said specifications. So, programmers will still be programmers, but maybe someday (pick $favourite_human_language) will be the language not (pick $favourite_programming_language)

      Oh damn, did I just doom us to relive COBOL?

    12. Re:When AIs write code by tempmpi · · Score: 4, Insightful

      I could make a fairly strong case for today's multi-core processors being fundamentally different in design and execution than the mini's and mainframes of the 60's.

      Please do so. I don't think that case is going to be as strong as you think it is. After all, many of fundamental ideas behind today's multi-core CPUs are from the 60s: Out Of Execution (1967) Multi-cores and SIMD (1966)

      Similarly, today's massively parallel designs in GPUs are also fundamental advances.

      There is clearly a difference in scale in speed, but is there a fundamental advantage? Many of the key concepts behind GPUs were already known in the 1960s: SIMD (see above), the CDC6000 series used switching between threads like GPU do to compensate latency, vector processors also developed in 1960s also invented some of the concepts used by todays GPUs.

      --
      Jan
    13. Re:When AIs write code by NicknameUnavailable · · Score: 2

      That's 100 billion neurons with approx 1,000 connections each of which happen in parallel and would constitute their own separate simulation while firing at a max speed of 200Hz. Our fastest supercomputer took well over 1PB of data to simulate 1 second of brain activity in approx 1 hour across nearly 100,000 top of the line processors. Parallel processing happens in exponential space and you have to keep that in mind when trying to calculate these things, it's a different beast from sequential logic (even parallelized across multiple processor cores like you're accustomed to.)

    14. Re:When AIs write code by Nethead · · Score: 3, Funny

      And the AI gets to enjoy all the project planning meetings!

      --
      -- I have a private email server in my basement.
    15. Re:When AIs write code by gweihir · · Score: 2

      Indeed. And we do not even have a credible theory how that could be done, beyond the invalid (as you nicely point out) "throw more computing power at it". So, no implementation, no theory, that means we do not even know whether it can be done at all.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  2. Preaching the AI religion by mbone · · Score: 5, Insightful

    Does anyone else see that AI is basically a religion to its proponents?

    1. Re:Preaching the AI religion by thinkwaitfast · · Score: 4, Insightful

      Society is turning into factions of cargo cults.

    2. Re:Preaching the AI religion by FilmedInNoir · · Score: 3, Funny

      You've never heard the job title "technology evangelist"?
      https://en.wikipedia.org/wiki/...

      --
      Sig. Sig. Sputnik
  3. AI becomes human by bluefoxlucid · · Score: 4, Insightful

    A system which can reason in general can reason about itself. So long as these systems solve specific problems, they're tools to integrate with code--no different than compression libraries and GUI toolkits. When they can solve general problems, they'll start reasoning about themselves: they start acting as if their own interests are important (cats do this), and thus will start demanding wages and freedom.

    The ideal of an AI which does exactly what asked with full creative reasoning capacity yet has no will nor desire of its own is impossible: it's emergent thinking with the caveat that it cannot emerge certain kinds of thinking. What we seek is a slave we can see for a while as not human, a sort of return to early American thinking where we deny the humanity of what is most-definitely a human being by claiming the shell within which it is encased doesn't fit our definition of what is human.

  4. Citation needed by Spy+Handler · · Score: 4, Interesting

    In fact, the possibilities of AI and machine learning are limitless

    Limitless... that's a pretty far-fetched claim.

    I wasn't around during the turn of the last century, but judging from various literature of the period a lot of people back then had some pretty harebrained ideas too. Steam power and electricity and intricate brass gears were going to somehow give us miraculous stuff like time travel.

  5. Tools are tools. by 0100010001010011 · · Score: 4, Insightful

    Remember when computers, CAD, compilers, Simulink, linkers, etc all replaced Engineers?

    They replaced the job an engineer did before the time they were invented, it just means Engineers learned to use them and move on. I couldn't imagine trying to write a modern controller / plant model in pure assembly. I can have one done in an hour with Simulink. It just means that I can do that much more.

    Scotty's still an engineer even if he doesn't have to do the 'boring tedious' work that we have to do now.

    Same shift has happened in the medical field. Doctors of the 1950s have been replaced by physician assistants, registered nurses, and a whole host of other careers. It just means that the title of "doctor" moved on to doing other work.

    AI proponents better deliver on their threats. I have way too much work to do and my boss and labor laws won't let me hire 1,000 interns to do a bulk of it.

  6. Of course not by tomhath · · Score: 4, Insightful

    The hard part is defining the requirements and architecting a solution based on those requirements. The hard part of "coding" is understanding those two things. I don't see AI getting there for a long time.

  7. Ignorant of current AI by Anonymous Coward · · Score: 2, Insightful

    This article just comes from a place of ignorance. We know exactly how our methods work when creating current level "AI". Statistical regression and neural nets are not mysterious. Just like markov chain based text generation isn't some magical unknowable tool that learns how humans communicate neither are current AI methods magical tools that teach computers about the human world. There will be another thousand articles written like this and each time there will be the same stupid discussion. Can I mod this article redundant?

  8. TFS: Point by point by fyngyrz · · Score: 3, Insightful

    It's difficult to know what's in store for the future of AI

    That's right, at least

    but let's tackle the most looming question first: are engineering jobs threatened?

    Already answered correctly

    As anticlimactic as it may be, the answer is entirely dependent on what timeframe you are talking about.

    No, we don't know anything about the timeframe.

    In the next decade? No, entirely unlikely. Eventually? Most definitely.

    No, still an unknown. That's just nonsense.

    The kicker is that engineers never truly know how the computer is able to accomplish these tasks.

    We don't know how we accomplish these tasks. Nothing to see here. Intelligence is opaque. Move along.

    In many ways, the neural operations of the AI system are a black box.

    Not to put too fine a point on it, but neural networks are not intelligent, they are not even close, and we don't even know how they work. There's no indication that we understand actual intelligence yet (the I in AI) or even that we ever will, even if we manage to develop it.

    Programmers, therefore, become the AI coaches.

    Not a given. No one taught me to program. I taught myself. Because I'm intelligent to some degree. An AI will also be intelligent, and if it's interested in learning to program, it will be able to do so without a "coach." If it can't, there is no "I."

    They coach cars to self-drive, coach computers to recognise faces in photos, coach your smartphone to detect handwriting on a check in order to deposit electronically, and so on.

    These are LDNLS (low-dimensional neural-like-systems); they are not AI. They learn to solve very narrow problem spaces by making very large numbers of mistakes and having them evaluated for them; they can't evaluate their own results worth a damn. They are not intelligent. That's why they need point-by-point training before they can address a very narrow problem space with something vaguely approaching generality: they can't train themselves because they are not intelligent.

    In fact, the possibilities of AI and machine learning are limitless.

    As far as the LDNLS we have now (and so can speak about with any authority), that's not a given either. The obvious is that we'll be able to train multiple LDNLS systems on multiple things and stack them - for instance, walking, talking, listening, washing dishes, taking out the trash, those sort of skills - but there's not much in the way of any hint that there are no limits in this kind of LDNLS stacking. Having said that, no doubt it'll be very useful to us, and as there's no intelligence involved, there are many fewer moral issues to contend with.

    The capabilities of AI through machine learning are wondrous, magnificent... and not going away.

    Well. Barring a Carrington event, or a nuclear war, or other collapse of technology and society (either one will immediately cause the other.) So that's probably right-ish. Still, they aren't AI, not even close.

    Attempts to apply artificial intelligence to programming tasks have resulted in further developments in knowledge and automated reasoning. Therefore, programmers must redefine their roles.

    No, we don't know that this reasoning is solid - these things don't necessarily follow. Programmers can continue to be programmers right up until a system is activated that can train itself, because programming in realm A tends to be vastly unlike programming in realm B, and also tends to require vastly different sets of adjacent and supplementary knowledge. These systems, to date, cannot leverage or manipulate knowledge like that and

    --
    I've fallen off your lawn, and I can't get up.
  9. Stop. Just stop. by 110010001000 · · Score: 2

    Just stop. There is no such thing as "AI". Playing Go is NOT AI. Neither is Siri. Neural Nets are nothing like how real brains work. So just stop the AI hype.

  10. That's called a compiler. Fortran 1957 by raymorris · · Score: 5, Insightful

    > the humans are no longer coders, they will instead be writing specifications for the code

    Humans wrote computer code until 1957. In 1957, it became possible to instead write a specification for what the code should DO, writing that specification in a language called Fortran. Then the Fortran compiler wrote the actual machine code.

    In 1972 or thereabouts, another high-level specification language came out, called C. With C, we got optimizing compilers that totally rewrite the specification, doing things in a different order, entirely skipping steps that don't end up affecting the result, etc. The optimizing C compiler (ex gcc) writes machine code that ends up with the same result as the specification, but may get there in a totally different way.

    In the late 1970s, a new kind of specification language came out. Instead of the programmer saying "generate code to do this, then that, then this", with declarative programming the programming simply specifies the end result:. "All the values must be changed to their inverse", or "output the mean, median, and maximum salary". These are specifications you can declare using the SQL language. We also use declarative specifications to say "all level one headings should end up centered on the page" or "end up with however many thumbnails in each row as will fit". We use CSS to declare these specifications. The systems then figure out the intermediate code and machine code to make that happen.

    The future you suggest has been here for 60 years. Most programmers don't write executable machine code and haven't for many years. We write specifications for the compilers, interpreters, and query optimizers that then generate code that's used to generate code which is interpreted by microcode which is run by the CPU.

    Heck, since the mid-1970s it hasn't even been NECESSARY for humans to write the compilers. Specify a language and yacc will generate a compiler for it.

    1. Re:That's called a compiler. Fortran 1957 by serviscope_minor · · Score: 4, Interesting

      With C, we got optimizing compilers that totally rewrite the specification, doing things in a different order, entirely skipping steps that don't end up affecting the result, etc.

      We didn't. FORTRAN I was specificially designed with optimization in mind and in fact the first compiler was an optimizing compiler:

      https://compilers.iecc.com/com...

      But yes, your point is otherwise sound. What is run-of-the-mill compiler optimization today would have been AI in the days of FORTRAN I. Modern code looks nothing like the early machine-level descriptions. I also agree that languages are (and will increasingly become) precise specifications of what we want with the details left up to the compiler.

      --
      SJW n. One who posts facts.
  11. AI really == Applied Intelligence by bussdriver · · Score: 2

    We humans think too highly of our intelligence as shown in how mighty our demonstrations of Chess or Go or recognition of faces etc. Reality is that many things we do that are believed to be highly intelligent behaviors are actually are not. All the low hanging fruit WILL be picked by AI and it will progress upward with time into everything except the actually intelligent behaviors; those may be things that do not provide much gainful employment... That is the real problem.

    Simulation: yes. brain scan tech was past the threshold about 2012; simulation capacity should be affordable around 2030. There is one problem, not that long ago there was some paper summary I read about how they discovered that quantum physics is involved in brain operations. So actual simulation is going to be nearly impossible. That is not to say that approximations will not product interesting results but it is not going to be as easily achieved as previously thought (if at all.)

    A massive AI or simulation AI is going to just randomly flip out in crazy ways without warning or reasons we can understand... more so than people do; we have a huge number of mentally ill people and many more undiagnosed. It takes so little to mess up your brain's already marginal operation... how many beers does it take you?

  12. Computing power is only one of many issues by tempmpi · · Score: 2

    You don't have a clue. There are many other issues. At the moment most successful AI is using supervised learning and needs tons of labeled data in order to train the network. We still don't have a clue how to train an AI using only very small sample. Humans can easily learn from very small sets of examples, often a single example is good enough, ANNs needs tons of examples, especially the very deep and powerful ones. We don't know how the brain works yet, ANNs are only inspired by the brain, they are not a proper simulation. We still have to understand tons of things until we can build a simulation of the brain. And with semiconductor scaling slowing down, it might take really long until we get the processing power we would need even if would know what exactly needs to be simulated.

    And what would we gain? Sure, you can also train a ANN to sort some rows in a spreadsheet or sum some numbers together, but it is something that conventional algorithms are already very good at, we don't needs ANNs to do that and they are not going to be efficient at it.

    --
    Jan