AI Restrictions Are Driving Open Source Growth in Enterprise Development

Staff Reporter

Restrictions on using AI tools in enterprise and government projects are changing how developers structure code, according to a LinkedIn post published on 18 March 2026 by Alex Skrypnyk, Director at DrevOps. He argues that when AI cannot be applied directly to client code due to policy or compliance concerns, developers increasingly extract generic functionality into standalone open source modules.

This approach separates reusable logic from sensitive implementations. Developers build general-purpose modules without client data or proprietary constraints, while keeping integration layers private. Although this pattern predates AI, the post states that restrictions are accelerating its adoption by making extraction the most practical way to maintain development efficiency.

Once code is moved into open source, AI tools can be applied without restriction to improve documentation, testing, and refactoring. The post also questions whether AI policy should focus on how code is generated, arguing instead for emphasis on quality controls such as testing, code review, and standards. The broader effect is an increase in new open source modules, as more generic functionality is published by default rather than after the fact.

Reference: Are AI Restrictions Actually Growing Open Source? by Alex Skrypnyk, DrevOps (18 March 2026)

Open Source

Developer Workflow

Drupal ecosystem

Software Development

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

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.