devopsy.kinsta.cloud

Tag: GenAI

Revolutionizing CI/CD: A Framework for Integrating Generative AI Across the Software Delivery Lifecycle
As a DevOps expert, I’ve witnessed firsthand the transformative power of automation and continuous improvement. Today, I’m excited to share a framework that takes our practices to the next level by integrating generative AI into the software delivery lifecycle. This approach not only streamlines our processes but also enhances the quality and efficiency of our deliverables.

The Gen AI-Powered CI/CD Framework

Here’s a step-by-step guide to building and implementing a generative AI framework for CI/CD:

Automated Code Generation and Review
1. Implement GitHub Copilot or Amazon CodeWhisperer for AI-assisted coding.
2. Use AI-powered static code analysis tools like SonarQube or Amazon CodeGuru Reviewer.
Action: Integrate these tools into your IDE and Git workflows, such as GitHub Actions.

Intelligent Test Generation
1. Leverage tools like Diffblue Cover for automated test case generation.
2. Use AWS DevOps Guru to identify areas needing additional testing based on historical data.
Action: Implement AI-generated tests in your test suites and CI pipelines.

Dynamic Infrastructure Provisioning
1. Utilize AWS CloudFormation or AWS CDK with AI-enhanced templates.
2. Implement predictive scaling using Amazon EC2 Auto Scaling with ML-powered forecasting.
Action: Create AI-driven IaC templates and integrate them into your deployment processes.

Automated Security Scanning
1. Integrate Amazon Inspector for AI-powered vulnerability assessments.
2. Use AI-enhanced SAST/DAST tools like Snyk, Checkmarx, or Veracode.
Action: Implement these scans in your CI/CD pipeline, triggered by code commits.

Intelligent Deployment Strategies
1. Implement AI-driven canary deployments using AWS CodeDeploy.
2. Utilize Amazon SageMaker to build ML models for predicting deployment success.
Action: Integrate these predictive models into your deployment decision-making process.

AI-Enhanced Monitoring and Alerting
1. Leverage AWS CloudWatch with AI-powered anomaly detection.
2. Implement predictive alerting using tools like Datadog or New Relic’s AI capabilities.
Action: Set up AI-driven alert thresholds and automated incident response workflows.

Continuous Feedback and Optimization
1. Use AI to analyze user feedback and application logs (AWS Comprehend for sentiment analysis).
2. Implement ML models to correlate code changes with performance metrics.
Action: Create dashboards that visualize AI-derived insights for continuous improvement.

Documentation and Knowledge Management
1. Utilize GitHub CoPilot or AWS CodeWhisperer to generate and update documentation automatically.
2. Implement AI-powered chatbots for internal knowledge sharing.
Action: Set up automated documentation pipelines triggered by code or configuration changes.

Implementation Strategy
1. Assessment: Evaluate your current CI/CD pipeline and identify areas where AI can add the most value.
2. Tool Selection: Choose AI-powered tools that integrate well with your existing stack. Consider AWS services for seamless integration if you’re already in the AWS ecosystem.
3. Pilot Project: Start with a small, non-critical project to test your AI-enhanced CI/CD framework.
4. Training: Upskill your team on AI concepts and the new tools you’re introducing.
5. Gradual Roll-out: Implement the framework in phases, starting with code generation and review, then moving through testing, deployment and monitoring.
6. Measure and Iterate: Use metrics like deployment frequency, lead time and change failure rate to assess the impact of your AI-enhanced pipeline.
7. Scale: Once proven effective, scale the framework across all your projects and teams.
Challenges and Considerations
- Data Privacy: Ensure that your AI tools comply with data protection regulations.
- AI Bias: Regularly audit your AI models for biases in code suggestions or deployment decisions.
- Over-reliance: Maintain a balance between AI assistance and human expertise.
Conclusion

Integrating generative AI into your CI/CD practices isn’t just about adopting new tools — it’s about reimagining the entire software delivery lifecycle. This framework provides a roadmap for leveraging AI to enhance every stage of your pipeline, from code generation to deployment and monitoring.

By implementing this framework, you’re not just optimizing your current processes; you’re future-proofing your DevOps practices. The combination of AI-driven insights and human expertise will lead to faster, more reliable software delivery and ultimately, better products for your end-users.
June 30, 2025
The Future of Application Development in the AI Era

The artificial intelligence (AI) hype has yet to fade. As the technology continues to make headlines, attention is focused on the impact and value AI could deliver for teams, companies and the wider industry.

One of the main questions for those in software development is: Can AI replace human coders?

Despite impressive strides in AI-driven tools, human developers remain essential —though their role is evolving.

Today, 34% of IT leaders report that their organizations use AI-assisted coding extensively, according to The Low-Code Perspective. Meanwhile, nearly half the respondents(47%) are in the experimental phase.

Low-code platforms and AI advancements are creating new opportunities and responsibilities for those involved. Yet, understanding how to make the most from AI-powered low-code requires clarity on the skills and expectations needed from employees.

Let’s take a closer look at the future of application development in this new era of AI — from training teams to navigating stakeholder involvement.

AI Won’t Replace Developers; It Will Help Evolve Their Role

Generative AI (GenAI) tools, such as ChatGPT and Copilot, are currently being used to suggest code snippets, troubleshoot errors and even complete functional code blocks based on prompts.

The role of GenAI in application development is to automate repetitive tasks and reduce low-value activity, but the technology is quickly evolving.

Soon, we could start seeing GenAI work as a co-worker alongside developers. For example, instead of crafting a data model manually, GenAI could assess a requirements document, an existing data schema or an idea formulated in natural language and populate a data model that can then be validated by a developer. The same applies to the generation of user interfaces: Rather than developing UIs from scratch, developers can upload designs or even low-fidelity drawings from a whiteboard session and generate pages that can then be refined.

For some, the productivity benefits of GenAI, as it continues to evolve, pose a question as to whether there is still room for low-code in the future.

Visual development, such as low-code, provides an arena that is not often available to organizations, as it enables people from multiple disciplines to build applications in an environment where everyone understands what’s going on behind the scenes. Not only does GenAI facilitate visual development at pace, but it also increases the speed of the entire development lifecycle when applied to a low-code platform.

AI-assisted low-code paired with skilled developers can unearth significant benefits. Of those surveyed, 85% believe combining AI and low-code would help their organization innovate faster. And 82% say it helps their organization innovate at scale.

Eventually, we will likely see the role of the developer become more of a composer, overseeing the work completed autonomously by virtual software agents. Developers will focus on the management and correction of applications rather than the heavy lifting.

Unlike AI, human expertise can handle nuances to create purpose-driven applications. For instance, understanding user requirements, anticipating potential system failures and integration with existing IT assets are just a few areas where human developers will remain critical. So, as we continue to integrate the technology into application development, it won’t eliminate the need for skilled coders — it will reshape it.

Stakeholder Support for AI is the Next Big Hurdle

We uncovered that a massive 84% of IT leaders say low-code empowers more people to be involved in app development. Yet, 41% report their C-suite lacks the technical knowledge to understand the potential of low-code for their organizations.

Navigating stakeholders is an ongoing consideration for technical teams, whether that is securing buy-in for vital technologies or unlocking future funds to fulfil the development roadmap. Yet, IT leaders are unearthing tension between their goals and those of their stakeholders.

This is concerning, considering that IT leaders report their chief operating officer (COO) as the topmost involved member of the C-suite when making decisions about low-code adoption. And the chief executive officer (CEO) is second.

As non-technical C-suite stakeholders become increasingly important decision-makers in IT capital expenditures and programs, continued conversations between these two stakeholder groups will help create a fuller understanding of low-code benefits.

In the pursuit of easy-to-use applications, businesses can mistakenly assume that low-code and AI tools eliminate the need for technical knowledge altogether — a fear that nearly two in five IT leaders share, with 39% believing their non-technical C-suite wants to use low-code to replace developer talent.

As the lines blur between non-technical and technical leaders in the IT space, goals must be aligned, with the right people in place, so everyone is on the same page for technology investments to be effective.

The Future of AI and Low-Code is Collaborative

Low-code platforms are already facilitating app creation by less technical developers, while AI tools are making coding faster and more efficient. There is a future on the horizon where low-code and AI operate in tandem, allowing developers and stakeholders to collaboratively design and deploy applications.

But the AI skills gap is widening, and today’s developers are expected to keep up. AI, used in conjunction with a powerful enterprise-grade low-code platform, holds significant potential to help bridge this gap when harnessed accessibly for smarter, faster development.

Ultimately, committing to improving productivity and enhancing developer experience is vital for businesses to stay competitive, and that means providing teams with the right tools to make development faster and more efficient. That way, tech teams can focus more on collaborating with the wider organization and problem-solving with accessible tools at the ready.

As organizations move forward, it will be essential to foster collaboration, ensure clarity in roles and encourage ongoing learning.

The true potential of AI and low-code is not in replacing coders but in empowering them. It not only accelerates development but also enables stakeholders to contribute more directly while helping organizations adapt dynamically in a rapidly evolving tech landscape.

June 11, 2025
How DevOps Strategy Is Evolving with Jim Cassens

Perforce Software CEO Jim Cassens dives into how the company’s overall approach to DevOps is evolving in the wake of a series of acquisitions.

Cassens talks through the company’s recent spate of acquisitions and how thoughtful integration—not just portfolio expansion—is driving value for customers. He also highlights the growing role of synthetic data, AI-enhanced testing and how automation is shifting the responsibilities of development teams.

A recurring theme is how generative AI is disrupting—not replacing—traditional developer roles. Cassens sees AI as a force multiplier, taking on repetitive, low-level tasks while freeing developers to focus on higher-order problems. But with that shift comes a challenge: How do early-career engineers gain the hands-on experience they need when entry-level work is being automated? That’s a question Cassens believes employers, not just universities, will need to answer.

They also delve into the pressure DevOps teams face as pipelines become more brittle and overloaded. Cassens warns that the current approach to automation and scripting isn’t sustainable in a world where AI can flood pipelines with code at unprecedented volume. Organizations will need to rethink how they structure CI/CD, data management, and even pipeline observability.

Finally, Cassens touches on the human element behind every digital transformation. As leaders weigh new tools and AI-powered workflows, he advises them to consider the fear and uncertainty many team members may be feeling—and to support them through education and open communication. The DevOps landscape may be changing fast, but people, not just platforms, will determine how successful the transition is.

June 10, 2025
Scaling Vibe-Coding in Enterprise IT: A CTO’s Guide to Navigating Architectural Complexity, Product Management and Governance
Enterprise IT organizations increasingly explore innovative approaches such as vibe-coding, a practice that leverages AI-driven tools and large language models (LLMs) to prototype and develop software with minimal traditional coding rapidly. Vibe-coding prioritizes functionality, user experience and iteration speed over strict adherence to conventional software engineering methodologies.

The timing is no coincidence. The surge in accessible, high-performance LLMs, alongside AI code assistants like GitHub Copilot and integrated APIs from OpenAI and Google, has lowered the barrier to entry for building intelligent applications. What once required full-stack developers can now be initiated by analysts, architects and subject matter experts.

While vibe-coding initially promises accelerated innovation and simplified development, scaling it across broader, less technical audiences introduces significant complexity, governance risks and operational challenges. Using the evolution of the CTO Signal Scanner application as a detailed case study, this report helps CTOs understand the intricate balance required to scale vibe-coding effectively and sustainably.

Initial Exploration: Prototyping With Intent

We didn’t start by chasing a product. We began by exploring a possibility. The goal was simple: Could an AI-enhanced CLI tool help an enterprise IT analyst track vendor signals more effectively?

That first version was exactly what it needed to be: A lightweight proof of concept written in Python with OpenAI integration. A fast way to test value. The command-line interface was the fastest path to signal, and it confirmed what we suspected: Generative AI could add immediate value in surfacing insights from routine vendor updates.

This wasn’t naive code-gen play. It was deliberate prototyping, vibe-coding in its best form: Small, sharp and curiosity-led.

Scaling Delivery: From CLI to Web Interface

Once the initial PoC proved valuable, we needed to expose it to a broader audience. The obvious next step was a web interface. Since we began in Python, extending it with Flask seemed logical, it let us stay close to the original codebase.

But this is where architectural momentum can become architectural friction.

In hindsight, this was the point where a more production-minded architectural lens could have shifted the trajectory: Python + Flask may feel familiar, but modern frontend gravity has clearly consolidated around React and TypeScript. The developer ecosystem, the agentic tooling and even model pre-training patterns align more naturally with the React + Firebase + TypeScript world.

That choice matters because the deeper your AI-assisted dev stack aligns with prevailing patterns, the more you can leverage the weight of pre-trained behavior.

Two Paths of Vibe-Coding: The Architect vs. the Enthusiast

This highlighted something important: Not all vibe-coding is created equal.

There’s the path of the expert system architect or senior SWE, using AI tools as force multipliers, prompting multiple agents, testing architectural forks and evaluating tradeoffs at speed. That’s a fundamentally different mode than a former developer or business analyst casually asking for features via a prompt and shipping the result unchecked.

Both of these approaches wear the same label, vibe-coding, but the workflows, risks and output quality are worlds apart.

It’s time we acknowledge that duality. One path is building the future. The other? Potentially repeating the sins of Lotus Notes and shadow IT with turbocharged tooling.

Enterprise Implication: What’s Actually Changing?

Vibe-coding, in the enterprise context, isn’t about replacing developers. It’s about changing the shape of the developer experience and putting more strategic pressure on architectural leadership.

The real bottleneck is no longer how quickly we can write code. It’s deciding what to build, what shape it should take and what’s operationally sustainable.

In this way, code-gen has revealed a hidden truth: There is now a premium on deep technical experience. Because if machines can write code, the critical skill isn’t the keystroke, it’s the decision tree behind it.

Strategic Pivot: SPA and Serverless Architecture

Acknowledging that microservices were overly complex, the team pivoted towards a React Single Page Application (SPA) with Google’s Firebase backend services, significantly reducing complexity and operational overhead:
- Frontend (React SPA): Leveraged React and Tailwind CSS for responsive, scalable and maintainable frontend development.
- Backend (Firebase): Utilized Firebase Authentication, Firestore and Cloud Functions to simplify backend processes, reduce complexity and improve integration.
- AI Integration (Gemini API): Centralized Cloud Functions optimized API usage, streamlined caching and maintained scalability and reliability.
Architecture Economics: Inference Latency, Unit Costs and Hosting Tradeoffs

As the application matured, the team encountered two major architectural forks — each tied directly to the economics and operational realities of AI at scale.

Inference Model Infrastructure: Hosted vs. Local

Initially, the Signal Scanner leveraged OpenAI’s APIs to rate and summarize articles. However, early tests showed that there was no material quality difference between OpenAI’s responses and outputs from open-source models like LLaMA or Mistral. The key differentiator turned out to be latency.
- OpenAI’s hosted models consistently returned responses in under three seconds.
- Local models, including SoC GPU(M2-Pro)-accelerated, returned results in five to 20 seconds, depending on cold start behavior and load conditions.
Strategic Insight: This is the token economy NVIDIA’s Jensen Huang refers to — AI workloads must be judged not just by compute cost, but by unit economics: latency, reliability and engineering overhead per insight.

For our use case, real-time responsiveness, OpenAI’s hosted infrastructure provided the latency profile we could not match internally without investing in GPU-backed environments in a data center or the public cloud.

Backend Infrastructure: Firebase vs. Kubernetes

The second decision was backend infrastructure. Should the application be deployed on Kubernetes (e.g., GKE, OpenShift) or Firebase?

Kubernetes offered:
- Predictable cost structures via reserved resources.
- Alignment with existing observability and security models.
- Long-term operational control.
Firebase offered:
- High developer velocity for small, fast-moving teams.
- Built-in authentication and real-time database.
- Less predictable costs due to usage-based billing.
Firebase reduced our initial backend development time by over 60% compared to building and securing a Kubernetes deployment, though cost forecasting became significantly more variable beyond the first 10k users.

Enterprise Consideration: Firebase prioritized delivery speed over cost control. It was the right choice for our current maturity level, but came with active monitoring and reversibility planning if costs grew beyond thresholds.

The Hidden Complexity: Backend Infrastructure Considerations

A significant challenge arose from backend infrastructure, often overlooked by vibe coders focused purely on frontend features:
- Non-experienced Vibe-coders rarely consider differences in backend storage (MySQL vs. NoSQL) or orchestrating backend services (API gateways, Kubernetes choices).
- Decisions around OpenShift, VMware Tanzu, or Kubernetes dramatically affect backend integration complexity, operational costs and frontend responsiveness.
Real-world Backend Challenge:
Accurately depicting the real-time processing status of AI article analysis (varying from seconds to minutes) proved difficult within the monolithic Flask setup. Transitioning to a React SPA architecture with Firebase backend seamlessly addressed these complexities, improving user feedback, reducing integration challenges and enhancing operational simplicity.

Product Management: Avoiding “Lotus Notes Syndrome” and Snowflake Complexity

Standing up and scaling vibe-coding centers of excellence for non-traditional application developers in enterprise environments demands rigorous product management discipline. Unchecked expansion of AI tools to general employees can repeat historical enterprise errors, generating fragmented systems, unmanaged technical debt and questionable ROI.

Historical Lessons:
- Lotus Notes Syndrome: Decentralized departmental workflow optimization initially accelerated productivity but eventually resulted in significant operational complexity and technical debt.
- Cloud Sprawl: Developers’ unrestricted cloud usage produced customized “snowflake” environments, hindering central support and operational management.
A Fortune 100 COO underscored that simply providing general employees with AI tools, without structured oversight, often leads to unintended consequences, operational fragmentation and long-term inefficiencies.

Structured Product Management Recommendations:
- Centralized AI Governance: Clearly defined committees or roles responsible for aligning AI tools with enterprise standards and objectives.
- Explicit Architectural Standards: Providing vibe coders with clear guidelines and reference architectures for consistency and interoperability.
- Disciplined Feature Scope Management: Evaluating each requested feature rigorously against strategic business objectives and potential complexity.
- Regular Technical Debt Reviews: Scheduled assessments to explicitly manage and mitigate AI-generated technical debt and maintainability concerns.
Nuanced Governance Challenges at Scale

Scaling vibe-coding practices across broader, non-technical audiences requires proactive governance adjustments:
- Architectural Consistency: Preventing non-technical vibe coders from creating inconsistent interfaces and fragmented backend integrations.
- Technical Debt Management: Explicit processes for reviewing, documenting and managing AI-generated code quality and maintainability.
- Security and Compliance: Comprehensive training and rigorous oversight to ensure adherence to enterprise-grade security and regulatory compliance.
- Ethical AI Use: Clearly communicated ethical guidelines for responsible AI deployment, avoiding inadvertent ethical breaches.
Cultural and Organizational Considerations

Successfully scaling vibe-coding also requires careful attention to organizational and cultural factors:
- Skill Development: Structured training emphasizing foundational software development and AI-specific skillsets (prompt engineering, AI integration best practices).
- Psychological Safety: Cultivating an environment supportive of iterative experimentation, learning from failures without punitive repercussions.
- Managing Cognitive Load: Ensuring developers maintain technical depth and avoid burnout amid rapid AI-assisted iteration cycles.
Key Lessons for CTOs Scaling Vibe-Coding
- Clearly understand operational and financial motivations behind architectural shifts.
- Transition cautiously from local, prototype-driven architectures to centralized, enterprise-grade infrastructures.
- Carefully evaluate architectural decisions based on practical ROI considerations, not just prevailing industry trends.
- Maintain rigorous product management discipline, explicitly managing scope and complexity to avoid operational fragmentation.
- Proactively address governance, security, compliance and technical debt management, particularly when scaling vibe-coding to general or non-technical audiences.
Conclusion

Effectively scaling vibe-coding within enterprise IT requires nuanced decisions regarding architecture, governance, product management and culture. The evolution of the CTO Signal Scanner vividly illustrates the complexities inherent in scaling from simple prototypes to enterprise-ready, centralized applications. By embedding rigorous product management, structured governance, clear architectural guidelines and cultural support, CTOs can harness the rapid innovation potential of vibe-coding without repeating historical enterprise pitfalls. This strategic, disciplined approach ensures long-term operational efficiency, technical stability and sustainable ROI for enterprise IT organizations.
June 9, 2025
How to Elevate DevOps Training and Testing With Generative AI
Everyone is talking about artificial intelligence (AI). More specifically, they are buzzing about generative artificial intelligence (GenAI), the chatbots with the perceived potential to usher in a universal utopia or destroy the world (depending on who you talk to).

These extremes are speculative at best, foretelling an uncertain future shaped by GenAI.

In the meantime, GenAI tools, like ChatGPT, Claude, Gemini and the countless other models popping up daily, are good coders.

In fact, they are really good coders.

More specifically, it is a good coding assistant. One study found that GenAI increases coders’ productivity and capabilities, expanding their aptitude for new data science tasks, even without prior experience in coding or statistics.

However, in 2025, we don’t just need more software. We need safer software that is resilient against even the most pernicious cybersecurity threats, putting companies and customers at risk.

For small startups and major corporations, this places increasing importance on DevOps and software development skills, training and certification.

This is where GenAI can really help companies. In addition to producing new code, it can enable companies to teach their tech teams how to protect sensitive data, maintain regulatory compliance and mitigate emerging security risks at scale.

Training and Testing Development is Difficult

DevOps teams need cutting-edge training and testing to prepare them for increasingly sophisticated and constantly emerging cybersecurity threats.

Creating training and testing programs that provide actionable information and don’t just check boxes and waste time is time-consuming, labor-intensive and expensive.

To produce truly effective training programs, in-house or third-party certification programs rely on a rigorous and systematic process involving iterative processes with subject matter experts (SMEs) and other experts who use their experience and expertise to guide content development.

Test creators leverage their insights to generate training material and test items, which are subsequently reviewed by a panel of SMEs, who modify these draft questions for accuracy, appropriateness, difficulty and relevance.

It’s a workflow ripe for new efficiencies that make creating high-quality training and testing materials more agile and responsive while controlling costs and improving consistency.

This is where GenAI can help companies streamline and enhance this complex workflow.

GenAI in DevOps Testing and Certification

GenAI offers compelling DevOps training and certification opportunities but also presents unique challenges.

For example, the technology’s ability to understand and generate natural language allows for the creation of realistic and engaging test scenarios. At the same time, GenAI can enhance and simplify spell-checking and grammar correction, ensuring the accuracy and professionalism of test items while making it more feasible to continuously create and improve training and testing content as the DevOps and cybersecurity field continues to change.

Taken together, GenAI offers a cost-effective solution for test development, potentially reducing the resources required for manual test creation.

To be sure, these are productivity and cost-control improvements, not full-scale automation because the technology still poses unique risks and challenges for certification programs. This includes:
- Accuracy and Reliability: GenAI platforms still make mistakes, hallucinating and confidently presenting wrong information as right.
- Bias: GenAI models can inherit biases from their training data, leading to unfair or discriminatory test content.
- Security and Privacy: Using commercial GenAI products can make it difficult to protect the security and privacy of sensitive test and test-taker data.
- Rapid Evolution: GenAI technology is both novel and rapidly changing, making it difficult for companies to keep up with the rate of change and the implications for their work.
- Legal Uncertainty: There is still uncertainty about the copyright status of AI-generated content.
Perhaps most prominently, because GenAI technology is still so new, its greatest strength and most significant shortcomings are probably still being discovered.

In response, assessment creators must stay adaptable and proactive, modifying their strategies to capitalize on GenAI’s advantages and minimize its drawbacks as the technology evolves.

Best Practices for Implementing GenAI in DevOps Testing and Certification

To harness the full potential of GenAI while mitigating its risks, several best practices can guide organizations in creating effective and responsible AI-powered testing and certification programs.

#1 Treat GenAI as an Assistant

Use AI to augment human expertise, not replace it. Subject matter experts should work alongside GenAI tools to ensure the quality and relevance of test content.

For example, GenAI can create practice tests or question variants that benefit the overall testing experience but don’t undermine expertise or production quality.

#2 Focus on Quality Control

Inaccurate training is the same as no training at all. When using GenAI tools to support training and test creation, robust quality checks ensure the accuracy, fairness and relevance of AI-generated content.

That’s why human review and validation are essential to integrating GenAI into the content creation process.

#3 Prioritize Data Security

Protect the privacy and security of test-taker data and sensitive test content. Use secure platforms and tools that comply with relevant data privacy regulations.

Put differently, don’t just put your test information into ChatGPT. Instead, leverage third-party tools that protect privacy and prevent your data from entering the public domain.

#4 Get Good at Prompt Engineering

Effective prompt engineering, which involves designing and refining input prompts to optimize GenAI model performance, is necessary for creating high-quality exam assets.

#5 Commit to Continuous Improvement

Continuously evaluate and refine the use of GenAI in testing and certification processes. Monitor the effectiveness of AI-powered tools and adapt strategies as needed.

Enhancing Security and Productivity With GenAI

Undoubtedly, GenAI can help organizations develop and validate the skills needed to build and maintain secure and reliable software.

Even so, training and test creators will need to integrate the technology thoughtfully and intentionally, addressing potential challenges and prioritizing data security and quality control.

Organizations can leverage GenAI to enhance their DevOps training and certification programs by embracing these best practices and remaining adaptable.

The result? Meaningful progress toward a more secure and efficient software development lifecycle.
June 3, 2025
AWS Previews GitHub Integration for Amazon Q Developer

Amazon Web Services (AWS) is expanding the DevOps platforms its generative artificial intelligence (AI) agents for application developers are integrated with to now include GitHub code repositories.

Available as a public preview, Amazon Q Developer can now be directly deployed on top of GitHub to enable DevOps teams to automatically, for example, review code, assign GitHub issues to an Amazon Q development agent that will then create an entire new feature for an application or migrate a code base to the latest version of a programming language.

Adnan Ijaz, director of product management for developer agents and experiences at AWS, said that since the launch of Amazon Q Developer, many application developers have extended the scope of the AI agents provided beyond writing code. AWS is now following that example to enable a wider range of software engineering tasks to be automated directly via a command line interface (CLI) or either a VS Code or JetBrains integrated development environment (IDE), he added.

The overall goal is to assign as many rote tasks as possible to autonomous AI agents that have been specifically trained to perform them, said Ijaz. In time, those AI agents will not only be able to complete tasks but also identify tasks that should be done based on what’s occurring across the software development lifecycle (SDLC), he added.

Regardless of the number of tasks assigned to an AI agent, however, there will continue to be a need for human oversight to ensure those tasks are completed as intended, said Ijaz.

Exactly how much AI agents are now being used to build software is unclear, but a Futurum Group research survey finds 41% of respondents now expect generative AI tools and platforms will be used to generate, review and test code. The one certain thing is that the volume of code being created is going to continue to increase exponentially in the months and years ahead as AI agents are integrated into software engineering workflows. Each organization will, as a result, need to determine for itself to what degree to rely on AI agents to write, review and test code. Right now, the quality of the code being generated by AI tools can vary widely, and in many instances, organizations are rightfully hesitant to deploy code in production environments unless a human developer thoroughly understands how it was constructed.

Nevertheless, as AI coding continues to evolve, the productivity gains are too much to ignore. Application development teams, at the very least, should by now be experimenting with various approaches, especially as it becomes simpler to assign tasks to an AI agent that, truth be told, many software engineers don’t especially enjoy doing themselves.

Ultimately, the pace of AI innovation is only going to accelerate. Before too long, the code surfaced by AI tools will improve. DevOps teams will soon find themselves building, deploying and updating a wide range of applications at levels of scale that a few short years ago might have seemed impossible. The issue now will be determining to what degree the DevOps pipelines currently relied on to manage software development might need to be revamped to accommodate all the code being created by AI agents supervised by human developers.

May 14, 2025
CodeRabbit Adds Support for VS Code to AI Code Review Platform

CodeRabbit today added support for the open-source Visual Studio Code editor to its platform that employs generative artificial intelligence (GenAI) to review code.

Company CEO Harjot Gill said adding support for VS Code will significantly expand the reach of a platform that is already integrated with AI coding tools such as Cursor and Windsurf.

CodeRabbit is primarily used within any Git-based repository to review code as commits are being made. That approach ensures that all code destined for a production environment has been reviewed by an AI platform that is accessed via a natural language chat interface.

Alternatively, application developers can also embed CodeRabbit to review code in real time within the tooling they are using to write code.

The overall goal is to surface routine mistakes in a way that developers can either catch themselves or enable a human reviewer of code to focus on more complex issues, said Gill.

That capability is going to be especially critical in an era where the volume of code being generated using AI tools will far exceed the ability of anyone to manually review that code, he added.

CodeRabbit traverses each code repository in the Git platform, prior to pull requests and related Jira/Linear issues, using a code graph analysis capability that identifies code dependencies across files, and custom instructions using Abstract Syntax Tree (AST) patterns. Used by nearly 5,000 customers to cut the time spent reviewing code in half, CodeRabbit can also pull dynamic data from external sources such as a large language model (LLM) as needed, noted Gill.

Additionally, CodeRabbit will generate crisp summaries of code changes, whether they affect a single line or add an entire new feature.

In contrast, existing code review tools are much more limited, he added. Modern code review cycles require developers to understand not just the quality and behavior of new code that has been generated, but also adhere to coding practices at the organization level and within the syntax of individual programming languages in addition to understanding file dependencies that impact other parts of the code and any conformity to security policies that might be required.

It’s not clear how widely AI is being applied to DevOps workflows, but a Futurum Research survey finds 41% of respondents now expect generative AI tools and platforms will be used to generate, review and test code.

While much of the initial focus on using AI to automate tasks has been on writing code, AI tools that review code will become just as widely adopted, if for no other reason,n code reviews are a task that not many developers enjoy, said Gill. Many organizations have historically set up two-person teams to review each other’s code. Now, more of that time can be allocated to either writing code or fine-tuning the code that might have been generated by an AI tool.

It’s still relatively early as far as the adoption of AI in DevOps workflow, but as more tedious tasks continue to be automated, it’s becoming clear that much of the drudgery that often conspires to slow down the pace of application development will steadily be reduced if not outright eliminated.

May 14, 2025
Zerve Adds AI Agents to Automate DevOps Workflows

Zerve today expanded its platform for visualizing complex IT infrastructure to include multiple generative artificial intelligence (AI) agents capable of planning, provisioning and building IT infrastructure, including the data workflows that developers need to drive applications.

Announced at the Open Data Science Conference (ODSC), the core Zerve Operating System has also been updated to include a distributed computing engine, dubbed Fleet, that enables via single command massively parallel code execution using serverless technology, invoked with a single command.

Designed to be hosted in an on-premises IT environment, the Zerve Operating System, AI agents that Zerve has added are capable of presenting a plan and then generating Zerve canvases by creating and connecting code blocks, writing code, orchestrating infrastructure and automating various parts of the data workflow as needed. If the agents encounter an error or their experiment fails, they will automatically try a different approach.

Zerve CEO Phily Hayes said the overall goal is to provide DevOps teams with a set of AI agents that, via a natural language interface,e can automate many of the manual tasks that previously made provisioning IT infrastructure tedious.

In combination with Fleet, it also becomes possible to more efficiently make multiple calls to large language models, he noted.

It’s not clear how widely AI is being applied to DevOps workflows, but a Futurum Research survey finds 41% of respondents now expect generative AI tools and platforms will be used to generate, review and test code.

In general. AI agents are leveraging the reasoning engines built into large language models (LLMs) to not only determine what line of code or word should come next in a sequence, but also to determine what task should be performed next. The degree to which those tasks can be automated depends on the amount of memory that the LLM and AI agent can provide.

Ultimately, the goal is not to replace software engineers but rather augment with a set of AI agents that make it possible to manage complex IT infrastructure at much higher levels of scale, said Hayes.

At this juncture, there is little doubt that AI agents will be incorporated into DevOps workflows, but each organization will need to determine what level of trust to have in them. Given the probabilistic nature of LLMs, it’s unlikely an AI agent is going to perform the same task exactly the same way every time. However, there is a wide range of DevOps tasks where it may not be especially critical to understand exactly how resources were provided, so much as it is to ensure there was an acceptable outcome.

In other scenarios, however, the way IT infrastructure is provisioned may need to be very precise. While an AI agent can make that task less tedious, software engineers will still need to review those configurations.

Hopefully, AI agents will make being a software engineer more rewarding, in the sense that less drudgery will be experienced. The challenge is determining when and how to onboard AI agents into a DevOps workflow that DevOps teams continue to manage and orchestrate.

May 13, 2025
Sumo Logic Previews AI Tool to Analyze Telemetry Data

Sumo Logic has created a prototype of a generative artificial intelligence (AI) tool that creates text-based summaries from large volumes of log and telemetry data collected by its log analytics platform.

Additionally, Sumo Logic is now also making it possible to deploy detection rules as code, which makes it simpler to incorporate into a DevSecOps workflow.

Sumo Logic is adding an ability to create baselines for user and entity behavior to reduce the number of false positives that are created when relying solely on static thresholds.

Finally, the company is adding support for multiple intelligence feeds by adding support for Structured Threat Information eXpression (STIX) syntax and the Trusted Automated eXchange of Intelligence Information (TAXII) data format.

Chas Clawson, Field CTO for security at Sumo Logic, said collectively these capabilities will help DevSecOps teams keep pace with the increased velocity at which code is now being created using various AI tools. Rather than having to search log data for anomalies, it is now becoming possible to employ AI to create a natural language prompt that generates a summary of actionable insights that surfaces key patterns, extracts relevant context, and highlights likely root causes, he added.

That capability should also help bridge the device that often exists between DevSecOps teams and cybersecurity professionals that, while capable of detecting a vulnerability, often lack the context needed to accurately assess its level of severity, noted Clawson.

It’s not clear how widely AI is being applied to DevSecOps workflows, but a Futurum Research survey finds 41% of respondents now expect generative AI tools and platforms will be used to generate, review and test code. As those tools are incorporated into DevOps workflows, it’s apparent that many of the tasks that conspire to make securing software supply chains a set of tedious tasks that few DevOps teams enjoy. However, if it becomes simpler to not only identify pressing issues but also instantly create and test a patch, the overall state of application security should steadily improve.

Better yet, the number of vulnerabilities being created might eventually decline as application developers take advantage of AI-infused tools that identify issues as they are writing code.

Unfortunately, many developers are now generating code using general-purpose large language models (LLMs) that were trained using examples of flawed code that were randomly collected from across the web, which in the short term means there might be more vulnerabilities finding their way into production environments. However, it’s just as equally possible that many developers who lack security training are now creating higher-quality code thanks to an LLM.

Each organization will need to determine to what degree to rely on AI technologies to automate various tasks and processes, but at the very least, they should be creating a list of tasks that are likely to be automated using AI technologies to better understand where to focus the efforts of their human software engineering resources. It’s not likely AI will replace the need for software engineers, but it should make being one a lot more enjoyable, as more tedious tasks, such as patching applications, are increasingly automated.

May 8, 2025
GenAI in Software Development with Nathen Harvey

Nathen Harvey, DORA Lead at Google Cloud, delves into how generative AI is rapidly reshaping the software development landscape, presenting both exciting opportunities and complex challenges.

Harvey reflects on his own journey, from early web operations and his time at Chef to leading the DORA program after its acquisition by Google. DORA (DevOps Research and Assessment), now in its 10th year, continues to be a definitive source for understanding how technical teams improve performance and value delivery. The program’s annual reports, especially its latest focused on generative AI, offer research-backed insights that are widely used across the industry.

The conversation dives deep into this year’s findings, starting with the rapid and widespread adoption of AI. Nearly 90% of organizations surveyed are prioritizing AI from a top-down perspective, while over 76% of practitioners report already using AI tools daily. This simultaneous push from leadership and uptake by developers indicates that AI isn’t a passing trend—it’s a permanent shift.

But the data reveals nuance. While AI tools are helping improve areas like documentation, productivity and developer satisfaction, there’s also a measurable decrease in software delivery stability and throughput. Harvey suggests that this may be due to larger and more complex change sets generated by AI tools, which clash with workflows optimized for smaller, more iterative updates. In essence, we’re accelerating one part of the pipeline while other parts can’t yet keep up.

Harvey emphasizes the importance of interpreting DORA findings in context—using them as hypotheses to test within each unique organization. He also raises critical questions about workforce development, particularly how AI might reduce opportunities for junior developers to gain real-world experience and grow into senior roles. The future, he notes, will require balance: leveraging AI as an amplifier while still investing in people and process.

The takeaway? AI is transforming DevOps, but not without growing pains. To navigate this shift, organizations need to blend data-driven research with community collaboration, continuous experimentation, and a commitment to developing talent at every level.

April 23, 2025