How are you verifying all the code that's generated? Do you think that verifying properly would take you as much effort as the original implementation would've?
Wow this is pretty cool! I'm gonna give a try.
For me, this is actually what most of my slack usage is. Just writing notes to myself and then occasionally messaging others.
I've read this and it gives a pretty good overview of the history as well as current events surrounding the semiconductor industry. I think it gives a good high-level overview so you'll have the foundation to dig deeper.
I don't think that this book by itself would be enough to understand the semiconductor business, but it's a great place to start to get acclimated.
Agreed. IMO, it all started with Hooks. Things really went downhill from there.
useEffect is terrible! Example, how easy it to forget the dependency array?! Because of that, you have to setup linting rules to fix the poor API provided by that hook...
I have the JetBrains Toolbox with the “All Products Pack” and it works like a charm! The JetBrains products are far superior to other products I’ve tried. I mostly used Pycharm, Datagrip, CLion, and Goland and love them. Couldn’t imagine dev without them
They can do all the R/D they want, however, they can’t produce on a large scale. Meaning, they won’t have a lot of the same capabilities these chips offer at scale.
Maybe you should consider applying for positions at places like D.E. Shaw or 2Sigma. From what I've read they many folks who have advanced degrees in maths and other similar fields. I'm sure you'd be able to put your skills to use at one of those places.
Plus, the pay is good too :)