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
Mere abstraction a bit different because with say JS you need to learn a skill. It is not easy for a non programmer to do well. Takes a lot of hours. Now or soon they will be telling the computer what they want for simple things. Userspace for non programmers is going to expand greatly.
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.
> is there a modern engineer on earth who hasn’t used Twilio’s API at least once?
Reading this thread makes me feel like I'm taking crazy pills. Twilio is huge and is the leader, but they hold less than 40% market share in CPaaS and makes something like 60-70% of their revenue in the US. There are a lot of competitors and a lot of reasons to never use Twilio.
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