personperson

In the future it’ll likely be that doing it manually will be considered specialty work. This is already the case with much of programming — as you’d bring in a higher level engineer to do something like tear into the source code of SDKs and monkey with them.

For something as “simple” as a doughnut, this will just improve the learning curve and let you learn some things a bit later, just like today you can jump into beginner JS without knowing any programming fundamentals

I feel like this isn’t the “betrayal” that it’s made out to be.

Twilio won at their niche. People often talk about “if we just get 1% of the market…” — is there a modern engineer on earth who hasn’t used Twilio’s API at least once?

They’re moving towards doing the same thing with other parts of tech companies, in this case it’s marketing. It’s not like their APIs change because of it, these are additional products they’re introducing. Engineers generally find anything marketing related icky, but they’re very happy to collect the checks which are funded through these icky distribution methodologies.

I’m pretty pro family but I have to admit you just absolutely smoked ‘em

I don’t think he’s entirely wrong. That being said, citing frontend examples of why Node is bad for a server side language is a reach.

I feel like arguing about which languages “suck” is generally reserved for the peak of Dunning Kruger mountain. Code is code, write better code.