← Weekly assignments

Week 15 — Group assignment: Interface and application programming

This page focuses on what I learned by following the group comparison of interface/app tools.

Individual assignment

Your personal work for this week — notes, photos, design files, and reflections.

Group assignment

Guangzhou (Chaihuo) — group documentation: comparing toolchains and development workflows across interface and application programming tasks.

Instead of only listing tools, I reorganized this week around my own learning path: what each tool taught me, when I should use it, and how it affects my Fab Academy workflow speed.

Note: The images below are shared group-reference visuals from the Chaihuo Week 15 page, included here with local relative paths.

1) Arduino IDE — fastest path for hardware verification

My key learning is that Arduino IDE remains the shortest route for board bring-up and quick actuator/sensor checks. For early-stage testing, reducing setup complexity is more important than maximizing architecture flexibility.

Arduino IDE interface
Group reference image: Arduino IDE interface.

2) Thonny — lowers friction for Python-based embedded experiments

I learned that Thonny is useful when my goal is rapid logic iteration and educational clarity. Its debugging feedback is straightforward, which helps when moving between MicroPython experiments and hardware tests.

Thonny IDE interface
Group reference image: Thonny environment.

3) VS Code — strong baseline for mixed codebases

The main takeaway for me is workflow unification: one editor for firmware notes, scripts, and web pages. With extensions, VS Code can bridge embedded tasks and documentation tasks in one place.

Visual Studio Code interface
Group reference image: VS Code interface.

4) MATLAB/Simulink — model-first thinking before hardware risk

I learned that MATLAB + Simulink is valuable when behavior must be reasoned before physical deployment. It is less about quick tinkering and more about reducing trial-and-error in control or signal-heavy problems.

MATLAB and Simulink
Group reference image: MATLAB/Simulink.

5) AI tools (Cursor / Codex CLI / Claude Code) — acceleration with process discipline

My biggest learning this week is not just that AI tools are fast, but that quality depends on clear task boundaries. When prompts are scoped well, these tools greatly speed up refactoring, debugging, and repetitive edits; when prompts are vague, I lose traceability.

Cursor IDE
Group reference image: Cursor IDE.
OpenAI Codex CLI
Group reference image: OpenAI Codex CLI.
Claude Code
Group reference image: Claude Code.

My practical conclusion for Fab Academy

  • Use Arduino IDE first for quick hardware validation.
  • Use VS Code as the stable daily environment for mixed tasks.
  • Use AI tools for speed, but always with explicit constraints and review checkpoints.
  • Use MATLAB/Simulink when modeling quality matters more than implementation speed.

Source

Group template and media source: Week 15 — Group Assignment: Interface and Application Programming.