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

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

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.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more