Tech stack

Technologies used in delivery across firmware, integration, and the software around the product.

This is not meant as a keyword wall. It is a practical view of the languages, targets, tooling, and workflow surfaces used in real client and product work.

Grouped by delivery area

The useful distinction is not frontend versus backend, but what part of product delivery each tool actually supported.

Embedded targets and firmware

Used in embedded delivery, device bring-up, firmware implementation, RTOS-oriented work, and hardware-adjacent product development.

CC++ESP32STM32nRF52AVRMSP430ZephyrOSRTOS kernelsbootloadersFOTA

Where this showed up

Baracoda: ESP32 firmware and field update behavior for an intelligent weight scale
M2MTeam: embedded software in medical robotics work
MicrOS: lightweight RTOS work across startup code, linker flow, kernel surfaces, and board bring-up
Profile-backed experience across bare-metal and OS-driven embedded implementation

Connectivity and product integration

Used where device behavior has to connect reliably to the rest of the product and survive real deployment conditions.

Wi-FiBLEMQTTCoAPOpenThreadUARTSPII2CREST APIsdevice-to-cloud integration

Where this showed up

Baracoda: Wi-Fi connectivity and update flows around the product boundary
Connected-product consulting: firmware, payloads, tooling, and backend touchpoints kept in one thread
Earlier telemetry-oriented work: hardware interfaces and connected-system integration
Profile-based experience explicitly covering MQTT, CoAP, OpenThread, and custom APIs

Software, tooling, and data

Used for backend integrations, internal tools, delivery support software, web integrations, and product-facing utilities around the device.

PythonNode.jsMongoDBdesktop toolingweb toolingautomation scriptsWordPresscloud servicesQtQEMU

Where this showed up

G2Labs delivery work: utility software and web-adjacent tooling around embedded products
SeaChange: software around a production media platform with integration constraints
Internal and client tooling: Python and Node.js where they shortened delivery loops
Profile-backed range including WordPress and cloud-connected integrations for modern hardware platforms
MicrOS: simulator-backed iteration and sample execution through QEMU

Workflow and engineering environment

Used in daily delivery, debugging, collaboration, and implementation flow across client, product, and open-source work.

GitHubGitLabVS CodeEclipseCMakeNinjaLinux (Ubuntu)CI workflows

Where this showed up

Client delivery across established teams: GitHub and GitLab workflows
Embedded development: VS Code, Eclipse, and Linux (Ubuntu) in day-to-day implementation
Consulting and product work: CI-backed iteration and handover support
MicrOS: public build flow and contributor-facing tooling around CMake and Ninja
Profile-listed workflow depth including CMake and open-source developer tooling