Week 15 — Interface and application programming

This week’s topic: Interface and application programming.

Group assignment

In Shenzhen Chaihuo, we compared interface/application toolchains by practical workflow value: bring-up speed, debugging clarity, collaboration efficiency, and model-driven reliability.

Work objective

Instead of making a tool catalog, we mapped each environment to a real task stage in Fab Academy development and summarized when each one gives the best return.

1) Fast bring-up path: Arduino IDE

Arduino IDE remains the shortest path for hardware verification and quick sensor/actuator checks, especially at early prototyping stage.

2) Rapid Python iteration: Thonny

Thonny is useful for MicroPython experiments where readability and low-friction debugging are more important than full project architecture.

3) Unified daily workspace: VS Code

VS Code works as a central workspace for firmware, scripts, documentation, and web pages, helping keep mixed tasks in one coherent environment.

4) Model-first development: MATLAB/Simulink

MATLAB/Simulink is most useful when behavior should be validated at model level before committing to hardware-side trial and error.

5) AI-assisted development with constraints

AI tools improved speed for repetitive edits and debugging, but quality depended on explicit task boundaries and review checkpoints.

Practical conclusion

• Start with Arduino IDE when hardware verification speed is critical.
• Use VS Code as the long-term workspace for mixed project artifacts.
• Use AI tools only with explicit scope and human review gates.
• Use MATLAB/Simulink when modeling confidence matters more than raw coding speed.