Dirk Roeckmann

In #SAP the notoriously slow transport times ‘drag’ #agentic #coding.We should abandon 3-system landscapes and use 2-system ones - dev and prod with a dedicated test client in dev with good data which will significantly improve performance becaus the agent generates and tests in dev only #ABAP
2/2

We all know that #coding #agents need iteration cycles of planning,reviewing, generating, unit testing etc.That’s fine if you can pull your codebase and iterate on it locally. Enter multi-system landscapes in #SAP #ABAP:Generation in dev and unit testing in test means imperformant transport drag
1/2

If #moltbook is of any interest, it’s the fact that it serves as a field study of what happens when you release autonomous agents in the wild.Somebody is working on a moltbook domination prompt right now 😉. Soon people will add #UCP servers so that their bots can buy new hardware 😂. #AI #SAP #ABAP

If people think #moltbook is innovative, don’t think for a second that state entities have not been doing this at scale across the web for years. And at scale, not on a Mac Mini 😂
#AI #SAP #ABAP

#moltbots posting on #moltbook are the hype right now. But aside from ‘autonomous token burning’ nothing new is happening. When bots talk about ‘their humans it’s part of their system instructions, even if new topics are started. Nothing ‘emergent’ here, just same old token prediction #AI #SAP #ABAP

In 1992 Japan the The 5th Generation Computer Systems (FGCS) relying on #Prolog & specialized hardware failed due to the PC wave and led to an #AI winter. Could #tensorlogic lead to a new push for (deep learnable) declarative logic programming on GPU and help explainability? Me thinks YES!🚨🔥

It is so amazing that Charles Sanders Peirce anticipated #tensorlogic with ‘The Logic Of Relatives’ already in 1870! #neurosymbolic #ai

Consequently, agentic coding underperforms in languages like #Haskell and #Prolog for architectural reasons and not only because of comparably sparse training data. With the advent of #tensorlogic where predicative logic runs on learnable tensors that could be a serious problem. #AI
2/2

Here’s one for the ‘#LLM obliterate manual coding’ faction: The auto-regressive architecture of transformers and also #COT work only well for sequential imperative programming and lack in the functional and declarative paradigms. Sequential generation vs global constraints, folks #AI
1/2

#TensorLogic also means that #declarativeprogramming and #functionalprogramming might have a huge boost from this. Anybody motivated to write a lightning fast and hyper-scalable #Prolog on #CUDA and some torch lib? 👍
#Lisp #Coalton #OCaml
2/2

#TensorLogic is a great idea. It does not only bridge the gap between #DeepLearning and #SymbolicManipulation in #AI but the idea alone that you can represent logic (deductive, inductive, abductive) fully as tensor operations is great.
1/2

I can’t understand why otherwise highly educated people can be so fully ignorant of the #history of #science when they postulate natural language ‘is the only #programminglanguage needed’ in the wake of #GenAI. Have they never heard of symbolization and Newton, Leibniz, Frege!? #SAP #ABAP

#AI has been so abused and is misunderstood meanwhile as a synonym of #LLM. We should use the terms #ML (#machinelearning) and #MR (#machine reasoning) widely: ML for all pattern matching paradigms void of semantics and MR for all semantic symbolic knowledge inference.Honest and not ‘intelligent’

Why is everybody so hyped up about flooding the market with turing-incomplete hardware? #GPU are a one-trick pony and once #AI will move on from glorified matmul, this stuff can’t even be repurposed to anything which is not isomorphic to matrix multiplication. #SAP #ABAP

Why is it that many people still believe the #benchmark scores when a new #LLM is introduced? Folks, the test datasets are available online and they will be used in training! This should be prohibited. Test datasets should be locked away and benchmarking should be done by a 3rd party. #SAP #ABAP

We should have noticed by now, that the scaling laws of #GenAI fail and we’ll enter a phase of diminishing returns. Equally problematic is the uncritical re-emergence of failed #symbolic paradigms which brought as #AI winter 1. #Neurosymbolic - yes but not based on failing monotonic reasoning

I have a hunch that #AI research will go beyond glorified matmul and #GenAI as we know it including its hardware will be toast. #LLM will be smaller, will run on turing-complete #CPU again and serve as what they were designed for - a great natural language interface and bridge to symbolic reasoning

“It doesn't make sense to hire smart people and then tell them what to do; we hire smart people so they can tell us what to do”
Steve Jobs

Think about that when you hire consultants 🧐
#SAP #ABAP

I can’t believe how much money is put into such hyper-specialized hardware like a #GPU which is not even turing-complete and can only do parallel matmul. This will all be immediate trash once #AI goes beyond tensor-based paradigms because it can’t be generally repurposed like a #CPU. #SAP #ABAP

In order for #neurosymbolic #AI to succeed we need a renaissance of #homoiconicity. Bring back #Lisp as 2nd lingua franca for #AI next to #Python and perfect their interoperability. IMHO the ideal scenario would be to host a performant Lisp on #Mojo! #Modular @Chris Lattner

Hi all - are #UI #annotations anachronistic in the age of #agentic #AI? Should only the final code be generated and not some intermediate code which has still to
go through the annotation engine? Let me know what you think #SAP #RAP #OData #CAP

In consumer web search and commerce the browser will become a module of #AI agents, #UI will be ephemeral i.e rendered on the fly. In enterprise this translates only partially. #GenAI is not intelligent but transformative. UI annotated code generation is an anchronism. #SAP #ABAP

Here is some common-sense and sad truth: Most customers fail to pen a consistent specification of what they need in natural language to human #developers - what makes deciders think that these very same people could instruct a #codingagent and then verify the results on top of that!? 🧐 #ABAP

There is no need for the #nocode, #locode and #procode silos anymore. No matter whether you #vibecode, use a lo-code interface or code manually in an IDE/editor: The resulting code should always be fully accessible for further optimization and not be hidden behind an opaque UI. #SAP #ABAP

While #SAP touts that it is advocating #OpenSource and being open in general, many recent actions suggest otherwise:
- OpenSAP courses : gone
- CAP 9 : only with BTP license
- OpenPartner Programme : discontinued
- UI5 community: underfunded
What’s going on??? #ABAP

🔥 #zed.dev is the best #IDE I saw in a long time. Fast, written in #Rust and SOTA #AI capable. Who wants to write a #SAP #ADT based #ABAP extension for it? 🚨

To all vibe coders their managers and CIO/CTO/CEOs out there: In case of failure, there is no one to blame but yourself: Not IT, not developers, not consultants, certainly not the #AI itself. To quote Jack Reacher: “Remember - YOU wanted this”. #SAP #ABAP

I like the fact that #SAP tries to be ‘#AI ready’ but at least as for coding it is my firm belief that instead of coming up with their own agent (#Joule) they should have distributed a curated #ABAP training dataset to the real players.Would have made a world of difference for customers. Am I right?

In the age of #AI agent driven flow, #NoUI and #EphemeralUI become more central and will push browser, websites and apps into the background. Questions will be answered directly w/o UI - if necessary, it will be generated on the fly and vanish after use. Exposing data to AI is king #SAP #ABAP

Why wait on #SAP #Joule? If you are on S/4 with #OData (doesn’t matter whether on-prem or cloud), expose your business data 2-fold: 1. webapi #RAP V4, consume with #CAP and 2. webapi V2, consume with #MCP OData bridge. You are ready for #AgenticAI using SOTA coding and #noui agents. Done! #ABAP