Adam Sturrock的动态

Preston So oscillation between low-code and composable makes a lot of sense...

I'll have to admit, being a developer at heart and someone who got started in web development primarily "maintaining" (i.e., fixing) Dreamweaver sites, my initial thoughts of no/low-code is less than positive. However, as you start to get into the weeds, it becomes clear there is a lot of value to simplifying both the developer and the marketer's experience through tools and patterns that can bridge the gap, especially in a headless architecture. I especially like?Preston So's take on "flex-code"; it's very close to how we're approaching our own digital experience framework.?

cheers Adam Sturrock and Preston So, great example of "a picture is worth a thousand words"

Intriguing version of my graph, thanks for sharing, Adam! I'm not quite sure that low-code is the silver bullet that restores the equilibrium I've written about over the course of this year. Low-code has the potential to stymie the developer experience just as much as headless has the potential to block marketers and editors. I'm more inclined to lean towards a *flex-code* paradigm that allows developers and marketers to use their preferred best-of-breed tools: https://www.cmswire.com/web-cms/flex-code-is-the-future-of-cms-builds-not-no-code-or-low-code/

Yes! API-first/Headless disrespects the marketing people.

Some further thoughts on the diagram; Y axis = control, X axis = speed - tradeoffs and sacrifices are typically made depending on which approach you adopt. #Headless was a knee jerk reaction to the monolithic approach, this in turn matured and became more sophisticated over time with the rise of #MACH and Composable.

Thomas Gottheil ??

https://www.outsystems.com/blog/posts/low-code-vs-no-code/ Here is a great article describing the differences between low-code and no-code as they often get lumped together, mixed, and used interchangeably which is confusing and misses the nuances. There are actually subtle but very important differences.