Thread: My wife was at the supermarket today picking up some bits and pieces and she got chatting to the young guy at the checkout.
They had a chat...
He had decided after school not to go to University and had been working there for a couple of years but was excited now because he was about to go.
He'd looked at the options after school and seen it as something that wasn't for him. But having worked for two years he decided that the job options weren't that good so decided to look again.
Gave my Dad an echo dot yesterday. He has macular degeneration and I thought it might help. Installed a big company's skill for him to help with trains (my parents can't drive any more) and watched the interaction.
It was terrible.
Sometimes tech just doesn't get it
I completely understood the interaction and the questions.
A 70+ yr old?
He asked a perfectly reasonable question about when the next train from X to Y was and the response was
"Do you want to plan a journey?"
Which was a bit confusing because he'd just said that
There was no "I didn't quite understand" or anything like that.
Our voice interactions should default to "my fault... Didn't understand... Sorry" and not respond with questions that seem confusing
If the person says "I just said that" then you've got it wrong
THREAD: A good practice is for each AWS Lambda function to do one thing rather than bundle all functionality into one function.
Why?
A quick answer is that the smaller the Lambda function, the faster it will load and the quicker it should run (depending on libraries etc), but that's very simplistic
Let's take a slightly more businesslike view of #serverless