How to Raise a Robot Army #dddperth
•
0 likes•36 views
Imagine you have a 100 days and your only directive is that you **must** spend at least an hour a day in the code. Could you build an army of bots and take over the world? Recently I've taken part in the #100DaysOfCode Challenge, which is designed to help beginners get started with meaningful and fun activities, even when they have no previous knowledge. Together we'll cover the basics of bot building and go under the hood to look at the code and the basic architecture that holds it together. We'll examine some of the bots you can build and by the end of the session you'll be able to start building your own robot minions.
More Related Content
What's hot
Similar to How to Raise a Robot Army #dddperth
Similar to How to Raise a Robot Army #dddperth (20)
More from Michelle Sandford
Recently uploaded
Recently uploaded (20)
How to Raise a Robot Army #dddperth
- 1. How to Raise a Robot Army over a #100DaysofCode Michelle Sandford @msandfor #robotsrising
- 3. How do I raise a robot army over 100 days of code? @msandfor #robotsrising
- 7. GitHub + Visual Studio Code + Heroku @msandfor #robotsrising
- 8. There are only 2 rules in #100DaysOfCode/ Rule #1 – Spend an hour a day in the Code @msandfor #robotsrising
- 9. There are only 2 rules in #100DaysOfCode/ Rule #2 – Tweet out your progress everyday @msandfor #robotsrising
- 10. Rule #3 – Give people shout-outs #Recognise There are only 2 rules in #100DaysOfCode/ @msandfor #robotsrising
- 11. #100DaysOfCode Day 0 https://github.com/msandfor/100-days-of-code/ There are only 2 rules in #100DaysOfCode/ Rule #4 – Have a plan Because real programmers start counting from 0 @msandfor #robotsrising
- 12. There are only 2 rules in #100DaysOfCode/ Rule #5 – Fork the repo and commit to the log @msandfor #robotsrising
- 13. There are only 2 rules in #100DaysOfCode/ Rule #6 – Create a fallback / setdefault() @msandfor #robotsrising
- 15. Computer says No! Hush now, I’m learning @msandfor #robotsrising
- 17. There are only 2 rules in #100DaysOfCode/ Rule #7 – Have fun with your code @msandfor #robotsrising
- 19. Follow CS Dojo on YouTube There are only 2 rules in #100DaysOfCode/ Rule #8 – Share useful tutorials with the community
- 21. Azure | Heroku | some other cloud Some other cloud @msandfor #robotsrising
- 22. Facebook | Twilio | Teams | Skype @msandfor #robotsrising
- 24. Checkout William Essilfie on https://www.twilio.com/blog There are only 2 rules in #100DaysOfCode/ Rule #8 – Share useful tutorials with the community
- 29. Azure Bot Service | QNAMaker | Facebook @msandfor #robotsrising
- 30. What I’ve learned/ @msandfor #robotsrising
- 35. Have you tried turning it off and on again? @msandfor #robotsrising
- 37. Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those! >>>import this @msandfor #robotsrising