I had an ESP32 on my desk, a breadboard full of jumper wires, and the Arduino IDE open. The code compiled. The serial monitor worked. And I hated every second of it.
The Arduino IDE is fine for a blinking LED. It is not fine for a project with multiple source files, libraries, and any kind of structure. No refactoring. Code completion is basic compared to a full C++ IDE. No way to navigate between definitions. I kept switching back to IntelliJ to think, and then back to the Arduino IDE to upload.
So I built a plugin
Flexible for Arduino brings the Arduino workflow into JetBrains. Board detection, serial monitor, compilation, upload - all inside IntelliJ or CLion. You write your sketch in an IDE that understands C++, with real autocomplete that knows your libraries, and then you hit a button to flash.
The serial monitor was the part I spent the most time on. The Arduino IDE has a decent one, and I needed to match it. Reading from a serial port sounds simple until you deal with baud rate detection, encoding, and not crashing when the user unplugs the board mid-stream.
What hardware projects teach you about IDE development
Building an IDE plugin for hardware forces you to think about things that pure software plugins never touch. Device detection. Serial ports that vanish. Build processes that target real hardware with real constraints. The feedback loop is slower - you write code, flash it, and wait for the LED to blink or the serial output to appear.
And that is exactly why good tooling matters more, not less. When your compile-test cycle takes 30 seconds instead of 3, you need your editor to catch mistakes before you hit upload.
If you are doing any serious work on ESP32 or Arduino - give it a try. The plugin has a 30-day trial.