01101000 01101001 00100001I'm a proud physicist who loves electronics and all sorts of technology at the hardware level. Interacting directly with science & engineering, analyzing something into its very core principle, while on the other hand also transforming the principles & ideas into something real.Being a hardware engineer is like a one-man band, at least for me, and not necessarily in a bad way. Extracting requirements from client or ideation and planning development with the team. Designing it which is my main hard skill, but also contains a complex interconnected decision making: • To make sure that the raw material or part I need is available, so needed to check to the distributor or take a deep dive into the datasheet to find a similar part replacement while still keeping the BOM optimized;• To make sure what I designed is manufacturable otherwise it's useless, so needed to check to the vendor for the constraint or manufacture limitation, understand how the design will have impact on the production phase; • To make sure that my design is compatible with the application layer. Hardware alone is usually a dumb thing and that's why it needed application/firmware, so I needed to understand or often write it myself what logic will perform on top of that hardware, what peripheral is needed, HAL to interact, and so on.There are hard work in a "hard"ware. It consumes time, energy, and money (or at least it's manageable if I'm not releasing any magic smoke from those expensive chips :D). But at the end of the day, with the rest of the energy, I can sit and appreciate what I've done. To able to make from as abstract as ideas/concepts into functional things that you can see, touch, and feel. And that's why I loved hardware.