What Two Developers Taught Me About Drupal Outside Web Summit

Why Shared Code and Established Frameworks Matter for AI-Generated Applications
The Drop Times opinion graphic features a stepped brick wall and tangled lines beside organized blue blocks. The headline explores lessons about Drupal learned from two developers outside Web Summit.

In Lisbon, the most useful conversation happened away from the stage. It was about trust in the code we ship, and it points to a big opening for Drupal.

Web Summit was wrapping up, and I was on my way out, waiting at the airport, when I found myself watching ads for Jira, AI companies and remote hiring platforms. When airport advertising is aimed squarely at tech workers, you get a sense of how many companies and developers have just spent the week in Lisbon.

Looking back, the second day was already telling. A severe storm was forecast, and the warnings were serious. Portuguese authorities advised Web Summit to suspend its programme, schools and non-essential services were set to close, and the venue doors closed too. The event was cancelled for the day on government advice.

But some of us still found ourselves outside, talking in the spaces around the event.

Lisbon was full of tech people, in herds. You could hear it everywhere: new ideas, new products, the usual talk of revolutions. But some of the most interesting conversations were happening outside the venue, away from the stages.

One caught my attention. Two people, clearly developers or very close to it, were discussing something sobering and genuinely interesting: trust. Trust in the code you write. Trust in its security. And trust in simply knowing what is in there.

That is a big topic, and one where Drupal can capitalise.

Why Drupal?

I have thought of Drupal as a low-code platform for a long time, well before everyone went crazy about low code. I gave a talk on this at DrupalCon Europe 2020, in the Amsterdam room, about low code and Drupal's role in it: “Low code, past, present and future.”

Generating thousands of lines of code is not sustainable from a trust, security or maintainability point of view. This is where frameworks matter enormously. Symfony and its peers will play a huge role, and Drupal has the same opportunity if we take it.

The key idea

If you ask an AI agent to just build something, it can go away and come back with thousands of lines of code that nobody can realistically manage.

Instead, tell it to use a framework, Drupal included. Ask it to write as little custom code as possible, use suitable contributed modules where they fit, and follow the framework's best practices.

I experimented with this over the past few weeks. First, I gave an AI agent the customer requirements, without technical direction, and asked it to build an application. The result was a JavaScript app with hundreds, perhaps thousands, of lines of code. Do I trust that code? Honestly, I did not even know what was in there. I would have struggled to make changes or add features myself.

In a second experiment, I started with the same user and business requirements, but added my own experience and thoughts about how the application should be built. Use Drupal. Use as few custom modules and as little custom code as possible, or none if the requirements allow it. Prefer suitable contributed modules and follow Drupal best practices.

The result was an application built on Drupal and community-contributed code that I could inspect, understand and extend myself, without relying on AI for every change or investing a huge amount of time just to understand the codebase.

That does not mean every contributed module should be trusted automatically. We still need to assess dependencies, review changes and keep software maintained. The difference is that we can start from an ecosystem of shared code and established patterns, rather than asking an agent to invent everything from scratch.

What we need to do

So what is the ask? Agents and AI tools need to learn that there are better ways to build, and the community needs to say so loudly and in many formats.

I am not talking about making more videos that are only about Drupal. I am talking about creating useful content that solves real problems with technology. Show different frameworks and languages where they make sense, then demonstrate how Drupal can help as part of the solution.

People may not be looking for a specific technology to save them. They are looking for a way to fix problem A, B or C. Let us start with the problem, show a useful solution, and let Drupal's role speak for itself.

It is the same idea as bursting the bubble: go where people are already meeting, beyond our own community. Web Summit is one example. Marketing conferences are another. Propose talks, build useful demonstrations, and write content that helps AI tools and search engines surface Drupal to people outside the Drupal bubble.

For some of this work, stop putting Drupal in the title or making it the main topic. Focus on the problem, then introduce Drupal as part of the answer.

If you want ideas for contributing to the new Drupal Advocacy Program, here are a few:

  • Create videos showing agents building with Drupal and contributed modules.
  • Write blog posts about your own experience.
  • Speak at DrupalCamps and DrupalCon.
  • Recruit more people to do the same.

What’s next for me

As you may know, I have been talking about the Drupal bubble for a long time. Now we are doing something about it. When Dries announced the Advocacy Program in his DrupalCon Rotterdam keynote, I felt proud and encouraged.

Now it is time for me to help others amplify the message while I focus on doing the work. I will not be giving more talks or keynotes about the Drupal bubble for now. Instead, I am sharing my slides and notes with the community, starting with Mike Anello, who proposed this idea after my keynote at DrupalCamp Italy. I will let others continue that work and focus on what I enjoy most: communication, sharing and evangelising about Drupal.

If you want to help, get in touch and let’s talk.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Related Events

Related People

Upcoming Events