All I can do is point someone in the right direction and give a few things to read. But nobody wants to read. Unfortunately, doing hardware is hard without rea

All I can do is point someone in the right direction and give a few things to read. But nobody wants to read. Unfortunately, doing hardware is hard without reading. Lots of it. Choosing a part requires reading datasheets by the dozen or hundreds, so you get fast at skimming them but when you pick one and design its circuit, you need to read every damn page of that PDF. And then go and dig up the errata if it exists too. Lots of knowledge about hardware exists either as institutional knowledge in people's heads or in books. But, electrons and physics still work the same way they did 30 years ago, so there's no reason you can't read an EE book from that long ago to get foundational concepts. Coders (myself included) try to Google our way to the fastest solution to each problem. Why read API documentation if someone has a solution on stack overflow? Unfortunately papering over knowledge gaps will often explode in your face because there inevitably will be mistakes, and now you have to wait 4 weeks to respin and assemble a new board. Long turn times and physical costs require a bit more level and less yolo in hardware. So there is no reason to become allergic to reading if you want to be in hardware.