Why Compiler Errors Are So Confusing
GCC error messages are written for compiler developers, not engineers. A message like "cannot convert 'String' to 'const char*'" tells an experienced C++ developer exactly what's wrong, but for someone learning embedded systems, it's impenetrable.
Common Arduino Errors AI Explains Well
- ▸Type errors — String vs char array, int vs long
- ▸Scope errors — variables declared inside if blocks
- ▸Library errors — missing includes, wrong function signatures
- ▸Linker errors — undefined references, missing implementations
- ▸Hardware-specific errors — SPI/I2C address conflicts
How to Paste Errors for Best Results
Copy the full error output, not just the first line. The most useful error is often several lines down. Include the platform (Arduino Uno, ESP32, STM32) and relevant code section.
Beyond Compilation Errors
- ▸Runtime errors — unexpected resets, watchdog timeouts, stack overflows
- ▸Logic errors — "my code compiles but the LED blinks at wrong rate"
- ▸Serial output — garbage on serial monitor instead of sensor readings
💡 Tip: Every error explanation includes a prevention tip — understanding why it happened stops an entire class of future bugs.