> First, a whole army of developers writing Javascript for the browser > started self-identifying as “full-stack”, diving into server development > and asyn

> First, a whole army of developers writing Javascript for the browser > started self-identifying as “full-stack”, diving into server development > and asynchronous code. This is gatekeeping--we're all ultimately self-identifying as software engineers. But more importantly it's not correct. Many of the original engineers working with Node had non-UI backgrounds. Node.js made asynchronous programming easy and promised that you could use the same language on the back-end and front-end, which seemed like good bang-for-buck for people that wanted to focus on products. Also, not to point the blame somewhere else, but wasn't it Golang engineers that went really hard on the microservices koolaid?