Even the concept of Cloud is already "known" within the community, so I expected more from this talk than what was given. I also expected to see more options as the abstract describes and maybe some examples how this would be used.
Another thing which was pity, is that the second speaker was not here so the talk ended short.
For next time, see that you have a backup plan to cover when your co-speaker isn't around.
Keep it up and show us improvements on a next event.
Well done. Not easy to have a co speaker fall out sick. Maybe share slides before the event. I agree with the above comments. Also I would haved love to see a comparison between traditional vs cloud. Why and when is your hosting the right pick. Keep speaking!
I understand that the co-speaker was sick and that this impacts the talk. But as a speaker you should compensate for that.
The talk was too short and that was a bit of a shame. There are some many stories to tell about Amazon AWS. I wish you would share more of your experiences.
This was a bit too "AWS 101" for me.
My advice: work on it, turn it into a full AWS talk, spend more time on some of the cool features and convince developers that you can do some really awesome automation with it.
Pretty basic talk about AWS. I was really looking forward to an in-depth view on Google App Engine, too bad your colleague fell out sick. Try to learn at least some of the content of the other part of the talk so you can give at least an overview of the features and highlight some advantages.
Speaking overall was well done. Even though it was obvious English isn't your native language, I could clearly understand you.
Thanks for the feedback and I agree with the comments:) I know that my talk was not in-depth. I should have elaborated a more on technical aspects of deploying, managing, etc on AWS.
It was an interesting talk that covered the basics. Would have love to see more in-depth examples though I realise the talk would have been longer with the co-speaker and thus there would be less time to go in-depth. Too bad about the Google App Engine.
Comments
Comments are closed.
Even the concept of Cloud is already "known" within the community, so I expected more from this talk than what was given. I also expected to see more options as the abstract describes and maybe some examples how this would be used.
Another thing which was pity, is that the second speaker was not here so the talk ended short.
For next time, see that you have a backup plan to cover when your co-speaker isn't around.
Keep it up and show us improvements on a next event.
Well done. Not easy to have a co speaker fall out sick. Maybe share slides before the event. I agree with the above comments. Also I would haved love to see a comparison between traditional vs cloud. Why and when is your hosting the right pick. Keep speaking!
I understand that the co-speaker was sick and that this impacts the talk. But as a speaker you should compensate for that.
The talk was too short and that was a bit of a shame. There are some many stories to tell about Amazon AWS. I wish you would share more of your experiences.
This was a bit too "AWS 101" for me.
My advice: work on it, turn it into a full AWS talk, spend more time on some of the cool features and convince developers that you can do some really awesome automation with it.
Pretty basic talk about AWS. I was really looking forward to an in-depth view on Google App Engine, too bad your colleague fell out sick. Try to learn at least some of the content of the other part of the talk so you can give at least an overview of the features and highlight some advantages.
Speaking overall was well done. Even though it was obvious English isn't your native language, I could clearly understand you.
Thanks for the feedback and I agree with the comments:) I know that my talk was not in-depth. I should have elaborated a more on technical aspects of deploying, managing, etc on AWS.
It was an interesting talk that covered the basics. Would have love to see more in-depth examples though I realise the talk would have been longer with the co-speaker and thus there would be less time to go in-depth. Too bad about the Google App Engine.
Anyway, overal it was well done talk.