I've had to be deliberate about what I do with embedded programming. I sat down to introspect, and realised that I was: - learning the inner workings of vario

I've had to be deliberate about what I do with embedded programming. I sat down to introspect, and realised that I was: - learning the inner workings of various electronics - learning #![no_std] Rust - learning about software standards like Matter - doing projects that I never complete - reading, discussing, watching From the 4 quadrants, I don't think I was doing enough of the first, being to produce DIY devices that I can use around the house. It was only when I deliberately decided to focus on the first, that I was able to tame my time spent on the other 3 quadrants. That has sometimes meant accepting that I should use things like ESPHome, build my firmware/software in C and C++, etc. Else my expertise will forever be theoretical, not the reason why I got into embedded development in the first place.