I wanted to start a blog for a long time, but I was always postponing it.
A little bit more than a year ago, I’ve made a commitment to write a blog at least ones in two weeks.
In fact, I’ve ended up to publish a blog post almost every week.
Today, I would like to look back at this year and share my thoughts with you.
Software developers communicate by using different terms and metaphors.
Some of those terms and metaphors are obvious for developers, but not that obvious for managers.
To communicate well, developers and managers need to interpret those terms in the same way.
Technical debt is one of those terms.
Let’s try to understand what is a technical debt is and what it isn’t.
In the previous articles, we have different aspects of developing Alexa skills.
We learned how to pass state between intents and sessions.
Sometimes, you may run into a situation when you need to interact with external services.
It could be a service to fetch weather information, local news or, you can even set up a private service to interact with IoT devices.
Basically, anything you can interact with over HTTP.
Now, let’s learn how we can interact with external APIs from an Alexa skill.
Keeping some state within a single session of Alexa skill could play an important role of how the skill interacts with a user.
Keeping the state between sessions may bring your skill to another level.
By doing so, the skill can pick up the user from the middle of a conversation and proceed from there.
Sounds great? So let’s learn how we can achieve that.
Last time we have learned how to capture input from the user.
Using captured inputs we are able to handle communication with users from our skills.
But a skill does not always have a linear conversation.
We may want to ask a question and behave differently based on the answer we’ve got.
To do that, we need to keep some information in the “memory” of an Alexa skill.
To achieve that, Alexa Skill SDK provides us an ability to use Session Attributes.
Let’s see how we can use that.