2020 Hackaday Remoticon

Why the 2020 Hackaday Remoticon Happened

Before Remoticon, the Hackaday Superconference was known as a compact, in-person gathering for engineers, embedded developers, security researchers, artists, and people who own more jumper wires than matching socks. The physical event offered talks, badges, hallway conversations, demonstrations, and workshops, but workshop capacity was limited by rooms, tables, equipment, and the inconvenient fact that two people cannot occupy the same chair without creating an HR incident.

The pandemic eliminated the usual Pasadena gathering, yet it also exposed a design opportunity. A remote event could welcome people who could not normally travel to California, while allowing attendees to work with the computers, test equipment, components, and half-disassembled gadgets already sitting in their homes. Hackaday therefore made workshops the center of Remoticon rather than a small side track.

General admission was free, while selected workshop registrations and mailed kits could involve separate arrangements. Eventbrite served as the ticketing hub, Hackaday.io hosted workshop pages and public discussions, and a schedule or “wayfinder” helped attendees navigate simultaneous activities. This was not one video call with 500 muted microphones. It was a distributed collection of classrooms, streams, chats, and workbenches stitched together with several platforms and a heroic quantity of browser tabs.

How the Virtual Hardware Conference Was Organized

Friday: Bring a Hack, Without Bringing Luggage

The weekend began with a community Bring-a-Hack session on Friday. Ticket holders joined through the Remo virtual-event platform and showed projects from their own spaces. That format preserved an essential part of a maker conference: the spontaneous moment when somebody says, “This motor controller is behaving strangely,” and six strangers immediately gather around because strange behavior is basically catnip for engineers.

Saturday: Keynotes, Workshops, Demos, and the Hackaday Prize

Saturday carried the largest public program. Kipp Bradford delivered a keynote earlier in the day, while Alfred Jones, then associated with Lyft’s self-driving engineering work, presented the evening keynote. Public workshop streams included RF emissions debugging, machine learning on microcontrollers, and PCB reverse engineering. Other channels carried demos and several heats of the SMD Challenge. The evening concluded with the Hackaday Prize ceremony, connecting Remoticon to Hackaday’s broader open-hardware community.

Sunday: More Technical Depth and More Tiny Components

Sunday continued with software-defined radio, hardware debugging, artificial-heart design methodology, zero-to-ASIC instruction, integrated-circuit reverse engineering, and a session on creating useful technical guides. The SMD Challenge returned for additional heats, proving that surface-mount components can disappear just as effectively on camera as they do on a real workshop floor.

The Workshops That Defined Remoticon 2020

The published program listed more than 20 hands-on workshops plus demonstrations. Topics ranged from soldering and circuit sculpture to radio-frequency troubleshooting, 3D printing on fabric, modular synthesis, firmware security, hardware debugging, finite element analysis, creative coding, robot control, sensor dashboards, and photorealistic PCB rendering. The variety mattered because it showed how broadly the word “hacking” was being used: not simply breaking security, but understanding systems deeply enough to modify, repair, reuse, or reinvent them.

PCB Reverse Engineering with Eric Schlaepfer

Eric Schlaepfer’s PCB reverse-engineering workshop demonstrated a careful, repeatable process for understanding an unfamiliar circuit board. Participants learned to identify components, build a bill of materials, photograph board layers, and trace connections into a schematic. The important lesson was not a magical trick. It was disciplined observation: label the parts, consult datasheets, map the traces, and resist the urge to declare the board haunted after the first confusing via.

Firmware Reverse Engineering with Asmita Jha

Asmita Jha introduced firmware analysis through theory and practical labs. Her workshop covered attack surfaces, static and dynamic analysis, extracting files from firmware images, identifying hardcoded credentials, modifying binaries, and using emulation when software targeted a different processor architecture. Tools discussed included Binwalk, Ghidra, QEMU, Firmwalker, FACT, and password-cracking utilities. By turning the session into guided exercises, the workshop gave beginners a route into a field that often looks like a wall of hexadecimal numbers wearing sunglasses.

Breaking Encrypted 3D-Printer Firmware with Uri Shaked

Uri Shaked’s workshop treated encrypted printer firmware as a live puzzle. Participants used a Jupyter-style workflow, Python, frequency analysis, known structures in ARM firmware, compression behavior, and pattern recognition to infer how the binary had been transformed. The case study was especially effective because it connected reverse engineering to a practical maker goal: replacing disappointing proprietary firmware with software the community could improve.

TinyML with Shawn Hymel

Shawn Hymel offered an end-to-end introduction to running machine learning on a microcontroller. The workshop moved from gathering audio samples to preparing data, training a model, and deploying it to an STM32 device capable of recognizing spoken commands. In a field where tutorials sometimes skip directly from “install the library” to “build a robot butler,” the complete workflow was valuable. It made embedded artificial intelligence feel like an engineering process rather than wizardry performed by a cloud server in an undisclosed cave.

Car Hacking with Amith Reddy

Amith Reddy focused on the Controller Area Network, or CAN bus, used by modern vehicles. With tools such as can-utils and the ICSim simulator, participants could observe packets, manipulate a virtual dashboard, and understand how vehicle subsystems communicate. The workshop emphasized safe experimentation and simulation before touching a real automobile, an excellent policy when the device under test weighs thousands of pounds and has opinions about momentum.

Sound, Synthesis, and Creative Hardware

Not every Remoticon session lived in the security dungeon. Jonathan Foote used VCV Rack to teach the building blocks of modular synthesis, including oscillators, filters, amplifiers, and envelope generators. Helen Leigh and Robyn Hails showed how piezo elements and common household materials could become microphones for found-sound experiments. Other workshops explored glowy origami, circuit sculpture, creative coding, 3D printing onto fabric, and interactive media. Together, these sessions reminded attendees that engineering is also a medium for art, noise, delight, and occasionally a very convincing robot vampire.

The SMD Challenge: Competitive Soldering Goes Remote

The virtual SMD Challenge was one of the event’s most distinctive experiments. Participants received or purchased small boards and component kits, then joined scheduled heats to assemble the circuits under time pressure. Teams associated with hacker conferences and badge communities also participated, while viewers watched through Twitch streams.

Remote competition introduced obvious complications. Organizers had to coordinate kits, time zones, cameras, judging, and different workbench setups. Yet the format also widened participation. A competitor did not need to fly with tools, explain flux to airport security, or discover at the venue that the good tweezers were still at home. The challenge turned isolated desks into one shared, slightly smoky electronics bench.

What Remoticon Got Right

It Used the Attendee’s Own Workshop

For hands-on learning, home participation had a surprising advantage: attendees already knew where their tools were, at least theoretically. They could install software before a session, arrange a second display, prepare components, and continue experimenting after the instructor signed off. Workshop pages preserved slides, code, setup instructions, project files, and public discussions, so the learning experience extended beyond a single broadcast.

It Lowered Geographic Barriers

Removing the trip to Pasadena opened the event to people who faced travel costs, visa restrictions, mobility barriers, family responsibilities, or schedules that made an in-person weekend impractical. Remoticon was still constrained by time zones and internet access, but the potential audience became global by design rather than global only in the promotional brochure.

It Created a Durable Technical Archive

Many workshop recordings were later edited and published, while Hackaday.io project pages continued to hold supporting material and discussions. That archive is arguably the event’s strongest legacy. A conference talk usually vanishes into memory, along with the name of the person who had the brilliant oscilloscope trick. Remoticon converted much of its program into reusable learning resources that could be revisited at a slower pace.

Where the Remote Format Struggled

The same design that created variety also produced fragmentation. Attendees had to move among Eventbrite, Hackaday.io, Remo, Zoom, YouTube, Facebook Live, Twitch, and workshop-specific resources. Multiple sessions overlapped, and a participant could spend several minutes locating the correct room while a presenter was already explaining the one command that prevented everything from catching metaphorical fire.

Technical failures were inevitable. One published workshop recap noted that part of a Zoom recording was lost. Participants also encountered setup problems involving virtual machines, operating-system differences, disabled virtualization settings, missing software, and time-zone mistakes. These are ordinary workshop problems, but remote delivery transfers more troubleshooting responsibility to each attendee.

Remoticon also could not fully reproduce hallway conversation, shared meals, badge hacking, or the energy of seeing a strange machine operate three feet away. The virtual format improved access and documentation, but it did not make physical community obsolete. It simply proved that a hardware conference could preserve meaningful participation when physical gathering was impossible.

Why the 2020 Hackaday Remoticon Still Matters

Remoticon 2020 was important because it treated disruption as a design problem. The organizers did not copy the in-person Superconference pixel for pixel. They changed the balance of the event, expanded workshop capacity, distributed materials in advance, used multiple public channels, and invited people to build from their own environments.

That approach reflected the culture of open hardware itself. Good hardware communities share files, expose methods, document mistakes, and allow other people to reproduce the work. Remoticon’s strongest sessions followed the same pattern: a presenter introduced a real problem, supplied tools or data, demonstrated a process, and left participants with enough information to keep exploring.

For later virtual and hybrid maker events, the lesson was straightforward. Remote conferences work best when they are designed as participatory systems, not as television schedules with chat boxes attached. Give attendees something to inspect, modify, assemble, measure, or debug. Otherwise, even the most enthusiastic engineer may begin reverse engineering the mute button purely for entertainment.

The 2020 Hackaday Remoticon Experience: A Weekend at the Home Workbench

The most authentic way to understand Remoticon is to imagine the event from an attendee’s desk. The conference did not begin when a keynote stream went live. It began days earlier, with preparation. A participant might install VCV Rack, download a firmware image, configure a virtual machine, locate a CAN-bus simulator, charge a camera, clear space beside the keyboard, and discover that every USB cable in the house had mysteriously become charge-only.

On Friday, the Bring-a-Hack session offered a lower-pressure entrance. Instead of walking into a crowded hotel room carrying a prototype, attendees joined from the places where those prototypes had been built. That changed the show-and-tell dynamic. A creator could reach behind the monitor for a spare board, point a camera at a machine too large to transport, or open the exact source files used in the project. The workshop itself became part of the presentation.

Saturday demanded tactical planning. One screen might hold the main YouTube stream, while another displayed workshop instructions, chat, code, or a datasheet. The schedule included keynotes, technical workshops, demonstrations, SMD heats, and the Hackaday Prize ceremony. Choosing one session meant missing another, a familiar conference problem now enhanced by the knowledge that both rooms were only one browser tab away.

The hands-on sessions could be deeply satisfying when preparation worked. In a TinyML workshop, a participant could move from audio samples to a model running on a microcontroller. In a reverse-engineering lab, the progress was more detective story than lecture: inspect a binary, form a hypothesis, test it, fail, notice a pattern, and suddenly understand why several bytes looked wrong. The instructor’s screen showed the official path, while each attendee’s machine supplied its own collection of warnings, dependency errors, and character-building exercises.

The SMD Challenge offered a different kind of tension. Competitors worked under cameras with tiny components, hot irons, and the awareness that dropping one resistor could turn a timed event into an archaeological excavation. Yet the remote setting also made the competition charmingly personal. Every camera revealed a different bench: pristine laboratory mats, improvised kitchen tables, magnifiers, homemade fume extractors, and tool collections assembled over years.

By Sunday, remote-conference fatigue probably competed with curiosity. The schedule still offered SDR, hardware debugging, IC reverse engineering, ASIC design, and technical communication. The smartest attendees likely accepted that no human could absorb everything and instead collected workshop pages and recordings for later. That behavior was not a failure of the format. It was one of its advantages. Remoticon became both a live gathering and a technical library.

The experience was therefore imperfect but unusually appropriate for its audience. Hardware hackers are accustomed to incomplete documentation, tools that almost work, and systems assembled from parts never intended to cooperate. A conference spread across several platforms was not elegant, but it was hackable. Participants learned, chatted, soldered, debugged, and adapted. In 2020, that counted as more than a successful weekend. It was proof that a hands-on technical community could remain active even when everyone had to stay physically apart.