I kind of did. I do enterprise API management using a low code solution now. It has its own embedded language. You have to understand transmission and programming generally.
I loved writing JavaScript, but not for work. I really felt like almost nobody in (corporate) JavaScript land could program and were super emotional about it. I really got tired of the stupidity and compensating nonsense. This new thing is so much better that it’s hard to put into words.
FrankWilhoit
I sort of did; the motivation was the poor quality of business requirements, which I traced to the extremely false belief that a physical data model can capture a business process. Then the game was to try to cultivate information architecture, to understand the rationales for legacy data models, especially where they were not good enough, and eventually train how to deduce adequate data models from the processes. Long story short, no one understood.
dadjoker
Yea, a guy named David Neal (@reverentgeek) was a full stack dev, who now does data engineering.
He also taught himself to draw, and is really good at it.
I loved writing JavaScript, but not for work. I really felt like almost nobody in (corporate) JavaScript land could program and were super emotional about it. I really got tired of the stupidity and compensating nonsense. This new thing is so much better that it’s hard to put into words.