Skip to main content

Finding your way in the AI landscape

The AI development landscape is evolving at an astonishing pace, with new tools emerging every day across every aspect of the development process. Whether you're fine-tuning models, optimizing deployment, or managing infrastructure, the ecosystem keeps expanding with innovative solutions.

Everyday I hear a colleague talk about a new and exciting tool. But how can you ever keep up with this ever growing list? The team behind AINativeDev created a guide to the AI development ecosystem.

A guide to the AI development ecosystem

With 244 tools currently featured, this curated landscape offers insights into how AI development is being shaped across various domains, including:

  • Prompting Tools – Enhancing AI interactions with structured prompts.

  • Code Editors & Review Tools – Helping developers write, test, and optimize AI-integrated code.

  • Autonomous Agents – Tools designed to automate coding tasks and enhance workflows.

  • Model Benchmarking & Observability – Ensuring models perform efficiently while staying transparent and accountable.

  • Frontend & Mobile AI Development – Supporting AI-driven user interfaces and mobile experiences.

  • Security & DevSecOps – Addressing vulnerabilities and fortifying AI systems against risks.

Spotlight on innovation

In this list there are a few standout tools I tried myself and I would recommend further exploring:

  • GitHub Copilot – The AI editor for everyone. The OG IDE extension that first brought us completions.

  • Cursor- The AI Code Editor. Built to make you extraordinarily productive, Cursor is the best way to code with AI.

  • Bolt – AI-powered code generation. Prompt, run, edit, and deploy full-stack web apps.

  • Aider– AI pair programming in your terminal. (I especially like the ‘architect’ mode)

  • Pulumi Copilot – Bringing AI into Infrastructure as Code solutions (Still investigating but looks really promising).

Future trends in AI development

Based on the list of available tools we can already see some trends:

  • A large part of the ecosystem focusses on the coding and QA part of the SDLC.
  • We're seeing niche solutions for everything—from frontend AI integration to DevSecOps, observability, and even autonomous coding agents. This specialization reflects how AI is deeply embedded into different aspects of software engineering.

As AI becomes more integrated into software development, ’we’re likely to see:

  • Increased adoption of autonomous coding agents that streamline development.

  • More advanced observability tools that improve transparency and debugging.

  • A surge in AI-powered security solutions to tackle vulnerabilities in real-time.

Have you explored any of these tools? Feel free to contact me to share your experiences.

More information

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...