There are a number of perspectives from which AI can be approached, and so people have different perceptions and understandings of it -- which can be based on their own direct knowledge and use of it, or what others say about it. Artificial intelligence is a very broad subject (much, much broader, and much more complex than it was, say, 20 or 30 years ago) and now includes significant advances in such areas as perception and motion (think of self-driving cars or those military robots and doggies

). And much of contemporary AI has had substantial influence from such areas as cognitive science and brain science. It's not just "the algorithm" or, more generally, algorithms. In fact quite a lot of it isn't algorithmic at all, and most people reading this sentence probably don't know what an algorithm really is anyway. Certainly the vast majority of news reporters haven't a clue.
I'm no expert in what I think of as contemporary AI -- which involves, among other things, large language models. I think that I grasp the fundamental approach and at least the major strengths and weaknesses -- but from outside the design/development/deployment/application community. And I do get feedback in various ways from people currently working on and with AI, and whom I stay in touch with. If you'll pardon some self-indulgence, here's my own current perspective on AI from a personal history perspective over about 30 years, and how I approach evaluating what I see nowadays in terms of AI theory and applications. Of course, just bail out on this if it's uninteresting or tedious.

But you may find some of the sketch of AI history that's in it to be interesting (keeping in mind that the last time I actually stood in a classroom and taught a course in AI was about 45 years ago.

), although I've certainly given a number of presentations and talks on it since then.
But before you bail on me, let me suggest you take a look at
"Getting from Generative AI to Trustworthy AI: What LLMs might learn from Cyc" (
https://arxiv.org/pdf/2308.04445) -- written by someone who was an old friend and colleague, and one of the major contributors (in both theory and practice) to AI into the 21st century, and with whom I also had some serious disagreements about AI in various respects. Some of the things that Doug says in this article (I'm not sure if it was ever published) are compatible with things expressed in this thread as well.
----------
I first got involved in AI in 1981 when I taught an upper-level undergraduate course using Patrick Winston’s book Artificial Intelligence. A year or so later I left my safe tenure at the university and devoted fifteen years (a small consulting firm, Bell Laboratories, and SAS Institute) to becoming a serious software engineer and formal language and compiler expert – few publications, but lots of work and applications. I got tired of that, and a colleague (a mathematician turned software engineer) suggested that I should take a look at Cycorp (
https://cyc.com/).
Cycorp (in Austin) didn’t at that time support any remote staff, but said a client of theirs was looking for someone in the RTP area where I was living. In 1997, after a two month vetting process, I began a job at Glaxo-Wellcome – first on the IT side in Research IT, and then on the science side in Exploratory Data Sciences, working primarily in the area of text mining and “intelligent information retrieval” in support of drug discovery and drug safety. During that period I was focusing in part on natural language systems for turning things like medical reports and doctors’ notes into usable data in an accurate way. The approach at that point was still using hand-written language analyzers such as Brill taggers and Abney (cascaded finite state automata) natural language parsers. The technology was advancing, but still cumbersome.
For three years I was heavily involved in working with Doug Lenat at Cycorp (GW was leasing the Cyc system, as was Pfizer) in attempting to apply Cyc to problems in drug discovery, bioinformatics and “intelligent search” engines for their scientists and librarians. Cyc is a “knowledge-based system” (KBS) with a heavy-duty inference engine – and then to apply its inferential capabilities you need to create a very large database in a particular domain (the result is often referred to as a “micro-theory”). This is very labor intensive, somewhat error-prone, and expensive both to develop and to test. One of the prototypes I did in the area of protein science was encouraging, but it was still pretty cumbersome and the company didn’t want to pursue it. Apparently the Pfizer project went the same way, although we definitely weren’t sharing information. (Aside: I think that one of the approaches that might be successful would be to use an LLM Ai to generate a KBS (avoiding the human labor-intensive and error-prone approach) -- which might then serve in part as both an enhancement and a check on the LLM AI. I think that Doug was suggesting this approach as a "hybrid".)
In 2000, Glaxo Wellcome merged with Smith-Kline Beechum and I moved from Research IT (in the IT organization) to Data Exploration Sciences in the Research (scientific) organization within GSK – but only momentarily. At that point the European head of bioinformatics at GW moved to Novartis and I got an invitation to join the Novartis Artificial Intelligence group (Basel) as Associate Director of Artificial Intelligence. While I learned a lot more about language processing and AI from some colleagues in that group (who had left the Paris IBM Natural Language Processing group to join it), and completed a major intelligent information retrieval application based on AI/intelligent search technology, I didn’t care for the group’s management and after a year returned to GlaxoSmithKline in the Biomedical Data Sciences division – and created the Semantic Technologies Group.
Skip forward several years, through more work with various AI-related products and technologies based primarily on the use of formal ontologies, and I formed a small (2 other guys and me) group to develop an AI and large data analysis approach to early detection of adverse drug reactions. I called the project “SafetyWorks”. We ended up doing all our own IT infrastructure and support (funded by the Drug Safety organization), and the project was hugely successful. This was then picked up by the OMOP (Observational Medical Outcomes Partnership) industry/academic/government consortium, and the work our group had done was also given away (including the hundreds of thousands of lines of code) to an external company to “productize” and lease back to GSK. I wanted nothing to do with any of that, and retired in 2007. The (then) junior member of the team ultimately later moved to Johnson & Johnson and became the principal investigator for OMOP.
I did get a nice lucite award trophy that says “SAEfetyWorks Innovation Award, 2008” for “outstanding contributions to drug safety science” – misspelling the name of the project. I also was offered a job as a director of Epidemiology at Merck, but declined that for several reasons, decided to retire early, and didn’t look back. (Well, I did a couple more publications after that, but more of a foundational/theoretical nature.)
So that’s the background and perspective from which I approach an understanding and evaluation of AI.
I’m really out of the game now, but I do keep in touch, read drafts of papers when asked, and offer encouragement and mostly harmless advice (when asked). To really keep up with it would require a great deal of energy and effort that I’m not willing to devote. It’s really hard stuff, and I got tired of the really hard stuff. Plus, I'm really old and don't do the really hard stuff so well any more. At this point, AI is kind of like astrophysics. Anyone can grasp small chunks of it and speculate about other parts of it. But to really make sense of it takes a great deal of study and effort, and short of that you have to depend on other people's dumbed down reports, explanations, and analyses. And figuring out which of those are in fact dependable is just another hard problem.
