In the previous article we have created our first Alexa skill.
We have implemented all the steps manually.
We have created a skill from the web interface.
We have configured the interaction model.
Then we have created a lambda function with the simplest implementation of the skill.
And then we have linked the lambda function and the skill together, so they can work as a one.
All of these steps can be optimized and improved.
That’s why this time I would like to cover a way to create an Alexa skill using a command line and a code editor of your choice.
Although we would need to use AWS web interface to create a user and policy, the rest would be done via command line interface.
Let’s get started.
In the previous article we have covered the basics of Alexa skills development.
We have discussed what is Alexa and Alexa skills, how does it work in general and why you may be interested to play with the technology.
Today we are going to build our first skill from zero to
production an Echo device.
Let’s get started.
During the last few months I was sticking to topics around Elixir.
But as a developer there are some other areas in software development I am interested in.
So I would like to write about them too and share my experience.
Recently I was playing around with Amazon Alexa skills development.
I’ve found that fun and interesting. So let’s get started.
When you are developer and work on different projects,
sooner or later you would face a need to extract some part of functionality into separate libraries to reuse it.
Different languages and frameworks provide their own functionality to distribute libraries among other developers or within a single company.
Elixir is not an exception here. For Elixir and Erlang, we have “Hex” as a package manager.
So, let’s see how we can publish our own Elixir package.
At the beginning of my Ruby on Rails career, I was using the “Rails Best Practices” code metric tool.
The intent of the tool is pretty simple.
It provides you suggestions how to improve your code. The best part of it, that on the https://rails-bestpractices.com website I was able to find detailed instructions why and how to fix those issues.
I love that tool. I was using it every day to check my code.
The cool part about those suggestions that I can go and read an explanation of that issue on their website.
I was using the tool mostly for learning stuff.
Now it’s time to learn some Elixir. And today I would like to discover a similar tool “Credo”.
Credo focuses on teaching and code consistency.