rsm
Well-known member
enjoy the future!
But it could mow your lawn?A robot can't steal your job if you're retired.
![]()
LISP, Smalltalk, Fortran?FWIW, I've been working in AI for decades. Most people have no idea that AI has been in use for several decades, what it has been doing, and what it will be doing.
To be successful, AI systems don't have to eliminate human workers or activities, it can also reduce the complexity of human tasks, or be assistive - allowing people with fewer skills / less knowledge to be more productive.
in the early days I did some proto-AI (automation using rules engine models) in CICS macro-level assembler and command-level COBOL;LISP, Smalltalk, Fortran?
Pascal or GTFO.Interesting. I like Prolog for it's do or die attitude. Did you find it use helpful in the transition to C and Java?
Party like it's 1970.Pascal or GTFO.
![]()
No Prolog didn't help with C or any other languages; Prolog is a very different language model, it's a rules / inference engine, for backward chaining; not much else. We used it for what were called expert systems back then.Interesting. I like Prolog for it's do or die attitude. Did you find it use helpful in the transition to C and Java? Were you in Europe in the early days? Banking sector?
The problem with open-to-the-public generative AI such as OpenAI / ChatGPT is the lack of governance; they will lie, hallucinate, develop biases, etc.I am a Principal Software Engineer at a healthcare analytics company.
We are doing prmarily java, sql, nodejs, and implementing performance sensitive operations in rust.
We’re honed in on ChatGPT type “ai” to improve our mapping of customer data to our catalog and contract data.
We did some trials on having ai actually write code. It was neat but underwhelming. It was able to reliably produce fragments and functions. Classes it produced were not that great. It was incapable of generating whole applications from scatch.
Its sql was pure crap. It regularly produced queries that did not generate the right results, performed like shit, and in several cases could not compile.
ChatGPT was terrible at math. Routinely generating incorrect mathematical functions and formulas.
It was common to find security vulnerabilities in “ai” generated code as well as poor performance. The code generated was very average. Looked like a junior engineer had written it.
It was particularly bad at things like implementing checks on external inputs and other general security best practices.
Where we found it exceled was when it was used by an engineer to bootstrap implementation. We did one where we generated a function to perform multi-threaded read and transformation of very large customer files in rust. The rust code it generated was not great but it allowed our engineer to focus on tightening up the generated code instead of producing it from scratch. It afforded a shorter implementation timeline.
It is proving very effective at mapping imported customer data into our historical analytical repositories. We were already above 90% on high confidence mapping. We are seeing that mapping rate go above 99% with this generation of “ai”.
The data used for training is crucial. We found that ChatGPT was generating some code using copyrighted intellectual property. It did not provide any attribution.The problem with open-to-the-public generative AI such as OpenAI / ChatGPT is the lack of governance; they will lie, hallucinate, develop biases, etc.
I heard of an attorney who recently used ChatGPT which used imaginary cases, he's under investigation for possible disbarment...
Healthcare and insurance especially; you need to be able to explain how results are generated or you're gonna face lawsuits.
The data used for training is crucial. We found that ChatGPT was generating some code using copyrighted intellectual property. It did not provide any attribution.
We also found that it was incapable of complying with opensource licensing requirements. When it used open source implementations, it failed to provide the license as required. Not a huge problem for experienced developers. I think we will see ip lawsuits on AI generated code in the future because people with just copy/paste generated code.
We are currently evaluating standing up a private instance for our mapping. Training it is… challenging.
NoHave a look at Hugging Face?
worth a look, they're HQ in France.