While I mostly publicize my #lowocode #handbook now, our #modeldriven #book is still pushing strong .

We're approaching 150 institutions #worldwide using the book. Latest one is an #MDE course by Mert Ozkaya at Yeditepe University (number 141).

With both books you can cover any #modeling, #DSL, #lowcode, #codegeneration, #modeldriven... topic. Pick the one that works best for you. Or even better, pick both !

https://mdse-book.com/

https://lowcode-book.com/

Very happy to see my #paper: "Positioning of the #lowcode movement within the field of model-driven engineering" (https://modeling-languages.com/low-code-vs-model-driven/) as one of the top cited papers of the #MODELS conference (according to #ACM https://dl.acm.org/conference/models).

I'm especially happy because:
It's a #workshop paper. We should not forget the value of discussing our ideas. Even if they have not fully developed. And even less validated. Ideas and discussions are still very valuable for #research advancement

It's a #single #author paper. I think it's important for any researcher to still publish single papers from time to time. Obviously, these papers will most likely workshop contributions (or similars) as current validation trends make it very difficult for a single author to "check all the boxes" (maybe with #LLMs...). But it's always something especial when you work alone.

Ich bin auf der Suche nach Leuten, die sich mit Open Source Low-Code-Plattformen auskennen.

Habt Ihr irgendwelche Tipps für mich?

Pls

#opensource #lowcode

EDIT: Tatsächlich geht es mir gar nicht um den konkreten Einsatz, sondern ich suche eher nach jemandem, der einen guten Überblick über das Thema hat, und z.B. Open Source und proprietäre Low-Code-Lösungen vergleichen und auch über potentielle neue Lock-In-Effekte bei Low Code sprechen könnte.

A #Metascience Study of the #LowCode #Scientific #Field

We aimed to:
Analyze the composition and growth (e.g., size, diversity, venues, and topics) of the emerging #LowCode #community; and
Explore how these aspects differ from those of the “classical” #modeldriven community.

This covers #ResearchQuestions such as:

Are Low-Code #publications affecting the number of traditional #Modeling publications?
How many Modeling conferences and workshops aim to explicitly attract Low-Code publications?
How are authors distributed across Low-Code and traditional Modeling publications?
How many Low-Code open-source platforms and tools explicitly relate to traditional Modeling techniques?

Lots of interesting insights

Read the post for the full details and/or meet me at the next #STAF #ECMFA conference in #Koblenz next month

https://modeling-languages.com/metascience-adoption-low-code/

Beyond Vibe Coding: Welcome to Vibe Modeling

#Vibecoding lets anyone build software by chatting with an AI /LLM. But the result is a throwaway artifact, nothing you could actually use in production.

#Vibemodeling takes the good parts of vibe coding and combines them with a model-based approach, enabling deterministic, reliable software generation without writing a single line of code and minimal tech expertise.

Want to know more? https://modeling-languages.com/vibe-modeling/

Your thoughts?

Read the first two chapters of the #lowcode #book for #free

If you would like to take a peek at the book before deciding whether it's worth buying (this seems an obvious decision to me but ...), you can now download a pdf file with the first two chapters:

https://lowcode-book.com/free-chapters/

(and remember in the same website you'll find plenty of other information and resources around the book)

You know, we invented systems before there were computers.
'Forms' were on paper, rather than on screens.
An 'in tray' was an actual metal wire, or wooden tray, for paper letters, notes, memos and forms.
A database was called a 'filing cabinet'.
An 'interface' was a mail box.
A 'front end' was a person, with a job title like administrator, or clerk.
These systems were described, in excruciating detail, in procedure manuals.
The processes were run not by CPUs, but by people.
'Bugs' were when people made mistakes.

Systems were difficult to understand, even harder to diagnose, and very very hard to fix or change.
To change the way a department worked, for e.g. accounts receivable was so hard that most companies never even tried.

And yet somehow people are under the impression that it is the code that is the difficult bit about modern business systems.
So they try and make the code part easier.
#LowCode #LoCode #NoCode #AI #GenAI #LLM

It was never the code. Code was never the bottleneck.

https://raganwald.com/2012/01/08/duck-programming.html

Now is the time to get away from techgiants and all their tech promises like #llm #cloud #lowcode #microservices and all the other promises they made.

Amazing software is made by people that are passionate about their craft this is also true for software #development . Don't get fooled that #llm can replace the systems thinking and problem solving abilities a passionate developer gained over the years.

Most software doesn't need that "massive" scale that is described in all the tech articles. Most of the time smaller systems and even monoliths are a great choice if done properly.

Also look forward to move your software away from regimes that are truely against the free and democratic world. Host in for example in #europe . Move away from software that could be easily removed in minutes from you. #Selfhosting build your own specialised software and count on companies based in countries you trust.

State Department wants a "market-leading low-code/no-code" application that can "host custom applications using Java Script, AJAX, PL/SQL logic, Angular JS, and Jelly" and host a chatbot. I'm excited to keep an eye on this and see the monstrosity that the winning bid turns out to be. https://orangeslices.ai/state-department-sources-sought-bureau-of-diplomatic-technology-dt-low-code-application-cloud-platform-tool-platform-as-a-service-paas-software-as-a-service-saas/
#LowCode #NoCode #LotsOfCode #StateDepartment

#LowCode Solutions Gain Traction In #Banking And #Insurance #DigitalTransformation

https://www.pymnts.com/innovation/2024/low-code-solutions-gain-traction-in-banking-and-insurance-digital-transformation/

I am not a programmer. This is frequently a cause for headaches.

I write lots of scripts, work with windows reverse engineering, code for micro-controllers, etc. but I don't write code that does anything ... visible?

So here I am with a project that requires a DB (of some sort), to store data as entered by users (so an auth portion as well), then perform simple math on it. And display results back. There are any number of ways to make it more rich/complicate the project, but that's it at it's core.

However; I have zero experience in this field. The DB structure (if you can call it that) that I'd want to use is simple but where does one get started creating anything UX attached to a database (sql? pgs? sqlite? etc.) these days? Without learning 10,0000 hours of code to do this one thing?

It feels like it should not be so grossly complex to do what I'm wanting, but I have no idea where to start and the few tools I had seen suggested all come with "First Build a VM, Install python, update pip, now setup docker then you need these 35 dependencies, and hey, how much do you know about compiling your own fork of nginx?, etc."

Suggestions from the #programmer/#webdev audience?

#lowcode ? #nocode ?

After spending years advocating for the API Design-First workflow, I’d like to talk about times where I completely ignore the whole idea and spin up something like Airtable to solve a problem and make an API that isn’t going to be great. I’ve not gone mad, promise. #ApiDesign #Automation #LowCode #NoCode https://apisyouwonthate.com/blog/low-code-no-code-and-automation-for-apis-gadget-or-godsend/

Low code: AI is lowering the barriers to entry, report

Low code tools are starting to evolve beyond their traditional sweet spot

https://www.computing.co.uk/news/4152890/low-code-ai-lowering-barriers-entry-report

As a Twitter refugee here a little #introduction to myself:

I am a #LowCode Specialist with background in supply chain management and as a #mechanic. I hold two #patents in heat regeneration.

By day I work for a startup in the #automotive field and by night I design or simplify things for everyday life by #3DPrinting.

I have a weakness for Dieter Rams #minimalist design, #gadgets and simple shapes. Building and riding #fixedgear bikes is something I do to get some fresh air after all.

This is an excellent article on whether #serverless and #low-code tools and approaches are greener.

I was interviewed for it along with others. There are lots of interesting views in here and I think it captures well where we are with the discussion.

Well worth a read.
---
RT @jkriggins
Another rabbit hole on another topic previously unexplored... Is #LowCode greener?

TL;DR: It all depends on what is meant by low code.

Thank you fo…
https://twitter.com/jkriggins/status/1602628726432350208

Audio excerpt from the new book:

https://www.philsimon.com/podcast/episode-74/

Jack of all trades, master of none. Have done stuff spanning from low voltage wiring in new houses, to #tax #accounting, to #lowcode #nocode application development (my current role). Wanna be writer, avatar and header are art of my MC. (By the amazing Lanmanigans over on Twitter https://twitter.com/Lanmanigans)

Avid audio entertainment consumer, music, podcasts, audiobooks, etc, are all great.