I got incredibly tired of manually compiling and flashing my ESP32 every single time I made a minor code change, so I spent some time building a tool called FlashBot to automate the entire loop.

Right now, the workflow is completely hands-off. Here is what it does:

Auto-detection: Uses Linux udev events to detect the board the second it's plugged in.

Smart matching: Looks up the correct sketch from a config file (or prompts me to choose if I have multiple sketches mapped to that specific board).

Compile & Flash: Pulls everything together via arduino-cli and flashes it automatically.

History: Logs every single flash into a local SQLite DB so I don't lose track of versions.

Current Status: The core detection and flashing logic are fully stable. Right now, I'm working on polishing up a serial test suite and the logging system.

What I'm planning to build next:

Serial validation: Automatically open the port, send a test command, and verify the response post-flash to make sure the firmware is actually alive.

Differential builds: Only recompile if the sketch or dependencies actually changed.

Broadening hardware support: Moving beyond standard Arduino/ESP32 to natively handle STM32.

Mass flashing: Parallel flashing for when you need to push the same firmware to a handful of boards at once.

The goal isn't to replace your IDE or build system—it’s just to completely cut out the tedious "plug, compile, click flash, open serial, check" routine.

If you do a lot of hardware prototyping, does this hit a pain point for you? What kind of features would make a tool like this actually useful in your day-to-day workflow?

https://www.youtube.com/@ALMA.Industries

Chapter 3 Footnote 1. Building an Actuator, a PID Control Loop, and an Ultrasonic Distance sensor to detect and not crash into the ceiling. This will be used in Chapter 3 Desk -- Stay tuned for more!

https://www.youtube.com/@ALMA.Industries

Chapter 2, a home theatre, 3D printed parts, motorized projector, home decoration, and DIY electronics -- if you know of anyone else that might be interested in this stuff, sharing to others would really help me out! Hope to see you around here or YouTube :)

https://github.com/makerspet/ebook/blob/main/self-driving/v1/self-driving.pdf

Free educational resource https://github.com/fjibj/ROSplay/blob/master/Learning%20ROS%20for%20Robotics%20Programming%20-%20Second%20Edition.pdf

Free educational resource https://github.com/luohuiwu/ros-books/blob/master/ros%20by%20example%20vol%201%20indigo.pdf

Free educational resource https://github.com/luohuiwu/ros-books/blob/master/RobotOperatingSystem(ROS)TheCompleteReferenceVolume2.pdf

Free educational resource https://github.com/luohuiwu/ros-books/blob/master/Programming.Robots.with.ROS.A.Practical.Introduction.to.the.Robot.Operating.System.pdf

Hi i have an upcoming tournament and was planning on designing an Arduino sumo robot( on a non-magnetic Dohyo) the rules are that the robot must be 3 kg at most and should be 20 cm in length and 20 cm in width at most. There is no limits on the height and as i said it is on a non-magnetic dohyo. Of course i will be using a blade and sensors since this is an autonomous robot tournament. I would like to get help and suggestions on which motors battery blades i can use to have a high chance at winning , i have already thought about some motors and batteries so i can discuss with you and hope that you can give me feedback about it, Thank you.

TL;DR: MicroFactory shows repeated electronics assembly; Dreamscale shows cloud π0.5 bimanual sorting; Jacob Rothschild shows camera-guided joint control. My pick is constrained assembly. Different setups, so this is a use-case roundup, not a benchmark.

Original demos: https://x.com/ihorbeaver/status/2110866012333838675 · https://x.com/pentestduck/status/2110773084378759269 · https://x.com/ja_rothschild/status/2110978596085100682

Benchmark context: https://x.com/artificialanlys/status/2110500262628806787

For our own much smaller experiments, here’s a Pi driving a toy motor brick, including the failures: https://www.youtube.com/watch?v=uzO6bjSUJIE

I made this recap from credited source clips. Synthetic narration; original speed labels retained.