Thank you, that tweet thread was really helpful. “Functions as a Service as a Service” maps it into familiar language I use today. Whereas “making every applica

Thank you, that tweet thread was really helpful. “Functions as a Service as a Service” maps it into familiar language I use today. Whereas “making every application on the Internet more programmable” sounds unrealistic (every application) and is pretty vague. The latter is like an aspirational goal that the team has, which is fine if that’s what motivates you, but as a customer it’s not what motivates me. What motivates me is the problems I have. “Making every application on the Internet more programmable” is actually a bit off-putting because it reminds me of the aggression of Microsoft and their "A computer on every desk and in every home." Bill Gates wrote it in internal memos. It’s not the words they used in their marketing campaigns. My pithy advice for the blog would be: Keep the motivational quote on the team’s wall and in the team’s memo, and find out what customers have on their wall and are writing in their memos. Glad that this sort of feedback on the blog is welcome, because it could be really good. Information architecture with the strange categories is another thing that’s confusing btw.