Firmware Development Workflow Guide


Hello, I'm a senior embedded engineer and I've worked in multiple industries (semiconductor, e-commerce, consumer electronics, mining, marine, automotive, and aerospace) for the last 7 years.

I'm also an embedded freelancer from 2021.

In this guide, I've distilled the techniques and workflow I use daily to develop firmware for many of my clients. Learn how to do firmware development in the real world.

This is a short guide to help you familiarize yourself with the professional environment (corporate, freelancing, or consulting).

If you want to get a preview chapter. You can access it for free here:

The guide will be a Notion Pages. For the guide content outline, see below:

It will help you to build firmware that:

  • Easier to add features
  • Easier to modify
  • Easier to debug
  • Easier to read

Great firmware design will save you tons of time, and tons of effort.

But you don't know me yet, so don't take my word for it. Here are some words from my customer who has accessed the guide:

Pay once to get lifetime access. You will also get guide updates for free.

What you will learn:

  • The complete workflow used in professional firmware development
  • Unit testing example using Catch2
  • Testing automation using GitHub Actions
  • Example project: Weather Station
  • Bonus example project: LoRaWAN GPS Tracker

I also plan to add more bonus materials in the future:

  • Firmware Development using the Agile approach (already done)

What you will get:

  • The link to the Notion Pages containing the complete package, including bonus materials.
  • Example projects.
  • Free lifetime updates


Is this a video course?


What does "Professional" mean?

A professional is someone who is getting paid to do something as a profession. If you think professional means a world-class expert, please don't buy.

In this guide, I'm showing you how a professional (me) applies his workflow to his daily tasks.

I’m an absolute beginner (I don’t know what Arduino is), should I buy it too?

No please don’t. I think you will be confused because of the technical depth. You should be a junior embedded engineer at least. If you’re a business person, marketer, or non-tech, it’s not for you.

I'm a senior engineer with 5+ YoE, should I buy?

Please don't. Senior engineers are very opinionated, they already have their own way of doing things, and they usually have no issues with embedded workflow.

This is for intermediate level engineers.

Why should I buy this right now?

Because you will get free lifetime updates.

I'm planning to add more value to this guide over time. And to compensate for my time and effort, I will raise the price to match its value.

If you buy now, you will definitely buy at a cheap price. Or, you can buy later when the cost is 2x the current price.

Why should I buy this? I can learn it for free somewhere else.

Shoot me a DM if you found one! Because I've never found it myself.

Even universities don't teach end-to-end workflow for firmware development.

This guide is highly practical, I only cover the stuff you will actually face at work.

The guide is a Notion Page, which you can access via a link.

It consisted of 14 chapters + 3 bonus chapters.

It's designed to be concise so the brevity is the main benefit. I don't want to add too much fluffs so you can start applying the concepts inside the book.

I want this!
248 sales

You'll get a link to my Notion Pages.

Copy product URL

Firmware Development Workflow Guide

I want this!