But if API Gateway or Cognito fails, I'll probably have a bigger problem than a tooltip that does not work. However, the tooltip will be cached, so if you loaded it once, it'll work even if API Gateway fails.
The AI part is used to generate tooltips, not to display them, so if it fails, I'll not be able to create new tooltips, or users will temporarily be unable to interact with them (ask sub-questions).
On Day 25, we connects the Create Tooltip flow by writing React code and an AppSync Lambda resolver with some help from CofounderGPT and Github Copilot.
VideoPuppet is excellent. I am using it to create videos for the Five Minutes Serverless Youtube channel, and so far, results are outstanding. I can create a video from the markdown file really fast.
I am not worried about A at all. This was a technical article, but here's the explanation I posted to twitter:
Although I enjoy talking about technology, and I enjoy working with serverless, it's important to note that using serverless for @slackvacation is not a technology decision. It's a business decision. Not because the auto -scaling, that's nice to have, but that's not a problem startups are facing in their early phase. It's about financial incentives — also, about focus, ability to move fast and test ideas, and the ability to grow without shooting future self into the foot.
We still often fail to do things fast enough, but we are aware of the problem and working hard to fix it.
Serverless architecture improves the way we build software. But it’s much more than just development, because it can improve the way we are building our products in general.
With serverless, your developers can focus on the business logic implementation, instead spending a lot of time on setting up and maintaining infrastructure. It also decreases the cost of your application, because it converts capital to operating expenses. Besides that, having smaller services allows you to implement changes and A/B tests easier, and to pivot faster.
With all the benefits mentioned above, serverless becomes more than the architecture choice, it becomes an important strategy. For example, it can allow you to charge teams per active user, without having to be a big company, such as Slack.
Well, I spent a few months writing a book about serverless, so we have slightly different opinion about serverless haha :)
I like this explanation why serverless looks promising: https://youtu.be/SPsaqiegOP4. I recommend full video, but those few minutes are the important part.
Personally, serverless helps me to build reliable software faster, and it minimizes the amount of time I need to spend setting up the infrastructure. For me it already changed the things big way. It'll not work the same way for everybody, which is fine and expected.
Serverless is more than a cloud computing execution model. It changes the way we plan, build, and deploy apps. But it also changes the way we test our apps.
Serverless can also change the way we test our non-serverless apps. For example, UI testing or load testing.
"How to select a tool in an ecosystem that generates frameworks faster than a Zerg Swarm, and kills them with the enthusiasm of Darwin on amphetamines?" :D
You are right. Skill is all about an interaction design, and the other problem with Alexa is that you can't catch phrases that Alexa can't parse to intents.
For Bitcoin, I am not into crypto currency, but that skill was done on live coding session, so I needed something that people like and that I can integrate really fast.
Serverless Apps with Node and Claudia.js walks you through building serverless apps on AWS using JavaScript. Inside, you'll create a full project designed to help you understand and apply general serverless design principles and concepts. Along the way, you'll also discover what Claudia brings to the table.
FB message templates already works fine, there's an example here: https://github.com/claudiajs/example-projects#chat-bots
In a next day or two we are planning to add a builder that simplifies creating those FB Messenger templates.
Telegram inline responses are working too.
But if API Gateway or Cognito fails, I'll probably have a bigger problem than a tooltip that does not work. However, the tooltip will be cached, so if you loaded it once, it'll work even if API Gateway fails.
The AI part is used to generate tooltips, not to display them, so if it fails, I'll not be able to create new tooltips, or users will temporarily be unable to interact with them (ask sub-questions).