From 834513bfb4e78451dd0faa8e051ba34dca083b82 Mon Sep 17 00:00:00 2001 From: Piyush Shewale <92243361+Piyush-OG@users.noreply.github.com> Date: Sat, 16 Oct 2021 10:50:18 +0530 Subject: [PATCH] Update README.md --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 3c4ed2a..67caf39 100644 --- a/README.md +++ b/README.md @@ -206,3 +206,8 @@ We've been to a lot of hackathons, both as hackers and sponsors. What advice do - **Go to workshops and activities.** Yes, you're probably here to hack, but you can't be productive for the whole time. Don't forget to take breaks, talk to people, and take advantage of what the organizers have put together for you. - **Demo.** Even if your hack isn't perfect, it's a hack. You had a weekend to build something and hopefully you did other things, too (maybe cup-stacking?) Prepare a demo and give it! It's fun and important to be able to explain what you did and to show others. - On the topic of demos, keep it short and simple. Yes, it's nice to have a lead-in showing you did background research, but the focus should be on showing what you built. That is the primary focus of judges: most everything else is probably secondary. +

All event of twilio is helpful,and its good to all learn something new

+ + +![images123](https://user-images.githubusercontent.com/92243361/137574867-dfe1e883-45e2-4c39-ac32-95fe465b9e68.png) +