# Igniton Code Assistant & Analyzer

**URL:** <https://forum.inductiveautomation.com/t/igniton-code-assistant-analyzer/98439>\
**Category:** Ignition\
**Created:** [November 10, 2024, 10:07am UTC](https://forum.inductiveautomation.com/t/igniton-code-assistant-analyzer/98439 "2024-11-10T10:07:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thidalgo](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@thidalgo](https://forum.inductiveautomation.com/u/thidalgo)\
**Post date:** [November 10, 2024, 10:07am UTC](https://forum.inductiveautomation.com/t/igniton-code-assistant-analyzer/98439/1 "2024-11-10T10:07:17Z")

</div>

Hi all,  
I'm thinking on boosting my development team with Code Assistants and Code Analysis tools. What are the most suitable for working with Ignition from your point of view ?  
Thanks.

---

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [November 10, 2024, 2:00pm UTC](https://forum.inductiveautomation.com/t/igniton-code-assistant-analyzer/98439/2 "2024-11-10T14:00:08Z")

</div>

Our stack is the following:

- **Code Analysis** : SonarQube, with Gitlab pipelines.
- **Code Assistance** : Microsoft Copilot or ChatGPT.

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [November 10, 2024, 5:10pm UTC](https://forum.inductiveautomation.com/t/igniton-code-assistant-analyzer/98439/3 "2024-11-10T17:10:45Z")

</div>

> [@thidalgo](#):
>
> Code Assistants

I haven't seen a code assistant that can reliably provide solutions for Ignition.  
When I'm training people who are new to scripting in Ignition, I show them how to navigate the Java and Ignition documentation, and I advise them to study the docs and take the time to really get their head around what they trying to do--especially when they are working on something they haven't done before. If your development team consists of seasoned veterans, perhaps something like gpt will be useful for roughing in sections of code, but if your team is just starting out or is in unfamiliar territory with a given project, I recommend steering clear of that approach.
