Yesterday I had the pleasure of attending Jamie’s first of five sessions named Bringing Drupal AI into your DNA, which also coincided with the Drupal AI initiative announced this week.
My personal key takeaway from this was how I agree that Drupal well suited as Digital Ops Orchestration too.
Beyond its technical suitability, you could add Drupal’s rich heritage in Open Source beyond just licensing but collaboration with the community.
In a day of age where AI SaaS platforms are emerging left, right, and centre, and AI hustlers and vibe coders are leveraging AI to build businesses with million-dollar ARR.
For those of us who are seasoned enough to have been working for decades in both Software Development and Digital, we know the risks associated with vendor lock-in.
Case studies of this risk don’t come as perfect as Builder.ai, which at one point had a $1.5B valuation and was publicly backed by Microsoft but which turned out to be the other kind of AI (700 Actual Indians working behind the scenes).
Here are my key takeaways:
- Creative Effort — If you’re using AI in your Content Management System to generate AI content, you’re barely scraping the bottom of the barrel. I’m not sure I’d even call it low-hanging fruit. How about we call it the least creative effort?
- Portability & Contingency — Are vibe coders and AI hustlers doing any due diligence? Microsoft sure wasn’t. What about contingencies? How about a platform that is already open source so that if or when your preferred or overvalued low/no-code platform collapses, you have portability and contingency?
- Ethics — AI brings this challenge to the forefront. Are we just creating unsustainable digital pollution? This is the age of authenticity, so authentic Open Source companies backed with communities have value.
- Can we pivot? Because everything is about to pivot and adapting, leading well, and bringing that community with you is quite a challenge.
Categories
