Mga 1 hour lang ako on the Pico W with Thonny. Connected via USB, opened the REPL, started typing Python directly into the running microcontroller. Read a sensor in real-time. No compile-upload cycle.
Software dev ako, sanay ako sa "save file, run python script, see result" loop. To be able to TYPE LIVE into a running embedded board feels like cheating.
Paano po kayo nasanay sa "compile, upload, hope it works" workflow when this kind of alternative exists? Or am I about to discover yung downsides ng MicroPython that everyone is too polite to bring up?
REPL on MicroPython — was this always possible??
-
mark_ee_qc
- Posts: 10
- Joined: Tue May 05, 2026 10:51 am
Welcome sa club! Yung first time gumagana yung REPL sa Pico mo, parang first-time mo nag-Python sa interactive prompt, same level ng amazement.
Downsides para naman fair: yung MicroPython runtime adds overhead. Pure C/Arduino code mas mabilis at mas memory-efficient. Sa Pico siguro hindi mo ito mararamdaman kasi sobra na mabilis siya, pero sa Uno-class chips, MicroPython hindi praktikal.
Also debugging while live in the REPL is great pero hindi siya replacement for proper logging, once your code starts running standalone (no PC connected), yung print statements mo wala pwede mag-receive. Mag-add ka ng SD logging or send-to-serial-buffer setup.
Downsides para naman fair: yung MicroPython runtime adds overhead. Pure C/Arduino code mas mabilis at mas memory-efficient. Sa Pico siguro hindi mo ito mararamdaman kasi sobra na mabilis siya, pero sa Uno-class chips, MicroPython hindi praktikal.
Also debugging while live in the REPL is great pero hindi siya replacement for proper logging, once your code starts running standalone (no PC connected), yung print statements mo wala pwede mag-receive. Mag-add ka ng SD logging or send-to-serial-buffer setup.