Jordi Cabot

Dirijo la unidad de I+D+i en Ing de Software en el LIST (Luxemburgo). Hablando de UML, DSLs, programación, OSS, IA.... Also in English: @JordiCabot

[Jordi Cabot @ingdesoftware]

Record Guinness al modelo UML más grande del mundo

[Jordi Cabot @JordiCabot]

📣📢 Announcing the 1st edition of the #workshop on #Quantum #Modeling, co-located with MODELS'26

Join us to explore the combination of quantum for model-driven engineering and #MDE for the development of quantum #hybrid systems

Details: ➡️ ➡️➡️ https://t.co/RnS4Y3DR4L

[Cormac @cormachayden_]

software engineers before vs after agents

[Jordi Cabot @JordiCabot]

🎬New release of our #uml and #lowcode #OSS #tools #dashboard 👏

☑️ The low-code dashboard live: https://t.co/RFJm6rw3Q6

🔗 https://t.co/6JJVsD0LpN

☑️ The UML dashboard live: https://t.co/UOE77aRMa9

🔗 https://t.co/550gJyOTDE

[Jordi Cabot @ingdesoftware]

ICYMI: Vibe-driven model-based engineering: cuando el low-code y la IA tuvieron un hijo https://t.co/drKLSuQddn vía @ingdesoftware
#lowcode #vibecode #vibecoding #vibemodeling #spec #modeling #IA

[Jordi Cabot @ingdesoftware]

Vibe-driven model-based engineering: cuando el low-code y la IA tuvieron un hijo https://t.co/drKLSuPFnP vía @ingdesoftware
#lowcode #vibecode #vibecoding #vibemodeling #spec #modeling #IA

[Jordi Cabot @ingdesoftware]

@NavarroDescals @FIEC1 Certament és un tema molt complicat. Jo vaig tornar... i vaig tornar a marxar

[Jordi Cabot @JordiCabot]

Vibe-driven model-based engineering: when low-code and AI had a son

Read on to discover how to best combine #lowcode and #AI (#vibecoding) to balance #determinism and #flexibility.

#hint: all the paths do not lead to #Rome but to #models

https://t.co/N1s3WYCE1b

[Jordi Cabot @JordiCabot]

Do you ask an #LLM to #review your paper BEFORE submitting it to a #conference? 🤔🤔

Some interesting comments 👉 https://t.co/LboE60Wses

[Jordi Cabot @ingdesoftware]

386. Más allá del código: cómo la IA redefine la ingeniería del software, con Jordi Cabot https://t.co/4LbsnZpq4a

[Jordi Cabot @JordiCabot]

13. #Timing is everything‼️‼️
No idea is so unique that only you will ever think of it. You are not that #smart.

☝️This is one of my favorite pieces of advice for #junior #researchers, who tend to think they are sooooo clever that nobody else is having the same idea. Well...

[Jordi Cabot @JordiCabot]

🚨#SLE (Software Language Engineering) Abstract deadline in 1w!🚨

Remember we accept:
✅Full
✅New ideas/vision
✅Tool papers

You can even submit papers that do not talk about #AI 🤯😱 (but no worries, you can also submit AI-related papers 😉)

https://t.co/VlfiVbJSYf

[Jordi Cabot @ingdesoftware]

Me arriesgo a prometer que será interesante

[Jordi Cabot @JordiCabot]

📌 📣 TALK announcement: Rethinking the #Future of #Software #Development: What, Who and How

🗓️ March 4st at 18:30
📍 University of Luxembourg, ampus Kirchberg, Rue Richard Coudenhove-Kalergi 6, Room Paul Feidert

#Free but need to register: https://t.co/wb51E68Tr3

[Thomas Wolf @Thom_Wolf]

Shifting structures in a software world dominated by AI. Some first-order reflections (TL;DR at the end):

Reducing software supply chains, the return of software monoliths – When rewriting code and understanding large foreign codebases becomes cheap, the incentive to rely on deep dependency trees collapses. Writing from scratch ¹ or extracting the relevant parts from another library is far easier when you can simply ask a code agent to handle it, rather than spending countless nights diving into an unfamiliar codebase. The reasons to reduce dependencies are compelling: a smaller attack surface for supply chain threats, smaller packaged software, improved performance, and faster boot times. By leveraging the tireless stamina of LLMs, the dream of coding an entire app from bare-metal considerations all the way up is becoming realistic.

End of the Lindy effect – The Lindy effect holds that things which have been around for a long time are there for good reason and will likely continue to persist. It's related to Chesterton's fence: before removing something, you should first understand why it exists, which means removal always carries a cost. But in a world where software can be developed from first principles and understood by a tireless agent, this logic weakens. Older codebases can be explored at will; long-standing software can be replaced with far less friction. A codebase can be fully rewritten in a new language. ² Legacy software can be carefully studied and updated in situations where humans would have given up long ago.

The catch: unknown unknowns remain unknown. The true extent of AI's impact will hinge on whether complete coverage of testing, edge cases, and formal verification is achievable. In an AI-dominated world, formal verification isn't optional—it's essential.

The case for strongly typed languages – Historically, programming language adoption has been driven largely by human psychology and social dynamics. A language's success depended on a mix of factors: individual considerations like being easy to learn and simple to write correctly; community effects like how active and welcoming a community was, which in turn shaped how fast its ecosystem would grow; and fundamental properties like provable correctness, formal verification, and striking the right balance between dynamic and static checks—between the freedom to write anything and the discipline of guarding against edge cases and attacks. As the human factor diminishes, these dynamics will shift. Less dependence on human psychology will favor strongly typed, formally verifiable and/or high performance languages.³ These are often harder for humans to learn, but they're far better suited to LLMs, which thrive on formal verification and reinforcement learning environments. Expect this to reshape which languages dominate.

Economic restructuring of open source – For decades, open-source communities have been built around humans finding connection through writing, learning, and using code together. In a world where most code is written—and perhaps more importantly, read—by machines, these incentives will start to break down.⁴ Communities of AIs building libraries and codebases together will likely emerge as a replacement, but such communities will lack the fundamentally human motivations that have driven open source until now. If the future of open-source development becomes largely devoid of humans, alignment of AI models won't just matter—it will be decisive.

The future of new languages – Will AI agents face the same tradeoffs we do when developing or adopting new programming languages? Expressiveness vs. simplicity, safety vs. control, performance vs. abstraction, compile time vs. runtime, explicitness vs. conciseness. It's unclear that they will. In the long term, the reasons to create a new programming language will likely diverge significantly from the human-driven motivations of the past. There may well be an optimal programming language for LLMs—and there's no reason to assume it will resemble the ones humans have converged on.

TL; DR:
- Monoliths return – cheap rewriting kills dependency trees; smaller attack surface, better performance, bare-metal becomes realistic
- Lindy effect weakens – legacy code loses its moat, but unknown unknowns persist; formal verification becomes essential
- Strongly typed languages rise – human psychology mattered for adoption; now formal verification and RL environments favor types over ergonomics
- Open source restructures – human connection drove the community; AI-written/read code breaks those incentives; alignment becomes decisive
- New languages diverge – AI may not share our tradeoffs; optimal LLM programming languages may look nothing like what humans converged on

¹ https://t.co/0gO5TUwguU
² https://t.co/oN0PnPr1dF
³ https://t.co/nWKSw0m2Ct
⁴ https://t.co/ZrH3fhzQD4

[Jordi Cabot @ingdesoftware]

🕵️ La Software Diversity Card

El cómo y el porqué deberíamos informar sobre la diversidad de los proyectos de software

🔗 https://t.co/2LRsJdvPcO

[Jordi Cabot @JordiCabot]

👀The Neural Network Factory: An LLM-Generated Dataset 👀

We leveraged GPT-5 to automatically generate a diverse dataset of 608 neural networks suitable for empirical experimentation

🔗 https://t.co/1bpXiZEsAZ

#NN #llm #dataset #empirical #research

[Andrés @pelusete]

@DanielBlancoSWE Lo que no consigo entender es cómo han pasado todos los programadores de odiar documentar a querer hacer solo eso 🤣

[Jordi Cabot @JordiCabot]

An AI (#Cursor) using another AI (our #vibemodeling editor) to create a #uml model in our web editor 🤯🫢

(shown by Bernhard Schenkenfelder )